CVE-2024-7569
Published: 13 August 2024
Summary
CVE-2024-7569 is a critical-severity Insertion of Sensitive Information Into Debugging Code (CWE-215) vulnerability in Ivanti Neurons For Itsm. Its CVSS base score is 9.6 (Critical).
Operationally, ranked in the top 8.0% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
CVE-2024-7569 is an information disclosure vulnerability affecting Ivanti ITSM on-prem and Neurons for ITSM versions 2023.4 and earlier. It stems from exposure of the OIDC client secret through debug information, as indicated by the associated CWEs covering insertion of sensitive information into externally accessible files and insecure storage of sensitive data.
An unauthenticated remote attacker can exploit the flaw over the network without requiring credentials or user interaction beyond a crafted request. Successful exploitation yields the OIDC client secret, enabling the attacker to achieve high-impact outcomes across confidentiality, integrity, and availability with a changed scope, consistent with the CVSS 9.6 rating.
The vendor has published a security advisory addressing the issue. The associated EPSS score has remained flat at 0.0747 with no material increase since disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-48468
Vulnerability details
An information disclosure vulnerability in Ivanti ITSM on-prem and Neurons for ITSM versions 2023.4 and earlier allows an unauthenticated attacker to obtain the OIDC client secret via debug information.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
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.
Tracking information locations and access supports secure storage practices instead of insecure ones.
Establishing an alternate site with equivalent protections directly mitigates insecure storage of sensitive backup information.
Requiring protection of backup information directly addresses insecure storage of sensitive data in backups.
Policy explicitly addresses insecure storage of CUI on external systems, requiring compliant handling and protections.
Proper categorization drives selection of storage controls that keep sensitive information from being stored insecurely.
The control explicitly requires secure storage mechanisms for sensitive information, closing the insecure-storage weakness class.
Storing information as fragments on distinct components is an architectural control that avoids insecure single-location storage of the complete sensitive data set.
OPSEC requirements improve handling and storage practices for sensitive supply-chain information.