# CVE-2023-23554: Code injection in pg ivm

> Attackers can execute arbitrary code with materialized view owner privileges by exploiting uncontrolled search path elements in pg_ivm.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Mar 2023
- **Updated:** 6 Mar 2025
- **Also known as:** GHSA-jwqx-q9h3-4q35

## What is CVE-2023-23554?

CVE-2023-23554 is a high-severity code injection vulnerability in pg_ivm, published on 7 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Uncontrolled search path element vulnerability exists in pg_ivm versions prior to 1.5.1. When refreshing an IMMV, pg_ivm executes functions without specifying schema names. Under certain conditions, pg_ivm may be tricked to execute unexpected functions from other schemas with the IMMV owner's privilege. If this vulnerability is exploited, an unexpected function provided by an attacker may be executed with the privilege of the materialized view owner.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2023-23554?

It affects 1 product.


Products: Sraoss Pg Ivm.

## How do I fix CVE-2023-23554?

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

## Is CVE-2023-23554 being exploited?

There is no known exploitation of CVE-2023-23554 in the wild and no public exploit code.

## Other vulnerabilities in pg_ivm

- [CVE-2023-22847](https://insights.sbomify.com/CVE-2023-22847/): Information disclosure in pg ivm (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-23554 and fix it if it is affected.

What it is: CVE-2023-23554 is a high-severity code injection vulnerability in pg_ivm, published on 7 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-23554 in the wild and no public exploit code.

Affected product: pg_ivm. 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-2023-23554/ (Markdown: https://insights.sbomify.com/CVE-2023-23554/index.md)
```

## Sources

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

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