CVE-2024-4879
CVE-2024-4879 is a security flaw in ServiceNow Utah, Vancouver, and Washington DC Now Platform. Attackers can run their own code on ServiceNow Utah, Vancouver, and Washington DC Now Platform from anywhere, without logging in. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 29 Jul 2024.[1]
ServiceNow Utah, Vancouver, and Washington DC Now Platform is business software or equipment. Most families won’t have it, but attackers break into it to get inside companies, and from there to what those companies hold about their customers, patients and staff. Fixed in version Utah Patch 10 Hot Fix 3, Utah Patch 10a Hot Fix 2, Vancouver Patch 6 Hot Fix 2 and Vancouver Patch 7 Hot Fix 3b and others of Now Platform.
Description
CISA calls it an improper input validation in ServiceNow Utah, Vancouver, and Washington DC Now Platform. In its words: “ServiceNow Utah, Vancouver, and Washington DC Now Platform releases contain a jelly template injection vulnerability in UI macros. An unauthenticated user could exploit this vulnerability to execute code remotely.”[1]
The CVE record adds: “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.”[2]
The underlying weakness is CWE-1287, in MITRE’s list of common software weaknesses.
It scores 9.8 out of 10 on the Common Vulnerability Scoring System, which rates it critical, scored by NVD using CVSS 3.1.[2]
Affected versions
NVD’s record lists these fixed versions: in each line, everything before the version shown is affected.[2]
| Product | Fixed in |
|---|---|
| Now Platform | Utah Patch 10 Hot Fix 3 |
| Now Platform | Utah Patch 10a Hot Fix 2 |
| Now Platform | Vancouver Patch 6 Hot Fix 2 |
| Now Platform | Vancouver Patch 7 Hot Fix 3b |
| Now Platform | Vancouver Patch 8 Hot Fix 4 |
| Now Platform | Vancouver Patch 9 |
| Now Platform | Vancouver Patch 10 |
| Now Platform | Washington DC Patch 1 Hot Fix 2b |
Most families won’t have ServiceNow Utah, Vancouver, and Washington DC Now Platform; it’s for whoever looks after IT at work.
Exploitation
CISA added it to its catalog of known exploited vulnerabilities on 29 Jul 2024, 19 days after it was made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 19 Aug 2024 to fix it.[1]
FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at over 99%. That’s in the top 1% of the flaws it scores.[4]
CISA assesses it as automatable: attackers can run it against many targets at once.
CISA doesn’t say who was attacked, or how.
Fix
ServiceNow has published a fix or advice.[3] CISA’s required action: “Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.”[1]
- Check whether you use it.ServiceNow Utah, Vancouver, and Washington DC Now Platform is business software or equipment, so most families won’t have it. If you run a business, or work from home on company equipment, ask whoever looks after your IT.
- Send this page to your IT person.Ask them to confirm it’s fixed (fixed in version Utah Patch 10 Hot Fix 3, Utah Patch 10a Hot Fix 2, Vancouver Patch 6 Hot Fix 2 and Vancouver Patch 7 Hot Fix 3b and others of Now Platform), or not in use. CISA gave US government agencies until 19 Aug 2024 to fix it.
- If it can’t be fixed, take it offline.CISA’s advice when there’s no fix is to stop using the product, or take it off the internet, until there is one.
You can’t fix someone else’s server, but you can watch for what follows a break-in like this: a breach notice, a password reset you didn’t ask for, or a scam message that knows things it shouldn’t. HARD watches for those for you and your family.
Timeline
| Date | Event |
|---|---|
| The flaw is made public in the National Vulnerability Database, with a severity score of 9.8.[2] | |
| CISA adds it to its catalog of flaws known to be used in attacks.[1] | |
| CISA’s deadline for US government agencies to fix it.[1] | |
| FIRST puts the odds of it being used in attacks in the next 30 days at over 99%.[4] |
See also
Other ServiceNow Utah, Vancouver, and Washington DC Now Platform flaws
- CVE-2024-5217: incomplete list of disallowed inputs ·
Added the same day
- CVE-2024-5217, ServiceNow Utah, Vancouver, and Washington DC Now Platform: incomplete list of disallowed inputs ·
- CVE-2023-45249, Acronis Cyber Infrastructure (ACI): insecure default password ·
References
- ^ Cybersecurity and Infrastructure Security Agency. “ServiceNow Improper Input Validation Vulnerability”. Known Exploited Vulnerabilities Catalog, added 29 Jul 2024.
- ^ National Institute of Standards and Technology. “CVE-2024-4879 Detail”. National Vulnerability Database, published 10 Jul 2024.
- ^ ServiceNow. Advisories and fixes: support.servicenow.com.
- ^ FIRST. “Exploit Prediction Scoring System”. EPSS 1.000, percentile 100.0, 31 Oct 2026.
- CVE Program. “CVE-2024-4879”. The official CVE record.
This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.