CVE-2022-4289 Vulnerability Analysis & Exploit Details

CVE-2022-4289
Vulnerability Scoring

6.4
/10
High Risk

If left unpatched, CVE-2022-4289 could lead to major system disruptions or data loss.

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: Changed
    Successful exploitation can impact components beyond the vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2022-4289 Details

Status: Modified

Last updated: 🕢 21 Nov 2024, 07:34 UTC
Originally published on: 🕘 09 Mar 2023, 21:15 UTC

Time between publication and last update: 622 days

CVSS Release: version 3

CVSS3 Source

cve@gitlab.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2022-4289 Vulnerability Summary

CVE-2022-4289: An issue has been discovered in GitLab affecting all versions starting from 15.3 before 15.7.8, versions of 15.8 before 15.8.4, and version 15.9 before 15.9.2. Google IAP details in Prometheus integration were not hidden, could be leaked from instance, group, or project settings to other users.

Assessing the Risk of CVE-2022-4289

Access Complexity Graph

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

CVE-2022-4289 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-4289, 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-4289, 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-4289 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: Low
    Exploiting CVE-2022-4289 may cause minor changes to data without severely impacting its accuracy.
  • Availability: None
    CVE-2022-4289 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.079% (probability of exploit)

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

CVE-2022-4289 References

External References

CWE Common Weakness Enumeration

NVD-CWE-noinfo

Vulnerable Configurations

  • cpe:2.3:a:gitlab:gitlab:15.3.0:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.3.0:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.3.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.3.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.3.1:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.3.1:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.3.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.3.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.3.2:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.3.2:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.3.2:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.3.2:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.3.4:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.3.4:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.3.4:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.3.4:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.3.5:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.3.5:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.3.5:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.3.5:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.4:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.4:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.4:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.4:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.4.0:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.4.0:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.4.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.4.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.4.4:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.4.4:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.4.4:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.4.4:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.4.6:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.4.6:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.4.6:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.4.6:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.5.0:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.5.0:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.5.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.5.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.5.2:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.5.2:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.5.2:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.5.2:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.5.3:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.5.3:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.5.3:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.5.3:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.5.5:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.5.5:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.5.5:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.5.5:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.5.6:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.5.6:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.5.6:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.5.6:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.5.7:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.5.7:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.5.7:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.5.7:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.6.0:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.6.0:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.6.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.6.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.6.1:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.6.1:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.6.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.6.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.6.2:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.6.2:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.6.2:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.6.2:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.6.3:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.6.3:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.6.3:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.6.3:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.6.4:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.6.4:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.6.4:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.6.4:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.7.0:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.7.0:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.7.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.7.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.7.1:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.7.1:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.7.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.7.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.7.2:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.7.2:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.7.2:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.7.2:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.7.7:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.7.7:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.7.7:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.7.7:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.8.0:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.8.0:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.8.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.8.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.8.1:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.8.1:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.8.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.8.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.8.2:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.8.2:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.8.2:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.8.2:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.8.3:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.8.3:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.8.3:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.8.3:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.9.0:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.9.0:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.9.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.9.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.9.1:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.9.1:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:15.9.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:15.9.1:*:*:*:enterprise:*:*:*

Protect Your Infrastructure against CVE-2022-4289: 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-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...
  • CVE-2025-2125 – A vulnerability has been found in Control iD RH iD 25.2.25.0 and classified as problematic. This vulnerability affects unknown code of the file /v2...
  • CVE-2025-2124 – A vulnerability, which was classified as problematic, was found in Control iD RH iD 25.2.25.0. This affects an unknown part of the file /v2/custome...