CVE Vulnerabilities

CVE-2022-43684

Exposure of Sensitive Information to an Unauthorized Actor

Published: Jun 13, 2023 | Modified: Nov 21, 2024
CVSS 3.x
6.5
MEDIUM
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu

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.

Weakness

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Affected Software

Name Vendor Start Version End Version
Servicenow Servicenow quebec-patch_1_hotfix_1 (including) quebec-patch_1_hotfix_1 (including)
Servicenow Servicenow quebec-patch_10 (including) quebec-patch_10 (including)
Servicenow Servicenow quebec-patch_10_hotfix_3 (including) quebec-patch_10_hotfix_3 (including)
Servicenow Servicenow quebec-patch_10_hotfix_3a (including) quebec-patch_10_hotfix_3a (including)
Servicenow Servicenow quebec-patch_10_hotfix_3b (including) quebec-patch_10_hotfix_3b (including)
Servicenow Servicenow quebec-patch_10_hotfix_4 (including) quebec-patch_10_hotfix_4 (including)
Servicenow Servicenow quebec-patch_2 (including) quebec-patch_2 (including)
Servicenow Servicenow quebec-patch_2_hotfix_1 (including) quebec-patch_2_hotfix_1 (including)
Servicenow Servicenow quebec-patch_2_hotfix_2 (including) quebec-patch_2_hotfix_2 (including)
Servicenow Servicenow quebec-patch_3 (including) quebec-patch_3 (including)
Servicenow Servicenow quebec-patch_4 (including) quebec-patch_4 (including)
Servicenow Servicenow quebec-patch_4_hotfix_2 (including) quebec-patch_4_hotfix_2 (including)
Servicenow Servicenow quebec-patch_5 (including) quebec-patch_5 (including)
Servicenow Servicenow quebec-patch_6 (including) quebec-patch_6 (including)
Servicenow Servicenow quebec-patch_7 (including) quebec-patch_7 (including)
Servicenow Servicenow quebec-patch_8 (including) quebec-patch_8 (including)
Servicenow Servicenow quebec-patch_9 (including) quebec-patch_9 (including)
Servicenow Servicenow rome-patch_1 (including) rome-patch_1 (including)
Servicenow Servicenow rome-patch_1_hotfix_1 (including) rome-patch_1_hotfix_1 (including)
Servicenow Servicenow rome-patch_1_hotfix_1a (including) rome-patch_1_hotfix_1a (including)
Servicenow Servicenow rome-patch_1_hotfix_1b (including) rome-patch_1_hotfix_1b (including)
Servicenow Servicenow rome-patch_1_hotfix_2 (including) rome-patch_1_hotfix_2 (including)
Servicenow Servicenow rome-patch_1_hotfix_3 (including) rome-patch_1_hotfix_3 (including)
Servicenow Servicenow rome-patch_10 (including) rome-patch_10 (including)
Servicenow Servicenow rome-patch_2 (including) rome-patch_2 (including)
Servicenow Servicenow rome-patch_2_hotfix_1 (including) rome-patch_2_hotfix_1 (including)
Servicenow Servicenow rome-patch_2_hotfix_2 (including) rome-patch_2_hotfix_2 (including)
Servicenow Servicenow rome-patch_3 (including) rome-patch_3 (including)
Servicenow Servicenow rome-patch_3_hotfix_1 (including) rome-patch_3_hotfix_1 (including)
Servicenow Servicenow rome-patch_4 (including) rome-patch_4 (including)
Servicenow Servicenow rome-patch_4_hotfix_1 (including) rome-patch_4_hotfix_1 (including)
Servicenow Servicenow rome-patch_4_hotfix_1a (including) rome-patch_4_hotfix_1a (including)
Servicenow Servicenow rome-patch_4_hotfix_1b (including) rome-patch_4_hotfix_1b (including)
Servicenow Servicenow rome-patch_5 (including) rome-patch_5 (including)
Servicenow Servicenow rome-patch_5_hotfix_1 (including) rome-patch_5_hotfix_1 (including)
Servicenow Servicenow rome-patch_5_hotfix_2 (including) rome-patch_5_hotfix_2 (including)
Servicenow Servicenow rome-patch_6 (including) rome-patch_6 (including)
Servicenow Servicenow rome-patch_6_hotfix_1 (including) rome-patch_6_hotfix_1 (including)
Servicenow Servicenow rome-patch_6_hotfix_2 (including) rome-patch_6_hotfix_2 (including)
Servicenow Servicenow rome-patch_7 (including) rome-patch_7 (including)
Servicenow Servicenow rome-patch_7_hotfix_1 (including) rome-patch_7_hotfix_1 (including)
Servicenow Servicenow rome-patch_7a (including) rome-patch_7a (including)
Servicenow Servicenow rome-patch_7b (including) rome-patch_7b (including)
Servicenow Servicenow rome-patch_8 (including) rome-patch_8 (including)
Servicenow Servicenow rome-patch_8_hotfix_1 (including) rome-patch_8_hotfix_1 (including)
Servicenow Servicenow rome-patch_8_hotfix_2 (including) rome-patch_8_hotfix_2 (including)
Servicenow Servicenow rome-patch_9 (including) rome-patch_9 (including)
Servicenow Servicenow rome-patch_9_hotfix_1 (including) rome-patch_9_hotfix_1 (including)
Servicenow Servicenow rome-patch_9a (including) rome-patch_9a (including)
Servicenow Servicenow rome-patch_9b (including) rome-patch_9b (including)
Servicenow Servicenow san_diego-patch_1 (including) san_diego-patch_1 (including)
Servicenow Servicenow san_diego-patch_1_hotfix_1 (including) san_diego-patch_1_hotfix_1 (including)
Servicenow Servicenow san_diego-patch_1_hotfix_1a (including) san_diego-patch_1_hotfix_1a (including)
Servicenow Servicenow san_diego-patch_1_hotfix_1b (including) san_diego-patch_1_hotfix_1b (including)
Servicenow Servicenow san_diego-patch_10_hotfix_1 (including) san_diego-patch_10_hotfix_1 (including)
Servicenow Servicenow san_diego-patch_10_hotfix_1a (including) san_diego-patch_10_hotfix_1a (including)
Servicenow Servicenow san_diego-patch_10_hotfix_1b (including) san_diego-patch_10_hotfix_1b (including)
Servicenow Servicenow san_diego-patch_10_hotfix_2 (including) san_diego-patch_10_hotfix_2 (including)
Servicenow Servicenow san_diego-patch_10_hotfix_2b (including) san_diego-patch_10_hotfix_2b (including)
Servicenow Servicenow san_diego-patch_2 (including) san_diego-patch_2 (including)
Servicenow Servicenow san_diego-patch_2_hotfix_1 (including) san_diego-patch_2_hotfix_1 (including)
Servicenow Servicenow san_diego-patch_3 (including) san_diego-patch_3 (including)
Servicenow Servicenow san_diego-patch_3_hotfix_1 (including) san_diego-patch_3_hotfix_1 (including)
Servicenow Servicenow san_diego-patch_3_hotfix_2 (including) san_diego-patch_3_hotfix_2 (including)
Servicenow Servicenow san_diego-patch_3_hotfix_3 (including) san_diego-patch_3_hotfix_3 (including)
Servicenow Servicenow san_diego-patch_3_hotfix_4 (including) san_diego-patch_3_hotfix_4 (including)
Servicenow Servicenow san_diego-patch_4 (including) san_diego-patch_4 (including)
Servicenow Servicenow san_diego-patch_4a (including) san_diego-patch_4a (including)
Servicenow Servicenow san_diego-patch_4b (including) san_diego-patch_4b (including)
Servicenow Servicenow san_diego-patch_5 (including) san_diego-patch_5 (including)
Servicenow Servicenow san_diego-patch_6 (including) san_diego-patch_6 (including)
Servicenow Servicenow tokyo (including) tokyo (including)
Servicenow Servicenow utah (including) utah (including)

Extended Description

There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:

Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:

Information exposures can occur in different ways:

It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References