Jelly Template Injection Vulnerability in ServiceNow UI Macros
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- Fix
- Fixed in Utah Patch 10 Hot Fix 3, Utah Patch 10a Hot Fix 2, Vancouver Patch 6 Hot Fix 2, Vancouver Patch 7 Hot Fix 3b, Vancouver Patch 8 Hot Fix 4, and 6 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
ServiceNow's Now Platform, specifically the Vancouver and Washington DC releases, is affected by a flaw in how it validates input in UI Macros. An unauthenticated remote attacker could exploit this to run arbitrary code within the Now Platform environment.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
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.
Timeline
- CVE published
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CISA remediation deadline
Due date for US federal agencies to patch
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- ServiceNow Now Platform
fixed in Utah Patch 10 Hot Fix 3; fixed in Utah Patch 10a Hot Fix 2; fixed in Vancouver Patch 6 Hot Fix 2; fixed in Vancouver Patch 7 Hot Fix 3b; fixed in Vancouver Patch 8 Hot Fix 4; fixed in Vancouver Patch 9; fixed in Vancouver Patch 10; fixed in Washington DC Patch 1 Hot Fix 2b; fixed in Washington DC Patch 2 Hot Fix 2; fixed in Washington DC Patch 3 Hot Fix 1; fixed in Washington DC Patch 4