p PatchFirst

GHSA-qq2p-4282-cfc5

GHSA-qq2p-4282-cfc5 · eduMFA: Incorrect InnoDB snapshot isolation possibly allows token reusage

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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

CVSS 7.1 · High · Fix available

Published
Updated

Stack: python

Affected products and versions

  • edumfa PyPI

    Versions
    • 1.2.0
    • 1.3.0
    • 1.4.0
    • 1.5.0
    • 1.5.1
    • 2.0.0
    • 2.0.1
    • 2.0.2
    • 2.0.3
    • 2.1.0
    • 2.2.0
    • 2.3.0
    • 2.4.0
    • 2.5.0
    • 2.6.0
    • 2.6.1
    • 2.7.0
    • 2.7.1
    • 2.7.2
    • 2.8.0
    • 2.9.0
    • 2.9.0rc1
    Affected ranges
    • ECOSYSTEM: < 2.9.1

    Update to 2.9.1

Original sources

Check your server →