# CVE-2023-41113: Information disclosure in n/a

> Authenticated users can leak file existence and content details if superusers enable specific non-default logging and directory configurations.

- **Severity:** Medium 4.3 (`CVSS:3.1/AC:L/AV:N/A:N/C:L/I:N/PR:L/S:U/UI: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:** 12 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-94q2-6rf3-frvc

## What is CVE-2023-41113?

CVE-2023-41113 is a medium-severity vulnerability in n/a, published on 12 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It allows an authenticated user to to obtain information about whether certain files exist on disk, what errors if any occur when attempting to read them, and some limited information about their contents (regardless of permissions). This can occur when a superuser has configured one or more directories for filesystem access via CREATE DIRECTORY and adopted certain non-default settings for log_line_prefix and log_connections.

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

It affects 1 product.


Products: Enterprisedb Postgres Advanced Server.

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

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

## Is CVE-2023-41113 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-41117](https://insights.sbomify.com/CVE-2023-41117/): Path traversal in n/a (high 8.8)
- [CVE-2023-41118](https://insights.sbomify.com/CVE-2023-41118/): Missing authorization in n/a (high 8.8)
- [CVE-2023-41119](https://insights.sbomify.com/CVE-2023-41119/): Privilege escalation in n/a (high 8.8)
- [CVE-2023-31043](https://insights.sbomify.com/CVE-2023-31043/): Information disclosure in n/a (high 7.5)
- [CVE-2023-41114](https://insights.sbomify.com/CVE-2023-41114/): Path traversal in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-41113 is a medium-severity vulnerability in n/a, published on 12 Dec 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-41113 in the wild and no public exploit code.

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

## Sources

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

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