# CVE-2022-38107: Sensitive Data Disclosure Vulnerability

> Attackers can view sensitive environmental details via detailed technical error messages in SolarWinds SQL Sentry.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2022
- **Updated:** 8 May 2025
- **Also known as:** GHSA-8wv9-mpgp-4x9v

## What is CVE-2022-38107?

CVE-2022-38107 is a medium-severity vulnerability in SolarWinds SQL Sentry, published on 19 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Sensitive information could be displayed when a detailed technical error message is posted. This information could disclose environmental details.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

## Which versions are affected by CVE-2022-38107?

It affects 1 product.


Products: Solarwinds Sql Sentry.

## How do I fix CVE-2022-38107?

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

## Is CVE-2022-38107 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-38107 and fix it if it is affected.

What it is: CVE-2022-38107 is a medium-severity vulnerability in SolarWinds SQL Sentry, published on 19 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-38107 in the wild and no public exploit code.

Affected product: SolarWinds SQL Sentry. 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-2022-38107/ (Markdown: https://insights.sbomify.com/CVE-2022-38107/index.md)
```

## Sources

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

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