CVE-2021-31866 json
Redmine before 4.0.9 and 4.1.x before 4.1.3 allows an attacker to learn the values of internal authentication keys by observing timing diff…
published 5y ago modified 2mo ago also BIT-redmine-2021-31866 , EUVD-2021-18741
- cvss
- 5.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 69%
- public exploits
- 0
- none known
Summary
Redmine before 4.0.9 and 4.1.x before 4.1.3 allows an attacker to learn the values of internal authentication keys by observing timing differences in string comparison operations within SysController and MailHandlerController.
Patch / fix
- bitnami redmine 4.0.9, 4.1.3
- redmine redmine 4.0.9, 4.1.3
- redmine Debian 14, Debian 13, Debian 12 5.0.0-1
debian advisories DEBIAN-CVE-2021-31866
- redmine Arch Linux 4.2.1-1
arch linux advisories AVG-1743
Is CVE-2021-31866 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 FencerExploit prediction
1.23% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| OSV | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | redmine | <4.0.9 >=4.1.0, <4.1.3 |
4.0.9 4.1.3 |
Classification
- Weakness
-
- CWE-203 Observable Discrepancy
References
-
redmine.org
/projects/redmine/wiki/Security_Advisories
vendor-advisory, advisory
-
redmine.org
/news/131
vendor-advisory, advisory
-
lists.debian.org
/debian-lts-announce/2021/05/msg00013.html
mailing-list, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2021-31866
web
Sources
- CVE List CVE-2021-31866
- NVD CVE-2021-31866
- OSV BIT-redmine-2021-31866
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.