CVE-2023-37516
Hcltech Hcl Leap ≤ 9.3.4
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:L/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-37516 is a low-severity Use of Cache Containing Sensitive Information (CWE-524) vulnerability in Hcltech Hcl Leap. Its CVSS base score is 3.2 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked at the 4th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SC-4 (Information in Shared System Resources) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-41403
Vulnerability Data
Missing "no cache" headers in HCL Leap permits user directory information to be cached.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V14.3.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces access authorizations so that cached sensitive data cannot be read by actors outside the intended sphere.
Directly prevents unauthorized transfer of information through shared resources such as caches.
Controls information flows to keep sensitive data from leaving its authorized control sphere via caches.
Requires cryptographic or other protection of sensitive information at rest, which covers cached data.
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.