CVE-2024-9537
ScienceLogic SL1 Unspecified Vulnerability
ScienceLogic SL1
ScienceLogic SL1 (formerly EM7) is affected by an unspecified vulnerability involving an unspecified third-party component packaged with SL1. The vulnerability is addressed in SL1 versions 12.1.3+, 12.2.3+, and 12.3+. Remediations have been made available for all SL1 versions back to version lines 10.1.x, 10.2.x, 11.1.x, 11.2.x, and 11.3.x.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 21 October 2024. US federal agencies were required to remediate it by 11 November 2024.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 3.8%, which is higher than 90.1% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2024-9537 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2024-9537.
What does CVE-2024-9537 affect?
CVE-2024-9537 affects ScienceLogic SL1. ScienceLogic SL1 (formerly EM7) is affected by an unspecified vulnerability involving an unspecified third-party component packaged with SL1. The vulnerability is addressed in SL1 versions 12.1.3+, 12.2.3+, and 12.3+. Remediations have been made available for all SL1 versions back to version lines 10.1.x, 10.2.x, 11.1.x, 11.2.x, and 11.3.x.
How severe is CVE-2024-9537?
CVE-2024-9537 is rated CRITICAL with a CVSS base score of 9.8. EPSS puts the probability of exploitation in the next 30 days at 3.8%, higher than 90.1% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 11 November 2024.
How should organisations respond to CVE-2024-9537?
Apply the vendor patch for ScienceLogic SL1 as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.