CVE-2024-5217
CRITICALCISA KEVEPSS 100th pctlDescription
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.
How to fix
Actively exploited, no published fix found yet
CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Federal remediation due: 2024-08-19
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Exploit Intelligence
Very high risk: more likely to be exploited than 100% of all known CVEs.
ServiceNow Incomplete List of Disallowed Inputs Vulnerability
ServiceNow Washington DC, Vancouver, and earlier Now Platform releases contain an incomplete list of disallowed inputs vulnerability in the GlideExpression script. An unauthenticated user could exploit this vulnerability to execute code remotely.
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Remediation due: 2024-08-19
References
Related Vulnerabilities
Other CWE-184 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2022-43396 | High | 8.8 | 55% | - | Fix |
| CVE-2017-7525 | Critical | 9.8 | 38% | - | Fix |
| CVE-2024-5178 | Medium | 4.9 | 34% | - | - |
| CVE-2018-7489 | Critical | 9.8 | 20% | - | Fix |
| CVE-2018-6383 | High | 8.8 | 13% | - | - |
| CVE-2024-32152 | Low | 3.1 | 12% | - | - |
Common questions
How do I fix CVE-2024-5217?
No published fix for CVE-2024-5217 has been found yet. It is on the CISA Known Exploited Vulnerabilities list; federal agencies must remediate by 2024-08-19. Apply the vendor's mitigations per CISA's guidance.
Is CVE-2024-5217 being actively exploited?
Yes. CVE-2024-5217 is listed in the CISA Known Exploited Vulnerabilities catalog, which means exploitation has been observed in the wild. US federal agencies were required to remediate it by 2024-08-19. Treat it as a priority whatever its CVSS score says.
How severe is CVE-2024-5217?
CVE-2024-5217 has a CVSS v3 base score of 9.8, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2024-5217
Markdown
[](https://tridentstack.com/cve/CVE-2024-5217)HTML
<a href="https://tridentstack.com/cve/CVE-2024-5217"><img src="https://tridentstack.com/cve/badge/CVE-2024-5217.svg" alt="CVE-2024-5217"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2025-11-03.