Administrative file disclosure via path-filter bypass
Published Jul 10, 2024 · Updated Aug 1, 2024
Sensitive file read in ServiceNow Now Platform Utah, Vancouver, and Washington DC allows remote authenticated users to read server files. The SecurelyAccess path filter accepts a crafted name such as /co..nf/... before cleanup removes the embedded '..', yielding a restricted /conf/... path. Administrative access to an affected instance is required; successful exploitation discloses sensitive server files without altering data or interrupting service.
Summary
What happened
Sensitive file read in ServiceNow Now Platform Utah, Vancouver, and Washington DC allows remote authenticated users to read server files. The SecurelyAccess path filter accepts a crafted name such as /co..nf/... before cleanup removes the embedded '..', yielding a restricted /conf/... path. Administrative access to an affected instance is required; successful exploitation discloses sensitive server files without altering data or interrupting service.
The record
- CVE
- CVE-2024-5178
- Published
- Jul 10, 2024
- Updated
- Aug 1, 2024
- Vendor
- ServiceNow
- Product
- Now Platform
- Classifications
- CWE-184, T1005
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jul 10, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <Utah Patch 10a Hot Fix 2
- Affected versionversion=0 <Utah Patch 10b Hot Fix 1
- Affected versionversion=0 <Utah Patch 10 Hot Fix 3
- Affected versionversion=0 <Vancouver Patch 10
- Affected versionversion=0 <Vancouver Patch 6 Hot Fix 2
- Affected versionversion=0 <Vancouver Patch 7 Hot Fix 3b
- Affected versionversion=0 <Vancouver Patch 8 Hot Fix 4
- Affected versionversion=0 <Vancouver Patch 9 Hot Fix 1
- Affected versionversion=0 <Washington DC Patch 1 Hot Fix 3b
- Affected versionversion=0 <Washington DC Patch 2 Hot Fix 2
- Affected versionversion=0 <Washington DC Patch 3 Hot Fix 2
- Affected versionversion=0 <Washington DC Patch 4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- SecurelyAccess crafted-path file-read payloadfunctional · observed in use
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Reported exploitation
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo