Unauthenticated sensitive-information disclosure
Published Aug 20, 2024 · Updated Mar 14, 2025
Information disclosure in apolloconfig Apollo 2.2.0 allows remote attackers to obtain sensitive information via crafted requests. The published references do not disclose the affected endpoint or the request-handling operation that exposes the data. No authentication or user interaction is required, but the public record does not identify the returned information or the route's default exposure.
Summary
What happened
Information disclosure in apolloconfig Apollo 2.2.0 allows remote attackers to obtain sensitive information via crafted requests. The published references do not disclose the affected endpoint or the request-handling operation that exposes the data. No authentication or user interaction is required, but the public record does not identify the returned information or the route's default exposure.
The record
- CVE
- CVE-2024-42662
- Published
- Aug 20, 2024
- Updated
- Mar 14, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 20, 2024CVE publishedPublication date reported by the CVE source.
- Mar 14, 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.
Weakness, pattern, technique
No sourced classifications are available.
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