Remote code execution via Maven path traversal
Published Jan 5, 2020 · Updated Aug 5, 2024
Path traversal in the GitLab EE Maven package registry allows remote attackers to gain privileges and execute code via crafted package parameters. The registry insufficiently sanitizes path-bearing Maven parameters before resolving package paths, but GitLab has not disclosed the exact parameter or filesystem operation. Network access to an affected registry requires no prior privileges, and successful exploitation can escalate privileges and execute code on the server.
Summary
What happened
Path traversal in the GitLab EE Maven package registry allows remote attackers to gain privileges and execute code via crafted package parameters. The registry insufficiently sanitizes path-bearing Maven parameters before resolving package paths, but GitLab has not disclosed the exact parameter or filesystem operation. Network access to an affected registry requires no prior privileges, and successful exploitation can escalate privileges and execute code on the server.
The record
- CVE
- CVE-2019-19628
- Published
- Jan 5, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 5, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo