CVE-2024-5217

Confirmed PUBLISHED

Incomplete Input Validation in GlideExpression Script

ServiceNow · Now Platform
Exploited in the wild PoC available

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.2 Critical

At a Glance

ServiceNow has addressed an input validation vulnerability that was identified in the Washington DC, Vancouver, and earlier Now Platform releases. This vulnerability could enable an unauthenticated user to remotely execute code within the context of the Now Platform. The vulnerability is addressed in the listed patches and hot fixes below, which were released during the June 2024 patching cycle. If you have not done so already, we recommend applying security patches relevant to your instance as soon as possible.

nessus_scanner nuclei_scanner cisa
CVE Published
Jul 10, 2024
Exploitation Reported
Jul 29, 2024
CVSS
9.2 Critical
EPSS
Remote Low complexity No user interaction Unauthenticated

Affected Versions

182 version rows · page 4 of 8

Vendor Product Version Status
servicenow
servicenow

0 to < washington_dc_patch_3_hot_fix_2

Affected
servicenow
servicenow

0 to < washington_dc_patch_4

Affected
servicenow
servicenow

0 to < washington_dc_patch_5

Affected
servicenow
servicenow

0 to < utah_patch_10_hot_fix_3

Affected
servicenow
servicenow

0 to < utah_patch_10a_hot_fix_2

Affected
servicenow
servicenow

0 to < utah_patch_10b_hot_fix_1

Affected
servicenow
servicenow

0 to < vancouver_patch_6_hot_fix_2

Affected
servicenow
servicenow

0 to < vancouver_patch_7_hot_fix_3b

Affected
servicenow
servicenow

0 to < vancouver_patch_8_hot_fix_4

Affected
servicenow
servicenow

0 to < vancouver_patch_9_hot_fix_1

Affected
servicenow
servicenow

0 to < vancouver_patch_10

Affected
servicenow
servicenow

0 to < washington_dc_patch_1_hot_fix_3b

Affected
servicenow
servicenow

0 to < washington_dc_patch_2_hot_fix_2

Affected
servicenow
servicenow

0 to < washington_dc_patch_3_hot_fix_2

Affected
servicenow
servicenow

0 to < washington_dc_patch_4

Affected
servicenow
servicenow

0 to < washington_dc_patch_5

Affected
servicenow
servicenow

0 to < utah_patch_10_hot_fix_3

Affected
servicenow
servicenow

0 to < utah_patch_10a_hot_fix_2

Affected
servicenow
servicenow

0 to < utah_patch_10b_hot_fix_1

Affected
servicenow
servicenow

0 to < vancouver_patch_6_hot_fix_2

Affected
servicenow
servicenow

0 to < vancouver_patch_7_hot_fix_3b

Affected
servicenow
servicenow

0 to < vancouver_patch_8_hot_fix_4

Affected
servicenow
servicenow

0 to < vancouver_patch_9_hot_fix_1

Affected
servicenow
servicenow

0 to < vancouver_patch_10

Affected
servicenow
servicenow

0 to < washington_dc_patch_1_hot_fix_3b

Affected

CVE References

Recommended Actions

  • Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.
  • Check enrichment artifacts for scanner coverage and available PoCs before rolling remediation validation.
  • Use the Pro API to automate enrichment, telemetry, and workflow delivery for VM, SOC, and CTI pipelines.