CVE-2021-33204 Vulnerability Analysis & Exploit Details

CVE-2021-33204
Vulnerability Scoring

9.8
/10
Critical Risk

As a catastrophic security flaw, CVE-2021-33204 has severe implications, demanding immediate intervention.

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: None
    No user interaction is necessary for exploitation.

CVE-2021-33204 Details

Status: Modified

Last updated: 🕕 21 Nov 2024, 06:08 UTC
Originally published on: 🕔 19 May 2021, 17:15 UTC

Time between publication and last update: 1281 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2021-33204 Vulnerability Summary

CVE-2021-33204: In the pg_partman (aka PG Partition Manager) extension before 4.5.1 for PostgreSQL, arbitrary code execution can be achieved via SECURITY DEFINER functions because an explicit search_path is not set.

Assessing the Risk of CVE-2021-33204

Access Complexity Graph

The exploitability of CVE-2021-33204 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-2021-33204

With low attack complexity and no required privileges, CVE-2021-33204 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-2021-33204, 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-2021-33204, 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-2021-33204 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2021-33204 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2021-33204 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.429% (probability of exploit)

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

CVE-2021-33204 References

External References

CWE Common Weakness Enumeration

NVD-CWE-noinfo

Vulnerable Configurations

  • cpe:2.3:a:pgxn:pg_partman:-:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:-:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:0.1.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:0.1.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:0.1.2:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:0.1.2:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:0.2.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:0.2.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:0.3.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:0.3.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:0.3.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:0.3.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:0.3.2:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:0.3.2:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:0.4.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:0.4.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:0.4.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:0.4.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:0.4.2:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:0.4.2:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:1.0.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:1.0.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:1.1.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:1.1.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:1.2.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:1.2.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:1.3.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:1.3.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:1.4.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:1.4.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:1.4.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:1.4.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:1.4.3:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:1.4.3:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:1.4.4:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:1.4.4:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:1.4.5:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:1.4.5:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:1.5.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:1.5.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:1.5.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:1.5.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:1.6.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:1.6.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:1.6.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:1.6.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:1.7.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:1.7.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:1.7.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:1.7.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:1.7.2:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:1.7.2:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:1.8.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:1.8.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:1.8.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:1.8.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:1.8.2:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:1.8.2:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:1.8.3:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:1.8.3:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:1.8.4:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:1.8.4:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:1.8.5:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:1.8.5:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:1.8.6:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:1.8.6:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:1.8.7:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:1.8.7:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:2.0.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:2.0.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:2.1.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:2.1.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:2.2.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:2.2.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:2.2.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:2.2.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:2.2.2:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:2.2.2:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:2.2.3:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:2.2.3:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:2.3.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:2.3.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:2.3.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:2.3.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:2.3.2:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:2.3.2:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:2.3.3:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:2.3.3:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:2.3.4:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:2.3.4:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:2.4.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:2.4.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:2.4.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:2.4.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:2.5.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:2.5.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:2.5.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:2.5.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:2.6.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:2.6.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:2.6.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:2.6.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:2.6.2:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:2.6.2:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:2.6.3:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:2.6.3:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:2.6.4:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:2.6.4:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:3.0.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:3.0.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:3.0.2:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:3.0.2:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:3.1.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:3.1.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:3.1.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:3.1.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:3.1.2:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:3.1.2:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:3.1.3:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:3.1.3:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:3.2.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:3.2.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:3.2.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:3.2.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:4.0.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:4.0.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:4.1.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:4.1.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:4.2.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:4.2.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:4.2.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:4.2.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:4.2.2:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:4.2.2:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:4.3.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:4.3.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:4.3.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:4.3.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:4.4.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:4.4.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:4.4.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:4.4.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgxn:pg_partman:4.5.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgxn:pg_partman:4.5.0:*:*:*:*:postgresql:*:*

Protect Your Infrastructure against CVE-2021-33204: 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-31203 – An integer overflow was addressed with improved input validation. This issue is fixed in macOS Sequoia 15.4, tvOS 18.4, iPadOS 17.7.6, macOS Sonoma...
  • CVE-2025-31202 – A null pointer dereference was addressed with improved input validation. This issue is fixed in iOS 18.4 and iPadOS 18.4, macOS Sequoia 15.4, tvOS ...
  • CVE-2025-31197 – The issue was addressed with improved checks. This issue is fixed in macOS Sequoia 15.4, tvOS 18.4, macOS Ventura 13.7.5, iPadOS 17.7.6, macOS Sono...
  • CVE-2025-30445 – A type confusion issue was addressed with improved checks. This issue is fixed in macOS Sequoia 15.4, tvOS 18.4, macOS Ventura 13.7.5, iPadOS 17.7....
  • CVE-2025-24271 – An access issue was addressed with improved access restrictions. This issue is fixed in macOS Sequoia 15.4, tvOS 18.4, macOS Ventura 13.7.5, iPadOS...