Incomplete Input Validation in SecurelyAccess API
- 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 Utah Patch 10 Hot Fix 3, Utah Patch 10a Hot Fix 2, Utah Patch 10b Hot Fix 1, Vancouver Patch 6 Hot Fix 2, Vancouver Patch 7 Hot Fix 3b, and 7 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
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
ServiceNow has addressed a sensitive file read vulnerability that was identified in the Washington DC, Vancouver, and Utah Now Platform releases. This vulnerability could allow an administrative user to gain unauthorized access to sensitive files on the web application server. The vulnerability is addressed in the listed patches and hot fixes, 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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- 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 Utah Patch 10b Hot Fix 1; 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 Hot Fix 1; fixed in Vancouver Patch 10; fixed in Washington DC Patch 1 Hot Fix 3b; fixed in Washington DC Patch 2 Hot Fix 2; fixed in Washington DC Patch 3 Hot Fix 2; fixed in Washington DC Patch 4