CVE-2022-43684 | ACL bypass in Reporting functionality

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.

Published: 2023-06-13 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-43684 is rated High Risk (67.7/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 1.80%). EPSS rose +1.60% over the last day, indicating growing attacker interest. High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-43684

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.20% 1.80% +1.60%
2 2026-03-04 0.14% 0.20% +0.06%
3 2026-03-01 — 0.14% —

Full EPSS history (40 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-43684

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.9 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.1 6.0 [email protected]
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 3.6 [email protected]

Weakness enumeration for CVE-2022-43684

Affected software / configurations for CVE-2022-43684

Vendor Product Version Raw CPE
servicenow servicenow quebec cpe:2.3:a:servicenow:servicenow:quebec:patch_1_hotfix_1:*:*:*:*:*:*
servicenow servicenow quebec cpe:2.3:a:servicenow:servicenow:quebec:patch_10:*:*:*:*:*:*
servicenow servicenow quebec cpe:2.3:a:servicenow:servicenow:quebec:patch_10_hotfix_3:*:*:*:*:*:*
servicenow servicenow quebec cpe:2.3:a:servicenow:servicenow:quebec:patch_10_hotfix_3a:*:*:*:*:*:*
servicenow servicenow quebec cpe:2.3:a:servicenow:servicenow:quebec:patch_10_hotfix_3b:*:*:*:*:*:*
servicenow servicenow quebec cpe:2.3:a:servicenow:servicenow:quebec:patch_10_hotfix_4:*:*:*:*:*:*
servicenow servicenow quebec cpe:2.3:a:servicenow:servicenow:quebec:patch_2:*:*:*:*:*:*
servicenow servicenow quebec cpe:2.3:a:servicenow:servicenow:quebec:patch_2_hotfix_1:*:*:*:*:*:*
servicenow servicenow quebec cpe:2.3:a:servicenow:servicenow:quebec:patch_2_hotfix_2:*:*:*:*:*:*
servicenow servicenow quebec cpe:2.3:a:servicenow:servicenow:quebec:patch_3:*:*:*:*:*:*
servicenow servicenow quebec cpe:2.3:a:servicenow:servicenow:quebec:patch_4:*:*:*:*:*:*
servicenow servicenow quebec cpe:2.3:a:servicenow:servicenow:quebec:patch_4_hotfix_2:*:*:*:*:*:*
servicenow servicenow quebec cpe:2.3:a:servicenow:servicenow:quebec:patch_5:*:*:*:*:*:*
servicenow servicenow quebec cpe:2.3:a:servicenow:servicenow:quebec:patch_6:*:*:*:*:*:*
servicenow servicenow quebec cpe:2.3:a:servicenow:servicenow:quebec:patch_7:*:*:*:*:*:*
servicenow servicenow quebec cpe:2.3:a:servicenow:servicenow:quebec:patch_8:*:*:*:*:*:*
servicenow servicenow quebec cpe:2.3:a:servicenow:servicenow:quebec:patch_9:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_1:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_1_hotfix_1:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_1_hotfix_1a:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_1_hotfix_1b:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_1_hotfix_2:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_1_hotfix_3:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_10:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_2:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_2_hotfix_1:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_2_hotfix_2:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_3:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_3_hotfix_1:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_4:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_4_hotfix_1:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_4_hotfix_1a:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_4_hotfix_1b:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_5:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_5_hotfix_1:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_5_hotfix_2:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_6:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_6_hotfix_1:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_6_hotfix_2:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_7:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_7_hotfix_1:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_7a:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_7b:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_8:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_8_hotfix_1:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_8_hotfix_2:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_9:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_9_hotfix_1:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_9a:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_9b:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_1:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_1_hotfix_1:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_1_hotfix_1a:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_1_hotfix_1b:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_10_hotfix_1:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_10_hotfix_1a:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_10_hotfix_1b:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_10_hotfix_2:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_10_hotfix_2b:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_2:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_2_hotfix_1:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_3:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_3_hotfix_1:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_3_hotfix_2:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_3_hotfix_3:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_3_hotfix_4:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_4:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_4a:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_4b:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_5:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_6:*:*:*:*:*:*
servicenow servicenow tokyo cpe:2.3:a:servicenow:servicenow:tokyo:-:*:*:*:*:*:*
servicenow servicenow utah cpe:2.3:a:servicenow:servicenow:utah:-:*:*:*:*:*:*

References for CVE-2022-43684

cvelogic Threat Intelligence