Skip to main content
Mallory
CriticalExploited in the wildCISA KEVVulnerability

CVE-2024-5217: Unauthenticated remote code execution in ServiceNow GlideExpression

Published Jul 10, 2024 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.2Critical · v4
EPSS99.6%100th percentile
CISA KEVYesAdded Jul 29, 2024
In the wildActivePer CISA KEV
Vendor
Servicenow
IdentifiersCVE-2024-5217CWE-184 · Incomplete List of Disallowed Inputs

CVE-2024-5217 is an input-validation vulnerability affecting ServiceNow Now Platform Washington DC, Vancouver, and earlier releases, including Utah. Incomplete filtering of disallowed inputs in GlideExpression script processing can allow an unauthenticated remote attacker to execute code in the context of the Now Platform. Technical accounts describe a GlideExpressionScript namespace-validation bypass involving single-quoted declarations. Some accounts instead assign a filesystem blacklist bypass to this CVE, creating uncertainty over the attribution of individual components in the associated three-vulnerability exploit chain.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can compromise a ServiceNow instance through unauthenticated code execution and expose its stored data. Exploitation has been associated with data-theft attacks. When chained with CVE-2024-4879 and CVE-2024-5178, the vulnerabilities can provide full database access, sensitive file access, and command execution on configured MID Servers inside customer networks. These broader outcomes are documented for the combined chain and should not all be attributed to CVE-2024-5217 alone.

Mitigation

If you can’t patch tonight, do this now.

Restrict network and application access to affected instances while patches are pending. Increase access-log monitoring and detection, configure suspicious-login alerts, and promptly investigate unusual activity. These controls reduce exposure or improve detection but are not a substitute for installing the applicable security fixes.

Remediation

Patch, then assume compromise.

Apply the vendor security patch or hotfix specifically addressing CVE-2024-5217 for the installed release. Listed fixed levels are Utah Patch 10 Hot Fix 3, Patch 10a Hot Fix 2, or Patch 10b Hot Fix 1; Vancouver Patch 6 Hot Fix 2, Patch 7 Hot Fix 3b, Patch 8 Hot Fix 4, Patch 9 Hot Fix 1, or Patch 10; and Washington DC Patch 1 Hot Fix 3b, Patch 2 Hot Fix 2, Patch 3 Hot Fix 2, Patch 4, or Patch 5. Confirm applicability against the vendor's CVE-specific guidance and verify that hosted instances received the update. Customer patches were applied during June 2024, with security updates also announced in July. Patching prevents future exploitation but does not remove an existing compromise; investigate suspected historical exploitation separately.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
ServicenowServicenowapplication
FAQ

Frequently asked questions

Is CVE-2024-5217 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Jul 29, 2024.
Is there a public exploit for CVE-2024-5217?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2024-5217.
Is there a patch for CVE-2024-5217?
Apply the vendor security patch or hotfix specifically addressing CVE-2024-5217 for the installed release. Listed fixed levels are Utah Patch 10 Hot Fix 3, Patch 10a Hot Fix 2, or Patch 10b Hot Fix 1; Vancouver Patch 6 Hot Fix 2, Patch 7 Hot Fix 3b, Patch 8 Hot Fix 4, Patch 9 Hot Fix 1, or Patch 10; and Washington DC Patch 1 Hot Fix 3b, Patch 2 Hot Fix 2, Patch 3 Hot Fix 2, Patch 4, or Patch 5.
What products are affected by CVE-2024-5217?
Servicenow.
How severe is CVE-2024-5217?
CVE-2024-5217 has a CVSS v4 score of 9.2 (Critical) and an EPSS score of 99.6% (100th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

16 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+10 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures6YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.