# CVE-2024-1713: Plv8 Deferred Trigger Privilege Escalation

> A user with object creation rights can escalate privileges to Superuser via deferred triggers during autovacuum in the plv8 extension.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Mar 2024
- **Updated:** 2 Aug 2024
- **Also known as:** UBUNTU-CVE-2024-1713

## What is CVE-2024-1713?

CVE-2024-1713 is a high-severity vulnerability in Plv8, published on 14 Mar 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions), CWE-394 (Unexpected Status Code or Return Value)

## Which versions are affected by CVE-2024-1713?

It affects 1 product.


Products: Plv8 Plv8.

## How do I fix CVE-2024-1713?

No fix has been published for CVE-2024-1713 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-1713 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-1713 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-1713 and fix it if it is affected.

What it is: CVE-2024-1713 is a high-severity vulnerability in Plv8, published on 14 Mar 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-1713 exists.

Affected product: Plv8. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-1713/ (Markdown: https://insights.sbomify.com/CVE-2024-1713/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-1713
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-1713
- OSV: https://osv.dev/vulnerability/CVE-2024-1713

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-1713/
Summaries are generated and may contain mistakes; the official description above is the record.