⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Critical · CVSS 9.2 ⚠ ACTIVELY EXPLOITED — CISA KEV

How to Fix CVE-2024-5217: Critical Vulnerability in Now Platform

Other vulnerabilities in the same area that are worth patching alongside this one:

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 9.2 - Critical
Actively exploited?Yes, listed in CISA KEV (added 2024-07-29)
Affected0 < Utah Patch 10 Hot Fix 3, 0 < Utah Patch 10a Hot Fix 2, 0 < Utah Patch 10b Hot Fix 1, 0 < Vancouver Patch 6 Hot Fix 2, 0 < Vancouver Patch 7 Hot Fix 3b, 0 < Vancouver Patch 8 Hot Fix 4, and others
Fixed inSee vendor advisory
Type (CWE)CWE-184: Incomplete List of Disallowed Inputs
Patch immediately. CISA's KEV listing means active exploitation is confirmed. Federal agencies must remediate by 2024-08-19.

What is CVE-2024-5217?

CVE-2024-5217 is a security flaw in Now Platform. 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.

Why this CVE matters

Unpatched network-facing software is the leading initial-access vector in public breach reporting. Treat any CVSS-9 class flaw on an internet-reachable system as urgent, regardless of whether public exploit code has been observed yet.

For deployments of Now Platform that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Confirmed in-the-wild exploitation makes that assumption mandatory, not cautious. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Open Now Platform's About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.

How to fix CVE-2024-5217

  1. Read the vendor advisory in full: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1648313
  2. Upgrade Now Platform to the patched build listed in the vendor advisory.
  3. Back up the configuration (and database, where applicable) before upgrading.
  4. Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
  5. Restart the affected service so the patched binary loads, then verify the new version (see verification section).

Patch via your OS package manager


# The exact package name and patched version are listed in the vendor advisory:
# https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1648313
# Debian / Ubuntu
sudo apt update
sudo apt install --only-upgrade nowplatform

# RHEL / Rocky / AlmaLinux / Fedora
sudo dnf upgrade nowplatform

# openSUSE
sudo zypper update nowplatform

# Verify the running version matches the fixed version
dpkg -s nowplatform 2>/dev/null | grep -i version || rpm -q nowplatform 2>/dev/null


# Windows: pull the cumulative update that ships this fix.
Install-Module PSWindowsUpdate -Force -SkipPublisherCheck
Get-WindowsUpdate -AcceptAll -Install -AutoReboot

Verify the fix landed


# 1. Confirm the running version matches the fixed-in version from the advisory:
#    https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1648313
#    Use the platform-specific version probe above.

# 2. Re-scan with your vulnerability scanner (Nessus, Qualys, Tenable, OpenVAS).
#    The scanner should no longer flag CVE-2024-5217 on the patched target.

# 3. Inspect recent service / kernel logs for crash loops or rollback events.
journalctl -u <service> --since "10 minutes ago"
dmesg --since "10 minutes ago"

If you cannot patch immediately

No official workaround exists beyond restricting network exposure to the affected component. Apply the vendor patch as the primary remediation.

How to verify the fix worked

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for log entries that do not match your normal request patterns, especially repeated requests to the same uncommon endpoint, and any administrative changes you cannot tie back to a known operator. Because Now Platform sits on CISA's Known Exploited Vulnerabilities catalog for this CVE, defenders should also pull the IOC list from the vendor advisory and from CISA's analysis if one was published.

Frequently asked questions

Is CVE-2024-5217 being exploited in the wild?

Yes. CISA added CVE-2024-5217 to the Known Exploited Vulnerabilities catalog, which means active exploitation has been confirmed by federal observation or credible vendor reporting.

Will a WAF or IDS rule fully mitigate CVE-2024-5217?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for Now Platform run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*