BlastRADIUS also affects eduMFA

published 2024-07-17 2y ago modified 2024-12-06 last yr.

cvss: 6.8; version 3.1, GitHub
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

### 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.

Patch / fix

fixed in 1 links 1

pypi edumfa 2.2.0

github.com/eduMFA/eduMFA@ad9d18b commit

Is GHSA-vhmj-5q9r-mm9g in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by	version	score	vector
GitHub	3.1	6.8	CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

Affected packages

ecosystem	package	affected	fixed in
pypi	edumfa	<2.2.0	2.2.0

Classification

Weakness

CWE-924 Improper Enforcement of Message Integrity During Transmission in a Communication Channel

References

Sources

GitHub Advisory GHSA-vhmj-5q9r-mm9g

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.