ACL bypass in Reporting functionality
- 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? →
- Not listed in CISA KEV
- Fix
- Fixed in Patch 10 Hot Fix 8b, Patch 10 Hot Fix 1, Patch 7, Tokyo Patch 1
- 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
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
ServiceNow has released patches and an upgrade that address an Access Control List (ACL) bypass issue in ServiceNow Core functionality. Additional Details This issue is present in the following supported ServiceNow releases: • Quebec prior to Patch 10 Hot Fix 8b • Rome prior to Patch 10 Hot Fix 1 • San Diego prior to Patch 7 • Tokyo prior to Tokyo Patch 1; and • Utah prior to Utah General Availability If this ACL bypass issue were to be successfully exploited, it potentially could allow an authenticated user to obtain sensitive information from tables missing authorization controls.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- ServiceNow Now Platform
From Quebec · fixed in Patch 10 Hot Fix 8b; From Rome · fixed in Patch 10 Hot Fix 1; fixed in Patch 7; From Tokyo · fixed in Tokyo Patch 1