Skip to content
Fencer Intel
high —

GHSA-qq2p-4282-cfc5 json

eduMFA: Incorrect InnoDB snapshot isolation possibly allows token reusage

published 5mo ago modified 5mo ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### Impact

For deployments using MySQL or MariaDB < 11.6.2 (or newer with innodb_snapshot_isolation=off) reusage of token values might be possible due to faulty transaction isolation inside the database. Exploiting this requires racing this transaction. Affected are all tokentypes whose values are only supposed to be used once, for example TOTP, HOTP and likely also WebAuthN.

#### Affected Combinations:

- MySQL (any version) - MariaDB with innodb_snapshot_isolation=OFF - innodb_snapshot_isolation was introduced in: MariaDB 10.6.18, MariaDB 10.11.8, MariaDB 11.0.6, MariaDB 11.1.5, MariaDB 11.2.4, MariaDB 11.4.2 with default OFF, can be turned ON as a workaround - for MariaDB >= 11.6.2 the default is ON, which is not affected - Same rules applies for Galera with underlying MariaDB

### Patches Fixed in version 2.9.1 by locking rows prior to write with SELECT FOR UPDATE.

### Workarounds Set innodb_snapshot_isolation to ON (default in MariaDB >= 11.6.2, e.g packaged in Debian 13).

### Resources https://mariadb.com/resources/blog/isolation-level-violation-testing-and-debugging-in-mariadb/

Patch / fix

  • pypi edumfa 2.9.1

Is GHSA-qq2p-4282-cfc5 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

Affected packages

ecosystem package affected fixed in
pypi edumfa
<2.9.1
2.9.1

Classification

Weakness

References

Sources

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.