GHSA-74r7-3mjm-jc5v — edumfa
MEDIUMGHSA-74r7-3mjm-jc5v is a medium-severity (CVSS 6.5) vulnerability in edumfa. A fix is available for edumfa — see the affected versions and patch details below.
eduMFA: Unauthenticated Failcounter Increment on Resolver Tokens via /validate/check
Real-World Exposure
edumfaReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | edumfa | all versions | 2.9.1pip install --upgrade 'edumfa==2.9.1' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for edumfa, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update edumfa to 2.9.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-74r7-3mjm-jc5v is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-74r7-3mjm-jc5v in your dependencies?
Find it across PyPI, including transitive dependencies.