dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 19 Aug 2024.
ServicenowApplication

CVE-2024-5217

CRITICAL · 9.8 CVSS v3.1 Published 2024-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

ServiceNow Now Platform contains an input validation vulnerability that allows unauthenticated remote code execution in the context of the platform. This critical flaw affects Washington DC, Vancouver, and earlier releases, enabling attackers to execute arbitrary code without credentials.

MitigationApply the June 2024 security patches and hot fixes released by ServiceNow for affected Washington DC, Vancouver, and earlier Now Platform releases immediately.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ServicenowApplication
Affected:= utah= vancouver= washington_dc

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify your ServiceNow platform version
    Log into the ServiceNow instance as an administrator. Navigate to System Definition > System Properties, or check the 'About' page (usually via the gear icon > About). Locate the 'Release' or 'Version' field which displays the platform release name (e.g., Washington DC, Vancouver, Utah).
    Affected if The displayed release name is Washington DC, Vancouver, or Utah (any Utah release).
  2. Confirm the specific version number
    In the same About or System Properties page, locate the build version or patch version number. ServiceNow versions are typically displayed as a date-coded release (e.g., WashDC-07-2024, Vancouver-01-2024, or a Utah build number).
    Affected if The version falls within the Washington DC, Vancouver, or Utah release families without the June 2024 security patches applied.
  3. Check for applied security patches
    Navigate to System Patch > Patch Set, or check the list of installed plugins and patches in the instance. Look for security patches released in June 2024 or later. ServiceNow security patches are typically identified by specific patch numbers in the patch history.
    Affected if No June 2024 security patch (or subsequent patch addressing this vulnerability) appears in the installed patches list.
  4. Verify instance accessibility
    Determine if the ServiceNow instance is exposed to the internet or accessible without VPN authentication. Check network/firewall settings to confirm whether the instance login page (login.do or login) is reachable from untrusted networks.
    Affected if The instance is publicly accessible via the internet and is running an unpatched affected version.

You are affected if your ServiceNow instance runs Washington DC, Vancouver, or Utah releases without the June 2024 security patches and is accessible to unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the June 2024 security patches and hot fixes released by ServiceNow for affected Washington DC, Vancouver, and earlier Now Platform releases immediately.

Fix this in Servicenow Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-5217 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-5217 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data