Skip to content
Server Security Center
KEVcritical9.8

CVE-2024-5217: ServiceNow Incomplete List of Disallowed Inputs

ServiceNow Utah, Vancouver, and Washington DC Now Platform · listed in the CISA catalog of actively exploited vulnerabilities since 2024-07-29.

CVSS v3.1 (CVE record)
9.8
critical
EPSS (exploit probability, 30 days)
99.6%
among the highest 0.1% of all CVEs
Added to CISA KEV
2024-07-29
US federal due date 2024-08-19
Automatable (CISA SSVC)
yes
technical impact: total

CVE-2024-5217 explained

CVE-2024-5217 is an input validation flaw (CWE-184: Incomplete List of Disallowed Inputs) in the ServiceNow Now Platform, affecting the Washington DC, Vancouver and earlier releases. An unauthenticated user could remotely execute code within the context of the Now Platform. CISA lists it as known to be exploited, so unpatched instances face a serious risk.

Impact

An unauthenticated attacker can remotely execute code in the context of the Now Platform over the network. No user interaction is needed and the attack complexity is low. Confidentiality, integrity and availability are all highly affected. CISA rates the flaw as automatable, meaning attackers can exploit it at scale, with total technical impact. CISA also lists it as known to be exploited. Whether it has been used in ransomware campaigns is unknown.

Who is affected

The CVE record lists ServiceNow Now Platform releases in the Utah, Vancouver and Washington DC families. Examples are Washington DC versions before Washington DC Patch 4 and Vancouver versions before Vancouver Patch 8 Hot Fix 4. The record lists more affected items than shown here. Fixed versions include 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, 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 and Washington DC Patch 5.

Written with AI from the data on this page and checked against it automatically.

Official description

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.

CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • ServiceNow Now Platform
    Affected
    • < 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
    • < Vancouver Patch 6 Hot Fix 2
    • < Vancouver Patch 7 Hot Fix 3b
    • < Vancouver Patch 8 Hot Fix 4
    • < Vancouver Patch 9 Hot Fix 1
    • < Utah Patch 10 Hot Fix 3
    • < Vancouver Patch 10
    • < Utah Patch 10a Hot Fix 2
    • < Utah Patch 10b Hot Fix 1
    Fixed in
    • Utah Patch 10a Hot Fix 2
    • Utah Patch 10b Hot Fix 1
    • Utah Patch 10 Hot Fix 3
    • 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
    • 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

How to fix it

  • Update to a fixed version: Utah Patch 10a Hot Fix 2, Utah Patch 10b Hot Fix 1, Utah Patch 10 Hot Fix 3, 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 (see the table).
  • Vendor advisory: support.servicenow.com/kb
  • CISA's deadline for US federal agencies: 2024-08-19 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Identify the release, patch and hot fix level of each ServiceNow instance you run.
  2. Apply the fixed patch or hot fix for your release family, such as Washington DC Patch 5, Vancouver Patch 10 or Utah Patch 10 Hot Fix 3.
  3. Follow the ServiceNow advisory for the June 2024 patching cycle and its instructions for your instance.
  4. If mitigations are unavailable, discontinue use of the product, as CISA's required action states.
  5. Review instances for signs of compromise, since the vulnerability is known to be exploited.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-184 Incomplete List of Disallowed Inputs

Questions about CVE-2024-5217

Do attackers need credentials to exploit CVE-2024-5217?
No. The description states that an unauthenticated user could remotely execute code within the context of the Now Platform. The CVSS vector also shows that no privileges and no user interaction are required.
Is this vulnerability being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2024-07-29. US federal agencies had a due date of 2024-08-19. Known ransomware use is listed as unknown.
Which fixes address the issue?
ServiceNow released patches and hot fixes during the June 2024 patching cycle. Examples are Washington DC Patch 4, Vancouver Patch 10 and Utah Patch 10b Hot Fix 1. Apply the one that matches your release family.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.