CVE-2023-31136 Vulnerability Analysis & Exploit Details

CVE-2023-31136
Vulnerability Scoring

3.7
/10
Moderate Risk

Exploiting CVE-2023-31136 requires specific conditions, leading to a moderate security impact.

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: 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-2023-31136 Details

Status: Modified

Last updated: 🕗 21 Nov 2024, 08:01 UTC
Originally published on: 🕑 09 May 2023, 14:15 UTC

Time between publication and last update: 561 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2023-31136 Vulnerability Summary

CVE-2023-31136: PostgresNIO is a Swift client for PostgreSQL. Any user of PostgresNIO prior to version 1.14.2 connecting to servers with TLS enabled is vulnerable to a man-in-the-middle attacker injecting false responses to the client's first few queries, despite the use of TLS certificate verification and encryption. The vulnerability is addressed in PostgresNIO versions starting from 1.14.2. There are no known workarounds for unpatched users.

Assessing the Risk of CVE-2023-31136

Access Complexity Graph

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

CVE-2023-31136 presents a challenge to exploit due to its high attack complexity, but the absence of privilege requirements still makes it a viable target for skilled attackers. A thorough security review is advised.

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

  • Confidentiality: Low
    CVE-2023-31136 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: None
    CVE-2023-31136 poses no threat to data integrity.
  • Availability: None
    CVE-2023-31136 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.199% (probability of exploit)

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

CVE-2023-31136 References

External References

CWE Common Weakness Enumeration

CWE-522

CAPEC Common Attack Pattern Enumeration and Classification

  • Session Sidejacking CAPEC-102 Session sidejacking takes advantage of an unencrypted communication channel between a victim and target system. The attacker sniffs traffic on a network looking for session tokens in unencrypted traffic. Once a session token is captured, the attacker performs malicious actions by using the stolen token with the targeted application to impersonate the victim. This attack is a specific method of session hijacking, which is exploiting a valid session token to gain unauthorized access to a target system or information. Other methods to perform a session hijacking are session fixation, cross-site scripting, or compromising a user or server machine and stealing the session token.
  • Signature Spoofing by Key Theft CAPEC-474 An attacker obtains an authoritative or reputable signer's private signature key by theft and then uses this key to forge signatures from the original signer to mislead a victim into performing actions that benefit the attacker.
  • Password Recovery Exploitation CAPEC-50 An attacker may take advantage of the application feature to help users recover their forgotten passwords in order to gain access into the system with the same privileges as the original user. Generally password recovery schemes tend to be weak and insecure.
  • Kerberoasting CAPEC-509 Through the exploitation of how service accounts leverage Kerberos authentication with Service Principal Names (SPNs), the adversary obtains and subsequently cracks the hashed credentials of a service account target to exploit its privileges. The Kerberos authentication protocol centers around a ticketing system which is used to request/grant access to services and to then access the requested services. As an authenticated user, the adversary may request Active Directory and obtain a service ticket with portions encrypted via RC4 with the private key of the authenticated account. By extracting the local ticket and saving it disk, the adversary can brute force the hashed value to reveal the target account credentials.
  • Modify Existing Service CAPEC-551 When an operating system starts, it also starts programs called services or daemons. Modifying existing services may break existing services or may enable services that are disabled/not commonly used.
  • Remote Services with Stolen Credentials CAPEC-555 This pattern of attack involves an adversary that uses stolen credentials to leverage remote services such as RDP, telnet, SSH, and VNC to log into a system. Once access is gained, any number of malicious activities could be performed.
  • Use of Known Domain Credentials CAPEC-560 An adversary guesses or obtains (i.e. steals or purchases) legitimate credentials (e.g. userID/password) to achieve authentication and to perform authorized actions under the guise of an authenticated user or service.
  • Windows Admin Shares with Stolen Credentials CAPEC-561 An adversary guesses or obtains (i.e. steals or purchases) legitimate Windows administrator credentials (e.g. userID/password) to access Windows Admin Shares on a local machine or within a Windows domain.
  • Credential Stuffing CAPEC-600 An adversary tries known username/password combinations against different systems, applications, or services to gain additional authenticated access. Credential Stuffing attacks rely upon the fact that many users leverage the same username/password combination for multiple systems, applications, and services.
  • Use of Captured Hashes (Pass The Hash) CAPEC-644 An adversary obtains (i.e. steals or purchases) legitimate Windows domain credential hash values to access systems within the domain that leverage the Lan Man (LM) and/or NT Lan Man (NTLM) authentication protocols.
  • Use of Captured Tickets (Pass The Ticket) CAPEC-645 An adversary uses stolen Kerberos tickets to access systems/resources that leverage the Kerberos authentication protocol. The Kerberos authentication protocol centers around a ticketing system which is used to request/grant access to services and to then access the requested services. An adversary can obtain any one of these tickets (e.g. Service Ticket, Ticket Granting Ticket, Silver Ticket, or Golden Ticket) to authenticate to a system/resource without needing the account's credentials. Depending on the ticket obtained, the adversary may be able to access a particular resource or generate TGTs for any account within an Active Directory Domain.
  • Use of Known Kerberos Credentials CAPEC-652 An adversary obtains (i.e. steals or purchases) legitimate Kerberos credentials (e.g. Kerberos service account userID/password or Kerberos Tickets) with the goal of achieving authenticated access to additional systems, applications, or services within the domain.
  • Use of Known Operating System Credentials CAPEC-653 An adversary guesses or obtains (i.e. steals or purchases) legitimate operating system credentials (e.g. userID/password) to achieve authentication and to perform authorized actions on the system, under the guise of an authenticated user or service. This applies to any Operating System.

