CVE-2022-0959 Vulnerability Analysis & Exploit Details

CVE-2022-0959
Vulnerability Scoring

6.5
/10
High Risk

If left unpatched, CVE-2022-0959 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: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2022-0959 Details

Status: Modified

Last updated: 🕡 21 Nov 2024, 06:39 UTC
Originally published on: 🕒 16 Mar 2022, 15:15 UTC

Time between publication and last update: 980 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2022-0959 Vulnerability Summary

CVE-2022-0959: A malicious, but authorised and authenticated user can construct an HTTP request using their existing CSRF token and session cookie to manually upload files to any location that the operating system user account under which pgAdmin is running has permission to write.

Assessing the Risk of CVE-2022-0959

Access Complexity Graph

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

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

  • Confidentiality: None
    CVE-2022-0959 has no significant impact on data confidentiality.
  • Integrity: High
    CVE-2022-0959 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: None
    CVE-2022-0959 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.057% (probability of exploit)

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

CVE-2022-0959 References

External References

CWE Common Weakness Enumeration

CWE-434

CAPEC Common Attack Pattern Enumeration and Classification

  • Accessing Functionality Not Properly Constrained by ACLs CAPEC-1 In applications, particularly web applications, access to functionality is mitigated by an authorization framework. This framework maps Access Control Lists (ACLs) to elements of the application's functionality; particularly URL's for web apps. In the case that the administrator failed to specify an ACL for a particular element, an attacker may be able to access it with impunity. An attacker with the ability to access functionality not properly constrained by ACLs can obtain sensitive information and possibly compromise the entire application. Such an attacker can access resources that must be available only to users at a higher privilege level, can access management sections of the application, or can run queries for data that they otherwise not supposed to.

Vulnerable Configurations

  • cpe:2.3:a:postgresql:pgadmin_4:-:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:-:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:1.0:-:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:1.0:-:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:1.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:1.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:1.0:beta1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:1.0:beta1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:1.0:beta2:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:1.0:beta2:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:1.0:beta3:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:1.0:beta3:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:1.0:beta4:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:1.0:beta4:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:1.1:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:1.2:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:1.3:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:1.3:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:1.4:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:1.4:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:1.5:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:1.5:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:1.6:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:1.6:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:2.0:-:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:2.0:-:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:2.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:2.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:2.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:2.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:2.1:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:3.0:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:3.1:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:3.2:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:3.3:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:3.3:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:3.4:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:3.4:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:3.5:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:3.5:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:3.6:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:3.6:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.0:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.1:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.2:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.3:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.3:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.4:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.4:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.5:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.5:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.6:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.6:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.7:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.7:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.8:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.8:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.9:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.9:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.10:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.10:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.11:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.11:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.12:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.12:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.13:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.13:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.14:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.14:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.15:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.15:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.16:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.16:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.17:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.17:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.18:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.18:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.19:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.19:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.20:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.20:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.21:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.21:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.22:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.22:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.23:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.23:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.24:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.24:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.25:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.25:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.26:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.26:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.27:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.27:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.28:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.28:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.29:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.29:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:4.30:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:4.30:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:5.0:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:5.1:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:5.2:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:5.2:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:5.3:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:5.3:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:5.4:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:5.4:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:5.5:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:5.5:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:5.6:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:5.6:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:5.7:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:5.7:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:6.0:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:6.1:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:6.2:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:6.2:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:6.3:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:6.3:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:6.4:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:6.4:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:6.5:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:6.5:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:pgadmin_4:6.6:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:pgadmin_4:6.6:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2022-0959: 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...