Advisory

GHSA-qq2p-4282-cfc5

Also known as: None

Summary

eduMFA: Incorrect InnoDB snapshot isolation possibly allows token reusage

Details

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/

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-05-18 15:36 UTC
Modified
2026-05-18 15:49 UTC

Affected packages and fixes

edumfa

PyPI · All systems

Affected

  • introduced 0, fixed 2.9.1 (ecosystem)

Fixed versions

2.9.1

Fix

  • Fixed version 2.9.1
    pip install --upgrade edumfa==2.9.1

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences