CVE-2022-2625 Vulnerability Analysis & Exploit Details

CVE-2022-2625
Vulnerability Scoring

8.0
/10
Very High Risk

Highly exploitable, CVE-2022-2625 poses a critical security risk that could lead to severe breaches.

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-2625 Details

Status: Modified

Last updated: 🕖 21 Nov 2024, 07:01 UTC
Originally published on: 🕖 18 Aug 2022, 19:15 UTC

Time between publication and last update: 825 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:R/S:U/C:H/I:H/A:H

CVE-2022-2625 Vulnerability Summary

CVE-2022-2625: A vulnerability was found in PostgreSQL. This attack requires permission to create non-temporary objects in at least one schema, the ability to lure or wait for an administrator to create or update an affected extension in that schema, and the ability to lure or wait for a victim to use the object targeted in CREATE OR REPLACE or CREATE IF NOT EXISTS. Given all three prerequisites, this flaw allows an attacker to run arbitrary code as the victim role, which may be a superuser.

Assessing the Risk of CVE-2022-2625

Access Complexity Graph

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

CVE-2022-2625 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-2625, 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-2625, 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-2625 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2022-2625 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2022-2625 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

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

EPSS Score: 0.231% (probability of exploit)

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

CVE-2022-2625 References

External References

CWE Common Weakness Enumeration

CWE-1321

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.
  • Exploiting Incorrectly Configured Access Control Security Levels CAPEC-180 An attacker exploits a weakness in the configuration of access controls and is able to bypass the intended protection that these measures guard against and thereby obtain unauthorized access to the system or network. Sensitive functionality should always be protected with access controls. However configuring all but the most trivial access control systems can be very complicated and there are many opportunities for mistakes. If an attacker can learn of incorrectly configured access security settings, they may be able to exploit this in an attack.
  • Manipulating User-Controlled Variables CAPEC-77 This attack targets user controlled variables (DEBUG=1, PHP Globals, and So Forth). An adversary can override variables leveraging user-supplied, untrusted query variables directly used on the application server without any data sanitization. In extreme cases, the adversary can change variables controlling the business logic of the application. For instance, in languages like PHP, a number of poorly set default configurations may allow the user to override variables.

Vulnerable Configurations

  • cpe:2.3:a:postgresql:postgresql:10.0:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:10.0:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:10.1:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:10.1:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:10.2:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:10.2:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:10.3:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:10.3:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:10.4:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:10.4:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:10.5:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:10.5:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:10.6:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:10.6:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:10.7:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:10.7:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:10.8:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:10.8:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:10.9:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:10.9:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:10.10:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:10.10:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:10.11:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:10.11:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:10.12:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:10.12:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:10.13:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:10.13:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:10.14:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:10.14:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:10.15:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:10.15:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:10.16:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:10.16:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:10.17:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:10.17:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:10.18:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:10.18:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:10.19:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:10.19:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:10.20:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:10.20:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:10.21:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:10.21:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:11.0:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:11.0:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:11.1:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:11.1:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:11.2:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:11.2:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:11.3:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:11.3:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:11.4:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:11.4:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:11.5:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:11.5:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:11.6:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:11.6:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:11.7:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:11.7:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:11.8:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:11.8:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:11.9:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:11.9:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:11.10:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:11.10:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:11.11:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:11.11:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:11.12:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:11.12:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:11.13:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:11.13:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:11.14:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:11.14:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:11.15:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:11.15:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:11.16:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:11.16:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:12.0:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:12.0:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:12.1:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:12.1:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:12.2:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:12.2:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:12.3:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:12.3:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:12.4:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:12.4:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:12.5:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:12.5:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:12.6:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:12.6:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:12.7:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:12.7:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:12.8:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:12.8:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:12.9:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:12.9:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:12.10:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:12.10:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:12.11:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:12.11:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:13.0:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:13.0:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:13.1:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:13.1:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:13.2:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:13.2:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:13.3:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:13.3:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:13.4:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:13.4:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:13.5:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:13.5:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:13.6:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:13.6:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:13.7:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:13.7:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:14.0:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:14.0:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:14.1:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:14.1:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:14.2:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:14.2:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:14.3:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:14.3:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:14.4:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:14.4:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:15:beta1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:15:beta1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:15:beta2:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:15:beta2:*:*:*:*:*:*
  • cpe:2.3:o:fedoraproject:fedora:36:*:*:*:*:*:*:*
    cpe:2.3:o:fedoraproject:fedora:36:*:*:*:*:*:*:*
  • cpe:2.3:o:redhat:enterprise_linux:6.0:*:*:*:*:*:*:*
    cpe:2.3:o:redhat:enterprise_linux:6.0:*:*:*:*:*:*:*
  • cpe:2.3:o:redhat:enterprise_linux:7.0:*:*:*:*:*:*:*
    cpe:2.3:o:redhat:enterprise_linux:7.0:*:*:*:*:*:*:*
  • cpe:2.3:o:redhat:enterprise_linux:8.0:*:*:*:*:*:*:*
    cpe:2.3:o:redhat:enterprise_linux:8.0:*:*:*:*:*:*:*
  • cpe:2.3:o:redhat:enterprise_linux:9.0:*:*:*:*:*:*:*
    cpe:2.3:o:redhat:enterprise_linux:9.0:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2022-2625: 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-43903 – NSSCryptoSignBackend.cc in Poppler before 25.04.0 does not verify the adbe.pkcs7.sha1 signatures on documents, resulting in potential signature forgeries.
  • CVE-2025-3796 – A vulnerability classified as critical has been found in PHPGurukul Men Salon Management System 1.0. This affects an unknown part of the file /admi...
  • CVE-2025-32953 – z80pack is a mature emulator of multiple platforms with 8080 and Z80 CPU. In version 1.38 and prior, the `makefile-ubuntu.yml` workflow file uses `...
  • CVE-2025-29058 – An issue in Qimou CMS v.3.34.0 allows a remote attacker to execute arbitrary code via the upgrade.php component.
  • CVE-2024-53591 – An issue in the login page of Seclore v3.27.5.0 allows attackers to bypass authentication via a brute force attack.