CVE-2020-8919
CVE-2020-8919 — Information leakage in Gerrit
An information leak vulnerability exists in Gerrit versions prior to 2.15.21, 2.16.25, 3.0.15, 3.1.10, 3.2.5 where a missing access check on the branch REST API allows an attacker with only the default set of priviledges to read all other user's personal account data as well as sub-trees with restricted access.
Published Updated Sources: cvelistV5, Google
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
0%
chance of exploitation in 30 days
CVSS base
3.5
LOW
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 3.5 | CVSS 3.1 | LOW | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-285
Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.
- T1574.010Hijack Execution Flow: ServicesFile Permissions Weakness
- T1083File and Directory Discovery
- T1562.003Impair Defenses: Impair Command History Logging
References
6 on the record
- gerrit.googlesource.com/gerrit/+/0532fb876cb86bc091a91f78e6f28fff9e39ca65
x_refsource_CONFIRM
- www.gerritcodereview.com/2.15.html#21521
x_refsource_CONFIRM
- www.gerritcodereview.com/2.16.html#21625
x_refsource_CONFIRM
- www.gerritcodereview.com/3.0.html#3014
x_refsource_CONFIRM
- www.gerritcodereview.com/3.1.html#3110
x_refsource_CONFIRM
- www.gerritcodereview.com/3.2.html#325
x_refsource_CONFIRM
Elsewhere on this site
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.