Skip to content
Server Security Center
KEVcritical9.8

CVE-2024-4879: ServiceNow Improper Input Validation

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.9%
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-4879 explained

CVE-2024-4879 is an input validation vulnerability in the ServiceNow Now Platform, identified in the Vancouver and Washington DC releases. An unauthenticated remote user could execute code within the context of the Now Platform. CISA lists it as known to be exploited, so self-hosted and partner instances that lack the patches need urgent attention.

Impact

An attacker needs no credentials and no user interaction to exploit this over the network. Successful exploitation allows remote code execution within the Now Platform, with high impact on confidentiality, integrity and availability. CISA rates it as automatable with total technical impact. This means attackers can exploit it at scale and gain full control of the affected component. CISA's catalog lists it as known to be exploited. Ransomware use is marked as unknown.

Who is affected

The CVE record lists the ServiceNow Now Platform as affected in versions before Washington DC Patch 1 Hot Fix 2b, Washington DC Patch 2 Hot Fix 2, Washington DC Patch 3 Hot Fix 1, Washington DC Patch 4, Vancouver Patch 6 Hot Fix 2, Vancouver Patch 7 Hot Fix 3b, Vancouver Patch 8 Hot Fix 4 and Vancouver Patch 9. It also lists three further affected entries. Fixed versions include Utah Patch 10a Hot Fix 2, Utah Patch 10 Hot Fix 3, Vancouver Patch 10 and the Vancouver and Washington DC patches and hot fixes named above.

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 Vancouver and Washington DC Now Platform releases. This vulnerability could enable an unauthenticated user to remotely execute code within the context of the Now Platform. ServiceNow applied an update to hosted instances, and ServiceNow released the update to our partners and self-hosted customers.

Listed below are the patches and hot fixes that address the vulnerability. 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 2b
    • < Washington DC Patch 2 Hot Fix 2
    • < Washington DC Patch 3 Hot Fix 1
    • < Washington DC Patch 4
    • < Vancouver Patch 6 Hot Fix 2
    • < Vancouver Patch 7 Hot Fix 3b
    • < Vancouver Patch 8 Hot Fix 4
    • < Vancouver Patch 9
    • < Utah Patch 10 Hot Fix 3
    • < Vancouver Patch 10
    • < Utah Patch 10a Hot Fix 2
    Fixed in
    • Utah Patch 10a Hot Fix 2
    • 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
    • Vancouver Patch 10
    • Washington DC Patch 1 Hot Fix 2b
    • Washington DC Patch 2 Hot Fix 2
    • Washington DC Patch 3 Hot Fix 1
    • Washington DC Patch 4

How to fix it

  • Update to a fixed version: Utah Patch 10a Hot Fix 2, 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, Vancouver Patch 10, Washington DC Patch 1 Hot Fix 2b and 3 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 every self-hosted or partner-managed Now Platform instance.
  2. Apply the matching fixed patch or hot fix listed by ServiceNow, such as Washington DC Patch 4 or Vancouver Patch 9, as soon as possible.
  3. For Utah instances, apply Utah Patch 10 Hot Fix 3 or Utah Patch 10a Hot Fix 2.
  4. Restrict network access to instances that cannot be patched immediately. Follow the vendor advisory's mitigations.
  5. Review instances for signs of compromise, since the vulnerability is known to be exploited.
  6. Confirm that ServiceNow-hosted instances have received the vendor's update.

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-1287 Improper Validation of Specified Type of Input

Questions about CVE-2024-4879

Are ServiceNow-hosted instances affected?
ServiceNow states that it applied an update to hosted instances. It released the update to partners and self-hosted customers, who must apply the relevant patches or hot fixes themselves.
Is this vulnerability being exploited?
Yes. CISA added CVE-2024-4879 to its Known Exploited Vulnerabilities catalog on 2024-07-29. US federal agencies had a due date of 2024-08-19 to apply mitigations per vendor instructions or discontinue use.
Does an attacker need an account to exploit it?
No. The vulnerability can be exploited remotely by an unauthenticated user without user interaction. This leads to code execution within the Now Platform.

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.