Skip to content
Fencer Intel
high 8.1

CVE-2019-12887 json

LinOTP replay vulnerability with auto resynchronization enabled for TOTP token

published 7y ago modified 4mo ago also GHSA-rqg8-xjp2-pg9w , PYSEC-2019-103 , EUVD-2019-0076

cvss
8.1
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 67%
public exploits
0
none known

Summary

KeyIdentity LinOTP before 2.10.5.3 has Incorrect Access Control (issue 1 of 2).

Patch / fix

  • pypi linotp 2.11.1
  • keyidentity linotp 2.10.5.3

Is CVE-2019-12887 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

Exploit prediction

1.17% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 8.1 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P
GitHub 3.0 8.1 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi linotp
<2.11.1
2.11.1

Classification

Weakness
  • CWE-294 Authentication Bypass by Capture-replay

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.