CVE-2024-9537

Confirmed PUBLISHED

ScienceLogic SL1 unspecified vulnerability

ScienceLogic · SL1
Exploited in the wild

Recommended Action

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

Confidence
Confirmed
Exploitation Status
Exploited in the wild
Observed in Sensors
No
Attempts (30d)
Unique Attacker IPs
CISA KEV
In CISA KEV
CVSS / EPSS
9.3 Critical

At a Glance

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.

cisa
CVE Published
Oct 18, 2024
Exploitation Reported
Oct 21, 2024
CVSS
9.3 Critical
EPSS
Remote Low complexity No user interaction Unauthenticated

Affected Versions

72 version rows · page 2 of 3

Vendor Product Version Status
sciencelogic
sl1

0 to < 12.2.3

Affected
sciencelogic
sl1

0 to < 12.3

Affected
sciencelogic
sl1

0 to < 10.1.x

Affected
sciencelogic
sl1

0 to < 10.2.x

Affected
sciencelogic
sl1

0 to < 11.1.x

Affected
sciencelogic
sl1

0 to < 11.2.x

Affected
sciencelogic
sl1

0 to < 11.3.x

Affected
sciencelogic
sl1

0 to < 12.1.3

Affected
sciencelogic
sl1

0 to < 12.2.3

Affected
sciencelogic
sl1

0 to < 12.3

Affected
sciencelogic
sl1

0 to < 10.1.x

Affected
sciencelogic
sl1

0 to < 10.2.x

Affected
sciencelogic
sl1

0 to < 11.1.x

Affected
sciencelogic
sl1

0 to < 11.2.x

Affected
sciencelogic
sl1

0 to < 11.3.x

Affected
sciencelogic
sl1

0 to < 12.1.3

Affected
sciencelogic
sl1

0 to < 12.2.3

Affected
sciencelogic
sl1

0 to < 12.3

Affected
sciencelogic
sl1

0 to < 10.1.x

Affected
sciencelogic
sl1

0 to < 10.2.x

Affected
sciencelogic
sl1

0 to < 11.1.x

Affected
sciencelogic
sl1

0 to < 11.2.x

Affected
sciencelogic
sl1

0 to < 11.3.x

Affected
sciencelogic
sl1

0 to < 12.1.3

Affected
sciencelogic
sl1

0 to < 12.2.3

Affected

CVE References

Show 4 more references

Recommended Actions

  • Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.
  • Use the Pro API to automate enrichment, telemetry, and workflow delivery for VM, SOC, and CTI pipelines.