Cyber Resilience

CVE-2023-6839

Info Disclosure in Wso2 Api Manager 3.0.0 … 4.0.0

Published
15 December 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.0053 42th percentile
Risk Priority 45 floored blend · peak EPSS

Summary

CVE-2023-6839 is a medium-severity Generation of Error Message Containing Sensitive Information (CWE-209) vulnerability in Wso2 Api Manager. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Software (T1592.002); ranked at the 42th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Due to improper error handling, a REST API resource could expose a server side error containing an internal WSO2 specific package name in the HTTP response.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1592.002 Software Reconnaissance
Adversaries may gather information about the victim's host software that can be used during targeting.
T1082 System Information Discovery Discovery
An adversary may attempt to get detailed information about the operating system and hardware, including version, patches, hotfixes, service packs, and architecture.
T1592 Gather Victim Host Information Reconnaissance
Adversaries may gather information about the victim's hosts that can be used during targeting.
T1595 Active Scanning Reconnaissance
Adversaries may execute active reconnaissance scans to gather information that can be used during targeting.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-2905Same product: Wso2 Api Manager
CVE-2024-8010Same product: Wso2 Api Manager
CVE-2026-2053Same product: Wso2 Api Manager
CVE-2024-4867Same product: Wso2 Api Manager
CVE-2024-5848Same product: Wso2 Api Manager
CVE-2024-10242Same product: Wso2 Api Manager
CVE-2023-31664Same product: Wso2 Api Manager
CVE-2025-6024Same product: Wso2 Api Manager
CVE-2024-2321Same product: Wso2 Api Manager
CVE-2024-4598Same product: Wso2 Api Manager

Affected Assets

wso2
api manager
3.0.0, 3.1.0, 3.2.0, 4.0.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V16.5.1

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-209

Detects error messages that leak sensitive information as evidence of disclosure.

addresses: CWE-209

The control directly mitigates generation of error messages containing sensitive authentication details by requiring obscured feedback instead of verbose responses.

addresses: CWE-209

Misdirection allows generation of misleading error messages that withhold or falsify sensitive details.

addresses: CWE-209

Explicitly requires error messages to avoid including sensitive or exploitable details while still supporting corrective action.

addresses: CWE-209

Validation ensures error messages contain only expected, non-sensitive content and blocks leakage via verbose errors.

addresses: CWE-209

Fail-safe procedures can be defined to suppress or sanitize error output, reducing generation of messages that contain sensitive information.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require sanitized error handling to prevent sensitive data disclosure.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Secure coding standards explicitly forbid exposing sensitive data in errors.

finds

Security testing can detect error messages that leak sensitive information.

A.8.15 Logging partial match
degrades

Logging policy can require suppression of sensitive data in error messages.

prevents

Secure SDLC mandates error-handling rules that avoid leaking sensitive information.

prevents

Application security requirements can specify safe error messaging.

prevents

Secure architecture principles include proper exception handling.

References