CVE-2024-10978 Vulnerability Analysis & Exploit Details

CVE-2024-10978
Vulnerability Scoring

4.2
/10
Medium Risk

The vulnerability CVE-2024-10978 could compromise system integrity but typically requires user interaction to be exploited.

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-2024-10978 Details

Status: Analyzed

Last updated: 🕞 20 Feb 2025, 15:41 UTC
Originally published on: 🕐 14 Nov 2024, 13:15 UTC

Time between publication and last update: 98 days

CVSS Release: version 3

CVSS3 Source

f86ef6dc-4d3a-42ad-8f28-e6d5547a5007

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2024-10978 Vulnerability Summary

CVE-2024-10978: Incorrect privilege assignment in PostgreSQL allows a less-privileged application user to view or change different rows from those intended. An attack requires the application to use SET ROLE, SET SESSION AUTHORIZATION, or an equivalent feature. The problem arises when an application query uses parameters from the attacker or conveys query results to the attacker. If that query reacts to current_setting('role') or the current user ID, it may modify or return data as though the session had not used SET ROLE or SET SESSION AUTHORIZATION. The attacker does not control which incorrect user ID applies. Query text from less-privileged sources is not a concern here, because SET ROLE and SET SESSION AUTHORIZATION are not sandboxes for unvetted queries. Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.

Assessing the Risk of CVE-2024-10978

Access Complexity Graph

The exploitability of CVE-2024-10978 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-2024-10978

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

  • Confidentiality: Low
    CVE-2024-10978 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: Low
    Exploiting CVE-2024-10978 may cause minor changes to data without severely impacting its accuracy.
  • Availability: None
    CVE-2024-10978 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.128% (probability of exploit)

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

CVE-2024-10978 References

External References

CWE Common Weakness Enumeration

NVD-CWE-noinfo

Vulnerable Configurations

  • 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:12.16:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:12.16:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:12.17:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:12.17:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:12.18:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:12.18:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:12.19:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:12.19:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:12.20:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:12.20:*:*:*:*:*:*:*
  • 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:13.12:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:13.12:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:13.13:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:13.13:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:13.14:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:13.14:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:13.15:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:13.15:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:13.16:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:13.16:*:*:*:*:*:*:*
  • 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:14.9:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:14.9:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:14.10:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:14.10:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:14.11:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:14.11:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:14.12:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:14.12:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:14.13:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:14.13:*:*:*:*:*:*:*
  • 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:postgresql:postgresql:15.4:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:15.4:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:15.5:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:15.5:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:15.6:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:15.6:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:15.7:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:15.7:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:15.8:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:15.8:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:16.0:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:16.0:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:16.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:16.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:16.1:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:16.1:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:16.2:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:16.2:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:16.3:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:16.3:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:16.4:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:16.4:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:17.0:-:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:17.0:-:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:17.0:beta1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:17.0:beta1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:17.0:beta2:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:17.0:beta2:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:17.0:beta3:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:17.0:beta3:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:17.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:17.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*
    cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2024-10978: 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...