Patchfirst
CVE-2020-11035 High · 7.5 EPSS 0.9%

weak CSRF tokens in GLPI

glpi-project · GLPI

Official description · CVE.org

In GLPI after version 0.83.3 and before version 9.4.6, the CSRF tokens are generated using an insecure algorithm. The implementation uses rand and uniqid and MD5 which does not provide secure values. This is fixed in version 9.4.6.

Breakdown
17.2 / 100
Exploited
Not confirmed
Reports
0
Tactics
7/15

How an attack unfolds

Based on mappings. Select a step to see the evidence.
  1. How attackers get in

  2. What they do

Disclosed on 5 May 2020. No public exploit code or confirmed exploitation is recorded.

techniques

4 , grouped by in kill-chain order 4

Initial AccessTA0001

Valid Accounts T1078 also Persistence, Privilege Escalation, Stealth
MITRE CTID mapping of the CVE · primary impact

Credential AccessTA0006

Network Sniffing T1040 also Discovery
MITRE CTID mapping of the CVE · primary impact
Brute Force T1110
MITRE CTID mapping of the CVE · how it is exploited
Adversary-in-the-Middle T1557 also Collection
MITRE CTID mapping of the CVE · primary impact

Detection

0 rules for this CVE · 100 general rules for its techniques

Rules for this CVE

0 that reference CVE-2020-11035 directly.

CVE-specific rules are not available in this build. Search SigmaHQ ↗

General rules for this CVE’s techniques

These detect the technique in general, not this specific vulnerability.

Brute ForceT111025 general rules
Valid AccountsT107856 general rules
Network SniffingT10409 general rules
Adversary-in-the-MiddleT155710 general rules

Sigma rules © SigmaHQ, Detection Rule License 1.1; linked, not reproduced.

What security researchers reported

Not named in any threat report yet

References

3 links, grouped by NVD tag
↑ ↓ chooseEnter openEsc close