CVE-2021-45901 json
The password-reset form in ServiceNow Orlando provides different responses to invalid authentication attempts depending on whether the user…
published 2022-02-10 4 y ago modified 2026-06-17 4 mo ago also EUVD-2021-32616
- cvss
- 5.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 14.3%
- EPSS 14.3% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Exploit-DB
Summary
The password-reset form in ServiceNow Orlando provides different responses to invalid authentication attempts depending on whether the username exists.
Timeline
- Published
- First public exploit (EDB-50741)
Exploit prediction
14.32% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-50741 ServiceNow - Username Enumeration webapps, 2022-02-16
- trustwave.com https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/servicenow-username-enumeration-vulnerability-cve-2021-45901/ referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/165989/ServiceNow-Orlando-Username-Enumeration.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-203 Observable Discrepancy
References
-
trustwave.com
/en-us/resources/blogs/spiderlabs-blog/servicenow-username-enumeration-vulnerability-cve-2021-45901/
exploit, third-party-advisory
-
packetstormsecurity.com
/files/165989/ServiceNow-Orlando-Username-Enumeration.html
exploit, third-party-advisory
-
trustwave.com
/en-us/resources/security-resources/security-advisories/
vendor-advisory
Sources
- CVE List CVE-2021-45901
- NVD CVE-2021-45901
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.