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-4879

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 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.

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

An input validation vulnerability in ServiceNow's Now Platform (Vancouver and Washington DC releases) allows unauthenticated remote code execution. Attackers can execute arbitrary code within the platform context without any credentials due to insufficient input validation.

MitigationApply the relevant security patches or hot fixes provided by ServiceNow for your instance version immediately, as patches are available through official channels.

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 instance version
    Log into the ServiceNow instance and navigate to System Properties > General or check the login page footer which typically displays the release version (e.g., Vancouver, Washington DC, Utah). Alternatively, query the system via the API endpoint /api/now/table/sys_properties with name='glide.version' to retrieve the version programmatically.
    Affected if The instance version is Vancouver or Washington DC (not Utah or later) as these are the affected releases listed in the CVE.
  2. Confirm the instance is directly accessible over the network
    Verify that the ServiceNow instance is reachable via HTTP/HTTPS from external networks or untrusted contexts. This can be tested by attempting to access the instance URL from a non-internal network or by reviewing network firewall rules and access control lists.
    Affected if The instance is externally accessible without proper network segmentation, as the vulnerability allows unauthenticated remote code execution.
  3. Check if Scripted REST APIs or Scripted Web Services are enabled
    Navigate to System Web Services > Scripted REST APIs or System Web Services > Scripted Web Services in the ServiceNow navigation pane. Review whether any APIs are exposed and whether they process user-supplied input without validation.
    Affected if Scripted endpoints that accept unauthenticated input are active and processing data without proper input validation, which is the attack vector for this RCE vulnerability.
  4. Review ACLs on exposed endpoints
    Navigate to System Security > Access Control (ACL) and review the ACL rules for endpoints under /api/ now/ paths. Check if unauthenticated access is permitted on script execution endpoints.
    Affected if ACLs allow unauthenticated or roles=public access to endpoints that execute server-side scripts, creating the condition for unauthenticated RCE.

If the ServiceNow instance runs Vancouver or Washington DC releases AND has externally accessible endpoints with unauthenticated script execution capabilities enabled, the environment is likely affected by CVE-2024-4879.

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 relevant security patches or hot fixes provided by ServiceNow for your instance version immediately, as patches are available through official channels.

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-4879 — 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-4879 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