eduMFA: Unauthenticated Failcounter Increment on Resolver Tokens via /validate/check
Priority LOW 38CWE-20Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
### Impact If the resolver parameter is passed, but the user does not exist, all failcounters of tokens in that resolver will be increased. ### Patches This, along with other issues, was fixed in eduMFA v2.9.1. ### Workarounds Limiting access to `/validate/check` to client applications (i.e. Shibboleth/FreeRADIUS) using an authorization policy with `api_key_required` or using e.g. the reverse proxy.
Why it matters now
Fix Fixed edumfa (PyPI): 2.9.1
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | edumfa (PyPI) | before 2.9.1 | 2.9.1 | Patch available | GHSA-74r7-3mjm-jc5v |
- edumfa (PyPI) Vendor— Affected before 2.9.1 Fixed in 2.9.1 Patch available GHSA-74r7-3mjm-jc5v
Remediation
- Fix · GHSA-74r7-3mjm-jc5v edumfa (PyPI) Fixed in 2.9.1 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-74r7-3mjm-jc5v
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences