CVE-2019-15737 json
An issue was discovered in GitLab Community and Enterprise Edition through 12.2.1.
published 7y ago modified 4mo ago also EUVD-2019-6672
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 72%
- public exploits
- 0
- none known
Summary
An issue was discovered in GitLab Community and Enterprise Edition through 12.2.1. Certain account actions needed improved authentication and session management.
Patch / fix
- gitlab gitlab 12.0.8, 12.1.8, 12.2.3
Is CVE-2019-15737 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.39% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
| NVD | 2.0 | 6.4 | AV:N/AC:L/Au:N/C:P/I:P/A:N |
Classification
- 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-ce/issues/42733
broken-link
Sources
- CVE List CVE-2019-15737
- NVD CVE-2019-15737
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.