CVE-2019-13007 json
An issue was discovered in GitLab Community and Enterprise Edition 11.11 through 12.0.2.
published 6y ago modified 4mo ago also EUVD-2019-4581
- cvss
- 4.9
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 62%
- public exploits
- 0
- none known
Summary
An issue was discovered in GitLab Community and Enterprise Edition 11.11 through 12.0.2. When an admin enabled one of the service templates, it was triggering an action that leads to resource depletion. It allows Uncontrolled Resource Consumption.
Is CVE-2019-13007 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
0.98% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-400 Uncontrolled Resource Consumption
- Technology feeds
References
-
about.gitlab.com
/blog/categories/releases/
release-notes, vendor-advisory
-
about.gitlab.com
/releases/2019/07/03/security-release-gitlab-12-dot-0-dot-3-released/
vendor-advisory
Sources
- CVE List CVE-2019-13007
- NVD CVE-2019-13007
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.