API traffic disclosure via missing TLS verification
Published Apr 28, 2023 · Updated Jan 31, 2025
Improper certificate validation in GitLab::API::v4 through 0.26 allows man-in-the-middle attackers to intercept GitLab API traffic. The constructor creates its HTTP::Tiny transport without verify_SSL enabled, so it accepts a certificate that cannot establish the GitLab server's identity. A successful attack requires control of the client-server network path and exposes request and response contents to interception.
Summary
What happened
Improper certificate validation in GitLab::API::v4 through 0.26 allows man-in-the-middle attackers to intercept GitLab API traffic. The constructor creates its HTTP::Tiny transport without verify_SSL enabled, so it accepts a certificate that cannot establish the GitLab server's identity. A successful attack requires control of the client-server network path and exposes request and response contents to interception.
The record
- CVE
- CVE-2023-31485
- Published
- Apr 28, 2023
- Updated
- Jan 31, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-295, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 28, 2023CVE publishedPublication date reported by the CVE source.
- Jan 31, 2025Record 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.
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