Cyber Resilience

CVE-2023-37486

Sap Commerce Hycom 2105 … 2205

Published
08 August 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 5.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0052 42th percentile
Risk Priority 46 floored blend · peak EPSS

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 Unsecured Credentials (T1552); ranked at the 42th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

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

T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
T1552.001 Credentials In Files Credential Access
Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials.
T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
T1539 Steal Web Session Cookie Credential Access
An adversary may steal web application or service session cookies and use them to gain access to web applications or Internet services as an authenticated user without needing credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-39439Same product: Sap Commerce Cloud
CVE-2026-24321Same product: Sap Commerce Cloud
CVE-2024-33003Same product: Sap Commerce Cloud
CVE-2024-33004Same vendor: Sap
CVE-2019-0344Same product: Sap Commerce Cloud
CVE-2026-23684Same product: Sap Commerce Cloud
CVE-2023-42481Same product: Sap Commerce Cloud
CVE-2024-0874Shared CWE-524
CVE-2024-12314Shared CWE-524
CVE-2024-45596Shared CWE-524

Affected Assets

sap
commerce cloud
2211
sap
commerce hycom
2105, 2205

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)
  • 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.

addresses: CWE-524

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.

PR.DS-01 mostly match
prevents

Protecting confidentiality of data-at-rest covers caches that persist sensitive information.

PR.AA-05 partial match
prevents

Enforcing least-privilege access permissions directly limits who can read cached sensitive data.

PR.DS-10 partial match
prevents

Protecting data-in-use can mitigate exposure when caches hold transient sensitive values.

PR.IR-01 partial match
prevents

Logical access controls on environments reduce the chance an outsider can reach the cache.

PR.PS-01 partial match
prevents

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.

prevents

Data leakage prevention can block unauthorized access to cached sensitive information.

prevents

Information access restriction directly limits who can read cached sensitive data.

mitigates

Information deletion ensures sensitive data is removed from caches when no longer needed.

mitigates

Cryptography can protect cached data at rest, but does not address access control scope.

prevents

Secure coding practices prevent caching of sensitive data outside intended boundaries.

none

Environment separation reduces risk of cache exposure across development/test/production.

References