CVE-2019-6240 json
An issue was discovered in GitLab Community and Enterprise Edition before 11.4.
published 7y ago modified 4mo ago also EUVD-2019-15807
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.2%
- EPSS 2.2% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
An issue was discovered in GitLab Community and Enterprise Edition before 11.4. It allows Directory Traversal.
Patch / fix
- gitlab gitlab 11.4.0
Is CVE-2019-6240 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
2.17% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/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-22 Improper Limitation of a Pathname to a Restricted Directory
- Technology feeds
References
-
about.gitlab.com
/blog/categories/releases/
product, vendor-advisory
-
about.gitlab.com
/2019/01/16/critical-security-release-gitlab-11-dot-6-dot-4-released/
vendor-advisory
Sources
- CVE List CVE-2019-6240
- NVD CVE-2019-6240
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.