CVE-2024-1713 | Plv8 Deferred Trigger Privilege Escalation

Exp

A user who can create objects in a database with plv8 3.2.1 installed is able to cause deferred triggers to execute as the Superuser during autovacuum.

Published: 2024-03-14 Last update: 2025-01-23 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2024-1713 is rated Exploit Available (51.2/100): CVSS High severity, with low exploitation likelihood (EPSS 0.07%). Core evidence: 1 public exploit reference(s) are indexed (Exploit-DB). Mandatory action: Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2024-1713

EDB-ID Source Kind Published Link
nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2024-1713

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-21 0.29% 0.07% -0.22%
2 2025-11-18 0.05% 0.29% +0.24%
3 2025-04-22 0.05%

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-1713

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.2 3.1 HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.3 5.3 [email protected]
7.2 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.2 5.9 [email protected]

Weakness enumeration for CVE-2024-1713

OS Trackers for CVE-2024-1713

vendor priority summary link
ubuntu medium CVE-2024-1713 medium priority: Ubuntu including 1 source packages (plv8), 10 status rows across 10 suites (bionic, focal, jammy, mantic, noble, oracular, plucky, questing, upstream, xenial): DNE 7, needs-triage 3. https://ubuntu.com/security/CVE-2024-1713

Affected software / configurations for CVE-2024-1713

Vendor Product Version Raw CPE
plv8 plv8 3.2.1 cpe:2.3:a:plv8:plv8:3.2.1:*:*:*:*:*:*:*

References for CVE-2024-1713

cvelogic Threat Intelligence