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

> Unauthenticated attackers can remotely execute code in ServiceNow Now Platform due to incomplete input validation in GlideExpression Script.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Yes, since 29 Jul 2024 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2024
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-5xx6-pf4v-cpf2

## What is CVE-2024-5217?

CVE-2024-5217 is a critical code injection vulnerability in ServiceNow Now Platform, published on 10 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

Weakness: CWE-697 (Incorrect Comparison), CWE-184 (Incomplete List of Disallowed Inputs)

## Which versions are affected by CVE-2024-5217?

It affects 1 product.


Products: Servicenow Servicenow.

## How do I fix CVE-2024-5217?

No fix has been published for CVE-2024-5217 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 19 Aug 2024.

## Is CVE-2024-5217 being exploited?

Yes. Attackers have exploited CVE-2024-5217 in the wild since at least 29 Jul 2024.

Public exploit code:

- ServiceNow - Incomplete Input Validation (nuclei): http/cves/2024/CVE-2024-5217.yaml

## Other vulnerabilities in ServiceNow Now Platform

- [CVE-2024-4879](https://insights.sbomify.com/CVE-2024-4879/): ServiceNow Improper Input Validation (critical 9.3, exploited in the wild)
- [CVE-2022-43684](https://insights.sbomify.com/CVE-2022-43684/): ACL bypass in Reporting functionality (critical 9.9)
- [CVE-2024-8923](https://insights.sbomify.com/CVE-2024-8923/): Sandbox Escape in Now Platform (critical 9.3)
- [CVE-2018-7748](https://insights.sbomify.com/CVE-2018-7748/): Code injection in n/a (high 8.8)
- [CVE-2024-8924](https://insights.sbomify.com/CVE-2024-8924/): Unauthenticated Blind SQL Injection in Core Platform (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-5217 and fix it if it is affected.

What it is: CVE-2024-5217 is a critical code injection vulnerability in ServiceNow Now Platform, published on 10 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2024-5217 in the wild since at least 29 Jul 2024.

Affected product: ServiceNow Now Platform. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-5217/ (Markdown: https://insights.sbomify.com/CVE-2024-5217/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-5217
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-5217
- OSV: https://osv.dev/vulnerability/CVE-2024-5217

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-5217/
Summaries are generated and may contain mistakes; the official description above is the record.