CVE-2023-37486
Sap Commerce Hycom 2105 … 2205
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-37486 is a medium-severity Use of Cache Containing Sensitive Information (CWE-524) vulnerability in Sap Commerce Hycom. Its CVSS base score is 5.9 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked at the 43th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-41373
Vulnerability Data
Under certain conditions SAP Commerce (OCC API) - versions HY_COM 2105, HY_COM 2205, COM_CLOUD 2211, endpoints allow an attacker to access information which would otherwise be restricted. On successful exploitation there could be a high impact on confidentiality with no…
more
impact on integrity and availability of the application.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V14.3.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.
Refreshing cached data or generating it ephemerally and deleting afterward directly mitigates storage of sensitive information in caches.
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.
Enforcing least-privilege access permissions directly limits who can read cached sensitive data.
Protecting confidentiality of data-at-rest covers caches that persist sensitive information.
Protecting data-in-use can mitigate exposure when caches hold transient sensitive values.
Logical access controls on environments reduce the chance an outsider can reach the cache.
Hardened configuration baselines can disable or secure caching of sensitive data.
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.
Information deletion ensures sensitive data is removed from caches when no longer needed.
Data leakage prevention can block unauthorized access to cached sensitive information.
A.8.26 only requires that security requirements (including those that could address caching of sensitive data) be identified and specified during development or acquisition; it does not itself mandate, design, or implement any change that would make the cache flaw stop being present in the resulting application.
A.8.27 mandates establishing and applying secure engineering principles (including secure-by-design, least privilege, hardening, and data sanitization) during architecture and development; it does not itself remove an already-written cache that stores sensitive information outside the intended control sphere.
Secure coding practices prevent caching of sensitive data outside intended boundaries.