Unauthenticated file disclosure via Workhorse request smuggling
Published Apr 22, 2020 · Updated Aug 4, 2024
HTTP request smuggling in GitLab 10.7.0 through 12.9.2 allows remote attackers to disclose files through a Workhorse bypass. GitLab identifies the locus as Workhorse but has not published the malformed-request parsing discrepancy that permits the bypass. The unauthenticated network path can expose files and permit unauthorized job artifact uploads; no code execution or service interruption is reported.
Summary
What happened
HTTP request smuggling in GitLab 10.7.0 through 12.9.2 allows remote attackers to disclose files through a Workhorse bypass. GitLab identifies the locus as Workhorse but has not published the malformed-request parsing discrepancy that permits the bypass. The unauthenticated network path can expose files and permit unauthorized job artifact uploads; no code execution or service interruption is reported.
The record
- CVE
- CVE-2020-11506
- Published
- Apr 22, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-444, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 22, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.
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