Internal package disclosure via malformed REST errors
Published Dec 15, 2023 · Updated Oct 8, 2024
Information disclosure in WSO2 API Manager allows remote attackers to obtain an internal package name through a malformed REST API request. An invalid token causes affected REST handlers to return an error entity without a JSON content type, allowing the response writer's server-side exception to expose a WSO2 package name. No authentication is required; disclosure is limited to technical details that identify the underlying WSO2 implementation.
Summary
What happened
Information disclosure in WSO2 API Manager allows remote attackers to obtain an internal package name through a malformed REST API request. An invalid token causes affected REST handlers to return an error entity without a JSON content type, allowing the response writer's server-side exception to expose a WSO2 package name. No authentication is required; disclosure is limited to technical details that identify the underlying WSO2 implementation.
The record
- CVE
- CVE-2023-6839
- Published
- Dec 15, 2023
- Updated
- Oct 8, 2024
- Vendor
- WSO2
- Product
- WSO2 API Manager
- Classifications
- CWE-209, T1592.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 15, 2023CVE publishedPublication date reported by the CVE source.
- Oct 8, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.0.0.0 <3.0.0.15
- Affected versionversion=3.2.0.0 <3.2.0.32
What conditions does exploitation require?
What is affected?
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