CVE-2022-43565 Vulnerability Analysis & Exploit Details

CVE-2022-43565
Vulnerability Scoring

8.1
/10
Severe Risk

Cybersecurity professionals consider CVE-2022-43565 an immediate threat requiring urgent 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: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: Required
    User interaction is necessary for successful exploitation.

CVE-2022-43565 Details

Status: Modified

Last updated: 🕖 21 Nov 2024, 07:26 UTC
Originally published on: 🕚 04 Nov 2022, 23:15 UTC

Time between publication and last update: 747 days

CVSS Release: version 3

CVSS3 Source

prodsec@splunk.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2022-43565 Vulnerability Summary

CVE-2022-43565: In Splunk Enterprise versions below 8.2.9 and 8.1.12, the way that the ‘tstats command handles Javascript Object Notation (JSON) lets an attacker bypass SPL safeguards for risky commands https://docs.splunk.com/Documentation/SplunkCloud/latest/Security/SPLsafeguards . The vulnerability requires the attacker to phish the victim by tricking them into initiating a request within their browser.

Assessing the Risk of CVE-2022-43565

Access Complexity Graph

The exploitability of CVE-2022-43565 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-43565

With low attack complexity and no required privileges, CVE-2022-43565 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

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-43565, 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-43565, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2022-43565 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2022-43565 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: None
    CVE-2022-43565 does not impact system 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.197% (probability of exploit)

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

CVE-2022-43565 References

External References

CWE Common Weakness Enumeration

NVD-CWE-Other

Vulnerable Configurations

  • cpe:2.3:a:splunk:splunk:8.1.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:8.1.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:8.1.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:8.1.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:8.1.2:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:8.1.2:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:8.1.4:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:8.1.4:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:8.1.5:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:8.1.5:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:8.1.6:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:8.1.6:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:8.1.7:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:8.1.7:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:8.2.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:8.2.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:-:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:-:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:8.1.2103:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:8.1.2103:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:8.2.2105:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:8.2.2105:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:8.2.2106:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:8.2.2106:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:8.2.2107:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:8.2.2107:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:8.2.2109:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:8.2.2109:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:8.2.2111:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:8.2.2111:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:8.2.2112:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:8.2.2112:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:8.2.2201:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:8.2.2201:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:8.2.2202:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:8.2.2202:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_cloud_platform:8.2.2203:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_cloud_platform:8.2.2203:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2022-43565: 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-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...
  • CVE-2025-2126 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla and classified as critical. This issue affects some unknown processing of the...