Skip to main content
Mallory
MediumVulnerability

CVE-2024-5178: Sensitive file read in ServiceNow SecurelyAccess API

Published Jul 10, 2024 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.9Medium · v4
EPSS33.6%98th percentile
CISA KEVNoNot listed
In the wildReported3 exploitation records in Mallory
IdentifiersCVE-2024-5178CWE-184 · Incomplete List of Disallowed Inputs

CVE-2024-5178 is an incomplete input validation vulnerability in the SecurelyAccess API of ServiceNow Now Platform releases Washington DC, Vancouver, and Utah. Insufficient validation of file access requests allows an administrative user to bypass restrictions and read sensitive files on the web application server. The vulnerability is a post-authentication file disclosure issue; unauthenticated compromise requires chaining it with separate vulnerabilities.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An attacker with administrative privileges can obtain sensitive server files that should remain inaccessible through the application. Disclosure can expose confidential configuration information and credentials, potentially supporting further compromise. Arbitrary code execution, full database access, and command execution on configured MID Servers are broader exploit-chain outcomes, not established standalone effects of this vulnerability.

Mitigation

If you can’t patch tonight, do this now.

No vulnerability-specific alternative workaround is documented. Apply the relevant security patches or hotfixes promptly. As defense-in-depth measures, restrict access to affected instances, enforce least privilege for administrative accounts, and increase access-log monitoring and suspicious-login detection. Investigate evidence of prior exploitation rather than treating patch installation as sufficient incident remediation.

Remediation

Patch, then assume compromise.

Install a vendor-designated fixed patch or hotfix for the affected release family. Utah: Patch 10 Hot Fix 3, Patch 10a Hot Fix 2, or Patch 10b Hot Fix 1. Vancouver: Patch 6 Hot Fix 2, Patch 7 Hot Fix 3b, Patch 8 Hot Fix 4, Patch 9 Hot Fix 1, or Patch 10. Washington DC: Patch 1 Hot Fix 3b, Patch 2 Hot Fix 2, Patch 3 Hot Fix 2, or Patch 4. Subsequent cumulative releases include these fixes. Patching prevents future exploitation but does not remediate an existing compromise.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2024-5178 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2024-5178?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2024-5178.
Is there a patch for CVE-2024-5178?
Install a vendor-designated fixed patch or hotfix for the affected release family. Utah: Patch 10 Hot Fix 3, Patch 10a Hot Fix 2, or Patch 10b Hot Fix 1.
How severe is CVE-2024-5178?
CVE-2024-5178 has a CVSS v4 score of 6.9 (Medium) and an EPSS score of 33.6% (98th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.