Vulnerable Configurations

  • cpe:2.3:a:vapor:postgresnio:-:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:-:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.0.0:-:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.0.0:-:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.0.0:rc.1:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.0.0:rc.1:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.0.0:rc.1.1:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.0.0:rc.1.1:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.0.0:rc.1.2:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.0.0:rc.1.2:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.0.0:rc.2:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.0.0:rc.2:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.0.0:beta.2:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.0.0:beta.2:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.0.0:beta.2.1:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.0.0:beta.2.1:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.0.0:beta.2.2:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.0.0:beta.2.2:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.0.0:beta.2.3:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.0.0:beta.2.3:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.0.0:beta.2.4:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.0.0:beta.2.4:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.0.0:beta.2.5:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.0.0:beta.2.5:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.0.0:beta.2.6:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.0.0:beta.2.6:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.0.0:beta.2.7:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.0.0:beta.2.7:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.0.0:beta.2.8:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.0.0:beta.2.8:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.0.0:beta.2.9:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.0.0:beta.2.9:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.0.0:beta.2.10:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.0.0:beta.2.10:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.0.0:alpha.1:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.0.0:alpha.1:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.0.0:alpha.1.1:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.0.0:alpha.1.1:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.0.0:alpha.1.2:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.0.0:alpha.1.2:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.0.0:alpha.1.3:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.0.0:alpha.1.3:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.0.0:alpha.1.4:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.0.0:alpha.1.4:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.0.0:alpha.1.5:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.0.0:alpha.1.5:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.0.0:alpha.1.6:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.0.0:alpha.1.6:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.0.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.0.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.1.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.1.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.1.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.1.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.2.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.2.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.2.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.2.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.2.2:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.2.2:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.3.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.3.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.3.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.3.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.4.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.4.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.4.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.4.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.4.2:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.4.2:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.4.3:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.4.3:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.4.4:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.4.4:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.5.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.5.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.5.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.5.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.5.2:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.5.2:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.6.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.6.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.6.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.6.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.6.2:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.6.2:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.6.3:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.6.3:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.6.4:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.6.4:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.6.5:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.6.5:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.7.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.7.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.7.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.7.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.7.2:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.7.2:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.8.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.8.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.9.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.9.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.10.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.10.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.11.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.11.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.11.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.11.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.12.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.12.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.12.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.12.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.13.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.13.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.14.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.14.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:vapor:postgresnio:1.14.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:vapor:postgresnio:1.14.1:*:*:*:*:postgresql:*:*

Protect Your Infrastructure against CVE-2023-31136: 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-3799 – A vulnerability, which was classified as critical, was found in WCMS 11. Affected is an unknown function of the file app/controllers/AnonymousContr...
  • CVE-2025-3798 – A vulnerability, which was classified as critical, has been found in WCMS 11. This issue affects the function sub of the file app/admin/AdvadminCon...
  • CVE-2025-3661 – The SB Chart block plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘className’ parameter in all versions up to, and inclu...
  • CVE-2025-3404 – The Download Manager plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the savePackage func...
  • CVE-2021-4455 – The Wordpress Plugin Smart Product Review plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in all v...