CVE-2023-36919
Sap Enable Now
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NSummary
CVE-2023-36919 is a medium-severity Exposure of Sensitive Information Due to Incompatible Policies (CWE-213) vulnerability in Sap Enable Now. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 39th 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
- 🇪🇺 ENISA EUVD: EUVD-2023-40839
Vulnerability Data
In SAP Enable Now - versions WPB_MANAGER 1.0, WPB_MANAGER_CE 10, WPB_MANAGER_HANA 10, ENABLE_NOW_CONSUMP_DEL 1704, the Referrer-Policy response header is not implemented, allowing an unauthenticated attacker to obtain referrer details, resulting in information disclosure.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 4 hardening rules · 4 OS baselines
V1.1.2V1.2.1V1.2.3V4.1.2
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.
Marking hardware components with the permitted impact or classification level directly supports consistent policy enforcement, reducing the chance that sensitive data is processed on an incompatible component and thereby exposed.
Demands documented authority and policy alignment for PII processing, reducing exposure due to incompatible or absent policies.
Directly enforces purpose compatibility and policy alignment for PII processing, preventing exposure from incompatible policies.
Validating that output matches expected content directly mitigates failures to properly encode or escape data for its destination context.
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.
Understanding stakeholder needs directly surfaces incompatible sensitivity expectations that produce the exposure.
Establishing risk-management policy based on organizational context is the primary mechanism for aligning divergent sensitivity rules.
Secure SDLC practices directly require proper output encoding to prevent injection and message malformation.
Regulatory and privacy obligations often define the conflicting sensitivity views that the weakness fails to reconcile.
Periodic policy review can detect and correct stakeholder-policy mismatches before they cause exposure.
Defining and enforcing access policy is one concrete place where incompatible sensitivity decisions manifest as unauthorized 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.
Classification directly addresses mismatched sensitivity views by defining what must be protected.
Legal and contractual requirements often impose stricter sensitivity rules than developer policy.
PII protection explicitly reconciles developer exposure with data-subject or regulator expectations.
Secure coding standards explicitly require correct output encoding and escaping to preserve message structure.
Security testing can detect missing or incorrect encoding but does not itself implement the control.
High-level policy can mandate consistent handling of sensitive data across stakeholder expectations.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Ubuntu 24.04 (1 rule)
- V-270708 Ubuntu 24.04 LTS must be configured so that remote X connections are disabled, unless to fulfill documented and validated mission requirements. prevents CWE-213
Windows Server 2019 (1 rule)
- V-205757 Windows Server 2019 Debug programs: user right must only be assigned to the Administrators group. prevents CWE-213