CVE-2022-46886 Vulnerability Analysis & Exploit Details

CVE-2022-46886
Vulnerability Scoring

5.5
/10
Significant Risk

Security assessments indicate that CVE-2022-46886 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: Required
    User interaction is necessary for successful exploitation.

CVE-2022-46886 Details

Status: Modified

Last updated: 🕙 06 Feb 2025, 22:15 UTC
Originally published on: 🕗 14 Apr 2023, 20:15 UTC

Time between publication and last update: 664 days

CVSS Release: version 3

CVSS3 Source

psirt@servicenow.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L

CVE-2022-46886 Vulnerability Summary

CVE-2022-46886: There exists an open redirect within the response list update functionality of ServiceNow. This allows attackers to redirect users to arbitrary domains when clicking on a URL within a service-now domain.

Assessing the Risk of CVE-2022-46886

Access Complexity Graph

The exploitability of CVE-2022-46886 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2022-46886

CVE-2022-46886 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2022-46886, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2022-46886, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2022-46886 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: Low
    Exploiting CVE-2022-46886 may cause minor changes to data without severely impacting its accuracy.
  • Availability: Low
    CVE-2022-46886 may slightly degrade system performance without fully affecting service availability.

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.056% (probability of exploit)

EPSS Percentile: 26.69% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 73.31% of others.

CVE-2022-46886 References

External References

CWE Common Weakness Enumeration

CWE-601

CAPEC Common Attack Pattern Enumeration and Classification

  • Cross-Site Flashing CAPEC-178 An attacker is able to trick the victim into executing a Flash document that passes commands or calls to a Flash player browser plugin, allowing the attacker to exploit native Flash functionality in the client browser. This attack pattern occurs where an attacker can provide a crafted link to a Flash document (SWF file) which, when followed, will cause additional malicious instructions to be executed. The attacker does not need to serve or control the Flash document. The attack takes advantage of the fact that Flash files can reference external URLs. If variables that serve as URLs that the Flash application references can be controlled through parameters, then by creating a link that includes values for those parameters, an attacker can cause arbitrary content to be referenced and possibly executed by the targeted Flash application.

Vulnerable Configurations

  • cpe:2.3:a:servicenow:servicenow:quebec:-:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:quebec:-:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:quebec:patch_10:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:quebec:patch_10:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_1:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_1:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_1_hotfix_1:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_1_hotfix_1:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_1_hotfix_1b:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_1_hotfix_1b:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_1_hotfix_2:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_1_hotfix_2:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_1_hotfix_3:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_1_hotfix_3:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_10:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_10:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_10_hotfix_1:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_10_hotfix_1:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_10_hotfix_2:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_10_hotfix_2:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_10_hotfix_2a:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_10_hotfix_2a:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_2:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_2:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_2_hotfix_1:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_2_hotfix_1:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_2_hotfix_2:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_2_hotfix_2:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_3:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_3:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_3_hotfix_1:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_3_hotfix_1:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_4:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_4:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_4_hotfix_1:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_4_hotfix_1:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_4_hotfix_1a:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_4_hotfix_1a:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_4_hotfix_1b:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_4_hotfix_1b:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_5:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_5:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_5_hotfix_1:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_5_hotfix_1:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_5_hotfix_2:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_5_hotfix_2:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_6:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_6:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_6_hotfix_1:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_6_hotfix_1:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_6_hotfix_2:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_6_hotfix_2:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_7:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_7:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_7_hotfix_1:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_7_hotfix_1:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_7a:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_7a:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_7b:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_7b:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_8:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_8:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_8_hotfix_1:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_8_hotfix_1:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_8_hotfix_2:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_8_hotfix_2:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_9:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_9:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_9_hotfix_1:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_9_hotfix_1:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_9a:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_9a:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:rome:patch_9b:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:rome:patch_9b:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:san_diego:patch_1:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:san_diego:patch_1:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:san_diego:patch_1_hotfix_1:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:san_diego:patch_1_hotfix_1:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:san_diego:patch_1_hotfix_1a:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:san_diego:patch_1_hotfix_1a:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:san_diego:patch_1_hotfix_1b:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:san_diego:patch_1_hotfix_1b:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:san_diego:patch_2:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:san_diego:patch_2:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:san_diego:patch_2_hotfix_1:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:san_diego:patch_2_hotfix_1:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:san_diego:patch_3:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:san_diego:patch_3:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:san_diego:patch_3_hotfix_1:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:san_diego:patch_3_hotfix_1:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:san_diego:patch_3_hotfix_2:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:san_diego:patch_3_hotfix_2:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:san_diego:patch_3_hotfix_3:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:san_diego:patch_3_hotfix_3:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:san_diego:patch_3_hotfix_4:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:san_diego:patch_3_hotfix_4:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:san_diego:patch_4:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:san_diego:patch_4:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:san_diego:patch_4a:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:san_diego:patch_4a:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:san_diego:patch_4b:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:san_diego:patch_4b:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:san_diego:patch_6:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:san_diego:patch_6:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:san_diego:patch_7:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:san_diego:patch_7:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:san_diego:patch_8:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:san_diego:patch_8:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:tokyo:-:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:tokyo:-:*:*:*:*:*:*
  • cpe:2.3:a:servicenow:servicenow:tokyo:patch1:*:*:*:*:*:*
    cpe:2.3:a:servicenow:servicenow:tokyo:patch1:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2022-46886: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-2130 – A vulnerability was found in OpenXE up to 1.12. It has been declared as problematic. This vulnerability affects unknown code of the component Ticke...
  • CVE-2025-26205 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in mainpositionTV in ltable.c. NOTE: this is dispute...
  • CVE-2025-26204 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in equalkey in ltable.c. NOTE: this is disputed beca...
  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...