CVE-2019-14943 in the critical feed json
An issue was discovered in GitLab Community and Enterprise Edition 12.0 through 12.1.4.
published 7y ago modified 4mo ago also EUVD-2019-6038
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 80%
- public exploits
- 0
- none known
Summary
An issue was discovered in GitLab Community and Enterprise Edition 12.0 through 12.1.4. It uses Hard-coded Credentials.
Is CVE-2019-14943 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.00% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-798 Use of Hard-coded Credentials
- Technology feeds
References
-
about.gitlab.com
/blog/categories/releases/
release-notes, vendor-advisory
-
about.gitlab.com
/2019/08/12/critical-security-release-gitlab-12-dot-1-dot-6-released/
vendor-advisory
-
gitlab.com
/gitlab-org/omnibus-gitlab/issues/4530
broken-link
Sources
- CVE List CVE-2019-14943
- NVD CVE-2019-14943
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.