CVE-2024-0985VulnerabilityPublished 22 Feb 2024Updated 11 Oct 2026

SUSE · security update for postgresql

Affects SUSESource GCVE Database

Not known to be exploited · patch available : update SUSE when convenient.

Data as of 26 Oct 2026, 06:26 UTC

Severity

Low

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 1.8% chance of exploitation in 30 days – higher than 78% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Feb 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Red Hatredhat/postgresql`pkg:rpm/redhat/postgresql`Other threats	Affected >=9.2	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Red Hat has released official security updates addressing CVE-2024-0985 for PostgreSQL packages in Red Hat Enterprise Linux 9 and Red Hat Software Collections for RHEL 7. Users should apply these updates promptly following Red Hat's guidance at https://access.redhat.com/articles/11258. The PostgreSQL service will be automatically restarted after the update to ensure the fix is applied. No additional mitigation steps are required beyond applying the official patches.

Description

This security update provides a functional equivalent of RHSA-2024:0950. The original Red Hat(R) advisory is available from the Red Hat web site at https://access.redhat.com/errata/RHSA-2024:0950.

Impact

An attacker with non-owner database privileges could exploit this vulnerability to execute arbitrary SQL commands, potentially leading to unauthorized data access or modification. This elevates the risk of privilege escalation within the database environment. The severity is rated as high by Red Hat, reflecting the significant risk posed by unauthorized SQL execution.

Summary

CVE-2024-0985 is a vulnerability in PostgreSQL where a non-owner user executing the 'REFRESH MATERIALIZED VIEW CONCURRENTLY' command can run arbitrary SQL. This flaw is classified under CWE-271 (Improper Privilege Management). Red Hat has issued security advisories RHSA-2024:0950 and RHSA-2024:0988 providing updated PostgreSQL packages for Red Hat Enterprise Linux 9 and Red Hat Software Collections for RHEL 7, respectively. The updates fix the vulnerability by restricting unauthorized SQL execution via this command. The PostgreSQL service is automatically restarted upon update installation to apply the fix.

CWE-271Privilege Dropping / Lowering Errors (opens in a new tab)
Class weaknessLikelihood of exploit: High
The product does not drop privileges before passing control of a resource to an actor that does not have those privileges.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
Architecture and Design · Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design · Separation of Privilege
Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Aug 2026, 17:43 UTC

WeaknessesCWE-271

Technical details

References

Community reviews

Related threats