CVE-2024-5217 — ServiceNow Incomplete List of Disallowed Inputs Vulnerability
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Confirmed exploitation (CISA KEV)+35
- Public exploit/PoC (nuclei)+4
- EPSS 99.6% (30-day exploitation probability)+15
- Technical severity (critical)+10
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
CISA required action CISA
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
US federal deadline: Aug 19, 2024 — passed 787 day(s) ago
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (ServiceNow Now Platform, Servicenow Servicenow).
- Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- EPSS ahead of 100% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes matching the vulnerability class (logic error), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| ServiceNow | Now Platform |
< Utah Patch 10 Hot Fix 3< Utah Patch 10a Hot Fix 2< Utah Patch 10b Hot Fix 1< Vancouver Patch 6 Hot Fix 2< Vancouver Patch 7 Hot Fix 3b< Vancouver Patch 8 Hot Fix 4< Vancouver Patch 9 Hot Fix 1< Vancouver Patch 10 and 5 more< Washington DC Patch 1 Hot Fix 3b< Washington DC Patch 2 Hot Fix 2< Washington DC Patch 3 Hot Fix 2< Washington DC Patch 4< Washington DC Patch 5 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Servicenow | Servicenow |
version utahversion utah-early_availabilityversion utah-patch_1version utah-patch_1_hotfix_1version utah-patch_1_hotfix_1aversion utah-patch_1_hotfix_1bversion utah-patch_1_hotfix_2version utah-patch_10 and 91 moreversion utah-patch_10_hotfix_1version utah-patch_10_hotfix_2version utah-patch_10aversion utah-patch_10a_hotfix_1version utah-patch_10bversion utah-patch_2version utah-patch_2_hotfix_1version utah-patch_2_hotfix_2version utah-patch_2_hotfix_3version utah-patch_2_hotfix_4version utah-patch_3version utah-patch_3_hotfix_1version utah-patch_3_hotfix_1bversion utah-patch_4version utah-patch_4_hotfix_1version utah-patch_4_hotfix_2version utah-patch_4_hotfix_2aversion utah-patch_4_hotfix_2bversion utah-patch_4_hotfix_3version utah-patch_4_hotfix_3bversion utah-patch_4_hotfix_4version utah-patch_4_hotfix_4bversion utah-patch_4_hotfix_5version utah-patch_5version utah-patch_5_hotfix_1version utah-patch_6version utah-patch_6_hotfix_1version utah-patch_6_hotfix_2version utah-patch_7version utah-patch_7_hotfix_1version utah-patch_7_hotfix_2version utah-patch_7aversion utah-patch_7bversion utah-patch_8version utah-patch_8_hotfix_2version utah-patch_9version utah-patch_9_hotfix_1version utah-patch_9_hotfix_1aversion utah-patch_9_hotfix_1bversion vancouverversion vancouver-patch_1version vancouver-patch_1_hotfix_1version vancouver-patch_2version vancouver-patch_2_hotfix_1version vancouver-patch_2_hotfix_1aversion vancouver-patch_2_hotfix_2version vancouver-patch_2_hotfix_3version vancouver-patch_2_hotfix1aversion vancouver-patch_3version vancouver-patch_3_hotfix_1version vancouver-patch_3_hotfix_2version vancouver-patch_3_hotfix_3version vancouver-patch_3_hotfix_4version vancouver-patch_4version vancouver-patch_4_hotfix_1version vancouver-patch_4_hotfix_1aversion vancouver-patch_4_hotfix_1bversion vancouver-patch_4_hotfix_2bversion vancouver-patch_5version vancouver-patch_5_hotfix_1version vancouver-patch_6version vancouver-patch_6_hotfix_1version vancouver-patch_7version vancouver-patch_7_hotfix_1version vancouver-patch_7_hotfix_1aversion vancouver-patch_7_hotfix_2version vancouver-patch_7_hotfix_2aversion vancouver-patch_7_hotfix_2bversion vancouver-patch_7_hotfix_3aversion vancouver-patch_7_hotfix_4version vancouver-patch_7_hotifix_1aversion vancouver-patch_7_hotifix_1bversion vancouver-patch_7_hotifix_2aversion vancouver-patch_7_hotifix_2bversion vancouver-patch_8version vancouver-patch_8_hotfix_1version vancouver-patch_8_hotfix_2version vancouver-patch_8_hotfix_3version vancouver-patch_9version washington_dcversion washington_dc-patch_1version washington_dc-patch_1_hotfix_1version washington_dc-patch_1_hotfix_2version washington_dc-patch_1_hotfix_2aversion washington_dc-patch_1_hotfix_2bversion washington_dc-patch_2version washington_dc-patch_2_hotfix_1version washington_dc-patch_3version washington_dc-patch_3_hotfix_1version washington_dc-patch_4version washington_dc-patch_5 |
Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.2 | CVSS 4.0 | Critical | — | — | psirt@servicenow.com via NIST National Vulnerability Database |
| 9.2 | CVSS 4.0 | Critical | — | — | SN via CVE Program (cve.org) e CISA ADP |
| 9.8 | CVSS 3.1 | Critical | 3.9 | 5.9 | psirt@servicenow.com via NIST National Vulnerability Database |
| 9.8 | CVSS 3.1 | Critical | 3.9 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
| 9.8 | CVSS 3.1 | Critical | — | — | GitHub, Inc. via GitHub Security Advisories |
| 9.8 | CVSS 3.1 | Critical | — | — | SN via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CISA KEV details CISA
CISA lists a CVE once it has evidence of exploitation against real targets.
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.
Public exploits, PoCs and detection templates
Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.
Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.
EPSS over time FIRST
Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 99.63%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Hunt retroactively in logs from before Jul 29, 2024 (KEV listing): exploitation may have started earlier.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · servicenow/now platform
- SSVC assessment updated
- Record published
- Affected products added · servicenow/servicenow
- CVSS changed · 9.8
- Source status changed · → Analyzed
- Added to CISA KEV (detected)
- Record created in this database
- 2024
- Added to CISA KEV catalog
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 13, 2026 – Oct 13, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
6 on the record
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2024-4879 ServiceNow Improper Input Validation Vulnerability KEV Jul 10, 2024
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2024-5217 is "ServiceNow Incomplete List of Disallowed Inputs Vulnerability", rated Critical. It affects Now Platform (ServiceNow); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 9.8 describes technical severity. EPSS 99.63% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.