CVE-2019-15725 json
An issue was discovered in GitLab Community and Enterprise Edition 12.0 through 12.2.1.
published 7y ago modified 4mo ago also EUVD-2019-6661
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 78%
- public exploits
- 0
- none known
Summary
An issue was discovered in GitLab Community and Enterprise Edition 12.0 through 12.2.1. An IDOR in the epic notes API that could result in disclosure of private milestones, labels, and other information.
Patch / fix
- gitlab gitlab 12.0.8, 12.1.8, 12.2.3
Is CVE-2019-15725 in your stack? 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.76% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
- Technology feeds
References
-
about.gitlab.com
/2019/08/29/security-release-gitlab-12-dot-2-dot-3-released/
release-notes, vendor-advisory
-
gitlab.com
/gitlab-org/gitlab-ee/issues/11431
broken-link
Sources
- CVE List CVE-2019-15725
- NVD CVE-2019-15725
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.