Cleartext Storage of OAuth Credentials in ServiceNow AI Platform
- 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 Xanadu Patch 11 Hot Fix 7a, Yokohama Patch 13 Hot Fix 4a, Zurich Patch 10 Hot Fix 3a, Zurich Patch 11 Hot Fix 1, Zurich Patch 11m (m-branch), 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
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
The ServiceNow AI Platform is affected by a flaw that can store users' passwords in plain, unencrypted text within a system table. This could allow someone who is not authorized to see those passwords to access them.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
ServiceNow has remediated an information disclosure vulnerability that was identified in the ServiceNow AI Platform. This vulnerability could cause a user's plaintext password to be persisted in a system table, potentially exposing that password to a user who otherwise would not be entitled to view it. ServiceNow remediated the vulnerability through security updates that address the unintended persistence of plaintext credentials. We are not currently aware of malicious exploitation against ServiceNow instances. We recommend customers promptly apply appropriate updates or upgrade to a patched release if they have not already done so.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- ServiceNow ServiceNow AI Platform
fixed in Xanadu Patch 11 Hot Fix 7a; fixed in Yokohama Patch 13 Hot Fix 4a; fixed in Zurich Patch 10 Hot Fix 3a; fixed in Zurich Patch 11 Hot Fix 1; fixed in Zurich Patch 11m (m-branch); fixed in Zurich Patch 12; fixed in Zurich Patch 13; fixed in Australia Patch 2 Hot Fix 3b; fixed in Australia Patch 4 Hot Fix 1; fixed in Australia Patch 4m (m-branch); fixed in Australia Patch 5