Summary
BlastRADIUS also affects eduMFA
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.
GHSA-VHMJ-5Q9R-MM9G has a CVSS score of 6.8 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.2.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-VHMJ-5Q9R-MM9G? GHSA-VHMJ-5Q9R-MM9G is a medium-severity security vulnerability in edumfa (pip), affecting versions < 2.2.0. It is fixed in 2.2.0.
- How severe is GHSA-VHMJ-5Q9R-MM9G? GHSA-VHMJ-5Q9R-MM9G has a CVSS score of 6.8 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of edumfa are affected by GHSA-VHMJ-5Q9R-MM9G? edumfa (pip) versions < 2.2.0 is affected.
- Is there a fix for GHSA-VHMJ-5Q9R-MM9G? Yes. GHSA-VHMJ-5Q9R-MM9G is fixed in 2.2.0. Upgrade to this version or later.
- Is GHSA-VHMJ-5Q9R-MM9G exploitable, and should I be worried? Whether GHSA-VHMJ-5Q9R-MM9G is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-VHMJ-5Q9R-MM9G is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-VHMJ-5Q9R-MM9G? Upgrade
edumfato 2.2.0 or later.