# CVE-2023-22847: Information disclosure in pg ivm

> An attacker can retrieve unauthorized data from Row-Level Security protected tables via pg_ivm materialized views.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **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-qw2m-6h7m-p859

## What is CVE-2023-22847?

CVE-2023-22847 is a medium-severity 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

Information disclosure vulnerability exists in pg_ivm versions prior to 1.5.1. An Incrementally Maintainable Materialized View (IMMV) created by pg_ivm may reflect rows with Row-Level Security that the owner of the IMMV should not have access to. As a result, information in tables protected by Row-Level Security may be retrieved by a user who is not authorized to access it.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Sraoss Pg Ivm.

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

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

## Is CVE-2023-22847 being exploited?

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

## Other vulnerabilities in pg_ivm

- [CVE-2023-23554](https://insights.sbomify.com/CVE-2023-23554/): Code injection in pg ivm (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-22847 is a medium-severity 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-22847 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-22847/ (Markdown: https://insights.sbomify.com/CVE-2023-22847/index.md)
```

## Sources

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

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