Unauthenticated SSRF via undisclosed deprecated service
Published Mar 13, 2020 · Updated Aug 4, 2024
Server-side request forgery in GitLab EE 3.0 through 12.8.1 allows remote attackers to make server-originated network requests. GitLab identifies the locus only as a deprecated service and has not disclosed the endpoint, input flow, or missing validation that permits the requests. No authentication or user interaction is required; the server can reach unintended services, while the vendor has not bounded the data or state exposed through those requests.
Summary
What happened
Server-side request forgery in GitLab EE 3.0 through 12.8.1 allows remote attackers to make server-originated network requests. GitLab identifies the locus only as a deprecated service and has not disclosed the endpoint, input flow, or missing validation that permits the requests. No authentication or user interaction is required; the server can reach unintended services, while the vendor has not bounded the data or state exposed through those requests.
The record
- CVE
- CVE-2020-10077
- Published
- Mar 13, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-918
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 13, 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