Cyber Resilience

CVE-2024-5217

Servicenow utah … washington_dc

CISA KEVActive ExploitationEUVD Exploited
Published
10 July 2024
Modified
03 November 2025
KEV Added
29 July 2024
Patch / advisory
CVSS Score v4 9.2
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.99 99.9th percentile
Risk Priority 75 floored blend · peak EPSS

Summary

CVE-2024-5217 is a critical-severity Incomplete List of Disallowed Inputs (CWE-184) vulnerability in Servicenow Servicenow. Its CVSS base score is 9.2 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 0.1% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

ServiceNow addressed an input validation vulnerability present in its Now Platform releases Washington DC, Vancouver, and earlier. The flaw, tracked as CVE-2024-5217, permits remote code execution in the context of the platform and carries a CVSS 4.0 score of 9.2.

An unauthenticated attacker with network access can supply crafted input to trigger arbitrary code execution without user interaction or elevated privileges. The associated CWEs (184 and 697) point to failures in input validation and equivalence checks that allow the malicious payload to reach execution.

ServiceNow’s June 2024 security patches and hot fixes resolve the issue; the vendor’s KB articles KB1644293 and KB1648313 list the specific fixed builds and urge customers to apply the relevant updates immediately. Public references also note active exploitation attempts against unpatched instances.

EPSS scores remain elevated, with a current value of 0.9411 and a recorded peak of 0.9616, indicating sustained exploitation interest since disclosure.

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
KEV Date Added
29 July 2024

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1027 Obfuscated Files or Information Stealth
Adversaries may attempt to make an executable or file difficult to discover or analyze by encrypting, encoding, or otherwise obfuscating its contents on the system or in transit.
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-4879Same product: Servicenow Servicenowboth on KEV
CVE-2024-8923Same product: Servicenow Servicenow
CVE-2024-8924Same product: Servicenow Servicenow
CVE-2023-1298Same product: Servicenow Servicenow
CVE-2023-1209Same product: Servicenow Servicenow
CVE-2020-5849Shared CWE-697both on KEV
CVE-2024-28246Shared CWE-184, CWE-697
CVE-2023-23844Shared CWE-184, CWE-697
CVE-2023-45133Shared CWE-184, CWE-697
CVE-2023-40037Shared CWE-184, CWE-697

Affected Assets

servicenow
servicenow
utah, vancouver, washington_dc

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 2 hardening rules · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)
  • V3.5.2
  • V4.4.2
  • V16.2.5

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation directly exercises security-relevant comparisons to discover incorrect logic.

SI-10 requires validity checks on inputs, which structurally replaces incomplete deny-lists with complete allow-list or sanitization logic.

A reference monitor must be small and correct, structurally limiting the chance of flawed comparison logic in authorization decisions.

Security engineering principles require correct implementation of comparison logic used for access and authentication decisions.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require complete, positive input validation instead of incomplete denylists.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can discover missing input checks, but does not prevent the weakness during development.

prevents

Secure development lifecycle includes code review and testing that can catch incorrect comparison logic.

prevents

Application security requirements can mandate complete input validation rules, but the control itself does not prescribe how to build those rules.

prevents

Secure architecture principles include robust input validation design, yet the control is broader than this single weakness.

prevents

Secure coding standards directly require exhaustive allow-lists or complete deny-lists for inputs, addressing the root cause of incomplete disallowed-input lists.

degrades

Secure authentication mechanisms rely on correct comparison of credentials or tokens.

References