How severe is GHSA-vhmj-5q9r-mm9g?

GHSA-vhmj-5q9r-mm9g has a CVSS score of 6.8/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-vhmj-5q9r-mm9g?

GHSA-vhmj-5q9r-mm9g affects the following packages: edumfa (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-vhmj-5q9r-mm9g?

Update edumfa to 2.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vhmj-5q9r-mm9g is resolved across your whole dependency graph.

How do I detect GHSA-vhmj-5q9r-mm9g in my PyPI dependencies?

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.

How do I mitigate GHSA-vhmj-5q9r-mm9g if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-vhmj-5q9r-mm9g?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-vhmj-5q9r-mm9g can be triaged on real exposure rather than presence alone.

Is GHSA-vhmj-5q9r-mm9g actively exploited in the wild?

No public exploit code has been indexed for GHSA-vhmj-5q9r-mm9g yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-vhmj-5q9r-mm9g published, and has it been updated?

GHSA-vhmj-5q9r-mm9g was published on July 17, 2024 and was last updated on December 6, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

MEDIUM severity

GHSA-vhmj-5q9r-mm9g — edumfa

MEDIUMFix: eduMFA/eduMFA@ad9d18b

GHSA-vhmj-5q9r-mm9g is a medium-severity (CVSS 6.8) vulnerability in edumfa. A fix is available for edumfa — see the affected versions and patch details below.

BlastRADIUS also affects eduMFA

Published

Jul 17, 2024

Updated

Dec 6, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 6, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍edumfa

Real-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

Summary

BlastRADIUS (see blastradius.fail for details) also affects eduMFA prior version 2.2.0, because the Message-Authenticator attributes were not checked.

Details

Website with the vulnerability information blastradius.fail The original vulnerability has been assigned CVE-2024-3596 Case in vince: https://kb.cert.org/vuls/id/456537

PoC

There is no known proof-of-concept except for the attack shown in the paper from the researchers

Impact

An attacker can trigger an authentication flow with a RADIUS-backed token, intercept the RADIUS packet sent by eduMFA and modify the RADIUS server's answer, which would lead eduMFA to believe that the token is valid, even though the RADIUS servers answer was a reject.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`edumfa`	all versions	2.2.0`pip install --upgrade 'edumfa==2.2.0'`

Detection & mitigation playbook

Open-source dependency

Detect
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.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vhmj-5q9r-mm9g 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-vhmj-5q9r-mm9g can be triaged on real exposure rather than presence alone.

Tailored to GHSA-vhmj-5q9r-mm9g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary BlastRADIUS (see blastradius.fail for details) also affects eduMFA prior version 2.2.0, because the Message-Authenticator attributes were not checked. ### Details Website with the vulnerability information blastradius.fail The original vulnerability has been assigned CVE-2024-3596 Case in vince: https://kb.cert.org/vuls/id/456537 ### PoC There is no known proof-of-concept except for the attack shown in the paper from the researchers ### Impact An attacker can trigger an authentication flow with a RADIUS-backed token, intercept the RADIUS packet sent by eduMFA and modify the RAD

O3 Security · Impact-Aware SCA

Is GHSA-vhmj-5q9r-mm9g in your dependencies?

O3 Security finds GHSA-vhmj-5q9r-mm9g across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works