CVE-2022-43684 json
ACL bypass in Reporting functionality
published 2023-06-13 3 y ago modified 2026-06-17 4 mo ago also EUVD-2022-46677
- cvss
- 9.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 78%
- public exploits
- 0
- none known
Summary
ServiceNow has released patches and an upgrade that address an Access Control List (ACL) bypass issue in ServiceNow Core functionality.
Additional Details
This issue is present in the following supported ServiceNow releases:
* Quebec prior to Patch 10 Hot Fix 8b * Rome prior to Patch 10 Hot Fix 1 * San Diego prior to Patch 7 * Tokyo prior to Tokyo Patch 1; and * Utah prior to Utah General Availability
If this ACL bypass issue were to be successfully exploited, it potentially could allow an authenticated user to obtain sensitive information from tables missing authorization controls.
Patch / fix
- ServiceNow Now Platform Patch 7, Patch 10 Hot Fix 1, Patch 10 Hot Fix 8b, Tokyo Patch 1
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 22 mo ago
Exploit prediction
1.80% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.9 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected products
- ServiceNow Now Platform
Classification
References
-
support.servicenow.com
/kb?id=kb_article_view&sysparm_article=KB1303489
vendor-advisory
- seclists.org /fulldisclosure/2023/Jul/11
- news.ycombinator.com /item?id=36638530
- x64.sh /posts/ServiceNow-Insecure-access-control-to-admin/
- packetstormsecurity.com /files/173354/ServiceNow-Insecure-Access-Control-Full-Admin-Compromise.html
Sources
- CVE List CVE-2022-43684
- NVD CVE-2022-43684
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.