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

> High-privileged users can leak sensitive information to external files when using external metadata storage in Seq.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jul 2023
- **Updated:** 24 Oct 2024
- **Also known as:** GHSA-hwvv-cf85-p845

## What is CVE-2023-38195?

CVE-2023-38195 is a medium-severity vulnerability in n/a, published on 22 Jul 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Datalust Seq before 2023.2.9489 allows insertion of sensitive information into an externally accessible file or directory. This is exploitable only when external (SQL Server or PostgreSQL) metadata storage is used. Exploitation can only occur from a high-privileged user account.

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

It affects 1 product.


Products: Datalust Seq.

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

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

## Is CVE-2023-38195 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-8096](https://insights.sbomify.com/CVE-2018-8096/): Auth bypass in n/a (critical 9.8)
- [CVE-2024-29866](https://insights.sbomify.com/CVE-2024-29866/): Privilege escalation in n/a (critical 9.1)
- [CVE-2025-27912](https://insights.sbomify.com/CVE-2025-27912/): Cross-site request forgery in Seq (high 8.8)
- [CVE-2025-27911](https://insights.sbomify.com/CVE-2025-27911/): Denial of service in Seq (medium 6.5)
- [CVE-2021-41329](https://insights.sbomify.com/CVE-2021-41329/): Information disclosure in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-38195 is a medium-severity vulnerability in n/a, published on 22 Jul 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-38195 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-38195/ (Markdown: https://insights.sbomify.com/CVE-2023-38195/index.md)
```

## Sources

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

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