CVE-2023-39417 Vulnerability Analysis & Exploit Details

CVE-2023-39417
Vulnerability Scoring

7.5
/10
Very High Risk

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

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and 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-2023-39417 Details

Status: Modified

Last updated: 🕗 21 Nov 2024, 08:15 UTC
Originally published on: 🕐 11 Aug 2023, 13:15 UTC

Time between publication and last update: 467 days

CVSS Release: version 3

CVSS3 Source

secalert@redhat.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2023-39417 Vulnerability Summary

CVE-2023-39417: IN THE EXTENSION SCRIPT, a SQL Injection vulnerability was found in PostgreSQL if it uses @extowner@, @extschema@, or @extschema:...@ inside a quoting construct (dollar quoting, '', or ""). If an administrator has installed files of a vulnerable, trusted, non-bundled extension, an attacker with database-level CREATE privilege can execute arbitrary code as the bootstrap superuser.

Assessing the Risk of CVE-2023-39417

Access Complexity Graph

The exploitability of CVE-2023-39417 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-2023-39417

This vulnerability, CVE-2023-39417, requires a high level of attack complexity and low privileges, making it difficult but not impossible to exploit. Organizations should ensure robust security configurations to mitigate 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-2023-39417, 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-2023-39417, 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-2023-39417 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2023-39417 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2023-39417 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.411% (probability of exploit)

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

CVE-2023-39417 References

External References

CWE Common Weakness Enumeration

CWE-89

CAPEC Common Attack Pattern Enumeration and Classification

  • Command Line Execution through SQL Injection CAPEC-108 An attacker uses standard SQL injection methods to inject data into the command line for execution. This could be done directly through misuse of directives such as MSSQL_xp_cmdshell or indirectly through injection of data into the database that would be interpreted as shell commands. Sometime later, an unscrupulous backend application (or could be part of the functionality of the same application) fetches the injected data stored in the database and uses this data as command line arguments without performing proper validation. The malicious data escapes that data plane by spawning new commands to be executed on the host.
  • Object Relational Mapping Injection CAPEC-109 An attacker leverages a weakness present in the database access layer code generated with an Object Relational Mapping (ORM) tool or a weakness in the way that a developer used a persistence framework to inject their own SQL commands to be executed against the underlying database. The attack here is similar to plain SQL injection, except that the application does not use JDBC to directly talk to the database, but instead it uses a data access layer generated by an ORM tool or framework (e.g. Hibernate). While most of the time code generated by an ORM tool contains safe access methods that are immune to SQL injection, sometimes either due to some weakness in the generated code or due to the fact that the developer failed to use the generated access methods properly, SQL injection is still possible.
  • SQL Injection through SOAP Parameter Tampering CAPEC-110 An attacker modifies the parameters of the SOAP message that is sent from the service consumer to the service provider to initiate a SQL injection attack. On the service provider side, the SOAP message is parsed and parameters are not properly validated before being used to access a database in a way that does not use parameter binding, thus enabling the attacker to control the structure of the executed SQL query. This pattern describes a SQL injection attack with the delivery mechanism being a SOAP message.
  • Expanding Control over the Operating System from the Database CAPEC-470 An attacker is able to leverage access gained to the database to read / write data to the file system, compromise the operating system, create a tunnel for accessing the host machine, and use this access to potentially attack other machines on the same network as the database machine. Traditionally SQL injections attacks are viewed as a way to gain unauthorized read access to the data stored in the database, modify the data in the database, delete the data, etc. However, almost every data base management system (DBMS) system includes facilities that if compromised allow an attacker complete access to the file system, operating system, and full access to the host running the database. The attacker can then use this privileged access to launch subsequent attacks. These facilities include dropping into a command shell, creating user defined functions that can call system level libraries present on the host machine, stored procedures, etc.
  • SQL Injection CAPEC-66 This attack exploits target software that constructs SQL statements based on user input. An attacker crafts input strings so that when the target software constructs SQL statements based on the input, the resulting SQL statement performs actions other than those the application intended. SQL Injection results from failure of the application to appropriately validate input.
  • Blind SQL Injection CAPEC-7 Blind SQL Injection results from an insufficient mitigation for SQL Injection. Although suppressing database error messages are considered best practice, the suppression alone is not sufficient to prevent SQL Injection. Blind SQL Injection is a form of SQL Injection that overcomes the lack of error messages. Without the error messages that facilitate SQL Injection, the adversary constructs input strings that probe the target through simple Boolean SQL expressions. The adversary can determine if the syntax and structure of the injection was successful based on whether the query was executed or not. Applied iteratively, the adversary determines how and where the target is vulnerable to SQL Injection.

Vulnerable Configurations

  • 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:11.17:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:11.17:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:11.18:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:11.18:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:11.19:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:11.19:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:11.20:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:11.20:*:*:*:*:*:*:*
  • 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:12.12:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:12.12:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:12.13:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:12.13:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:12.14:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:12.14:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:12.15:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:12.15:*:*:*:*:*:*:*
  • 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:13.8:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:13.8:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:13.9:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:13.9:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:13.10:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:13.10:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:13.11:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:13.11:*:*:*:*:*:*:*
  • 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:14.5:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:14.5:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:14.6:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:14.6:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:14.7:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:14.7:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:14.8:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:14.8:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:15.0:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:15.0:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:15.1:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:15.1:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:15.2:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:15.2:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:15.3:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:15.3:*:*:*:*:*:*:*
  • cpe:2.3:a:redhat:software_collections:-:*:*:*:*:*:*:*
    cpe:2.3:a:redhat:software_collections:-:*:*:*:*:*:*:*
  • 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:*:*:*:*:*:*:*
  • cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:*
    cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:*
  • cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*
    cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*
  • cpe:2.3:o:debian:debian_linux:12.0:*:*:*:*:*:*:*
    cpe:2.3:o:debian:debian_linux:12.0:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2023-39417: 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-3284 – The User Registration & Membership – Custom Registration Form, Login Form, and User Profile plugin for WordPress is vulnerable to Cross-Site Reques...
  • CVE-2025-3278 – The UrbanGo Membership plugin for WordPress is vulnerable to privilege escalation in versions up to, and including, 1.0.4. This is due to the plugi...
  • CVE-2025-2010 – The JobWP – Job Board, Job Listing, Career Page and Recruitment Plugin plugin for WordPress is vulnerable to SQL Injection via the 'jobwp_upload_re...
  • 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...