CVE-2019-5485
CriticalPublic exploitCommand Injection in gitlabhook
Published Sep 16, 2019 · Updated Aug 4, 2024 · Also known as GHSA-549f-73hh-mj38
Key Facts
Patch immediately- CVE-2019-5485 is a critical-severity vulnerability (CVSS 10.0 v3.1) affecting Gitlabhook (Gitlabhook Project).
- It is not listed in any known-exploited vulnerabilities catalog. Public exploit code is available.
- EPSS estimates a 59% probability of exploitation in the next 30 days.
- No fixed version is listed yet; check the vendor advisory for mitigations.
- Brandefense priority: patch immediately, because it is very likely to be exploited soon.
CVSS v3.1
10.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS (30-day exploit likelihood)
59%
Higher than 99.1% of all scored CVEs
Exploited in the wild
No known
Not in a known-exploited catalog
Public exploit code
Available
Proof-of-concept or weaponized module
Get the full CVE-2019-5485 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
Description
NPM package gitlabhook version 0.0.17 is vulnerable to a Command Injection vulnerability. Arbitrary commands can be injected through the repository name.
Affected Products
3 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| GitlabhookGitlabhook Project | 0.0.17, >= Not Fixed | n/a |
Timeline
Publicly disclosed
Sep 16, 2019
Last updated
Aug 4, 2024
Weakness Type
- CWE-78 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
References
FAQ
Common Questions.
NPM package gitlabhook version 0.0.17 is vulnerable to a Command Injection vulnerability.
Affected: Gitlabhook (Gitlabhook Project) versions 0.0.17, >= Not Fixed. The full list is in the CVE brief.
It is not listed in any known-exploited vulnerabilities catalog.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
Public exploit code is available.
No fixed version is listed yet; check the vendor advisory for mitigations.
Brandefense priority: patch immediately, because it is very likely to be exploited soon.
Is CVE-2019-5485 Running On Your Attack Surface?
Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.
Request A Demo