# CVE-2022-24875: Potential Secrets being logged to disk in CVEProject/cve-services

> Attackers with log access can read user secrets due to improper logging in the CVE Services API, requiring a code patch or manual log cleanup.

- **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:** 21 Apr 2022
- **Updated:** 23 Apr 2025

## What is CVE-2022-24875?

CVE-2022-24875 is a medium-severity vulnerability in CVEProject cve-services, published on 21 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The CVEProject/cve-services is an open source project used to operate the CVE services api. In versions up to and including 1.1.1 the `org.conroller.js` code would erroneously log user secrets. This has been resolved in commit `46d98f2b` and should be available in subsequent versions of the software. Users of the software are advised to manually apply the `46d98f2b` commit or to update when a new version becomes available. As a workaround users should inspect their logs and remove logged secrets as appropriate.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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

It affects 1 product.


Products: Cve Cve-Services.

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

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

## Is CVE-2022-24875 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-24875 is a medium-severity vulnerability in CVEProject cve-services, published on 21 Apr 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-24875 in the wild and no public exploit code.

Affected product: CVEProject cve-services. 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-24875/ (Markdown: https://insights.sbomify.com/CVE-2022-24875/index.md)
```

## Sources

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

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