# CVE-2022-31004: Potential secrets being logged to disk in CVE Services

> Attackers with disk access can read plaintext production secrets logged by the CVE Services API due to improper handling of random keys.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 25 May 2022
- **Updated:** 22 Apr 2025

## What is CVE-2022-31004?

CVE-2022-31004 is a high-severity vulnerability in CVEProject cve-services, published on 25 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CVEProject/cve-services is an open source project used to operate the CVE services API. A conditional in 'data.js' has potential for production secrets to be written to disk. The affected method writes the generated randomKey to disk if the environment is not development. If this method were called in production, it is possible that it would write the plaintext key to disk. A patch is not available as of time of publication but is anticipated as a "hot fix" for version 1.1.1 and for the 2.x branch.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information), CWE-779 (Logging of Excessive Data)

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

It affects 1 product.


Products: Mitre Cve-Services.

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

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

## Is CVE-2022-31004 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-31004 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2022-31004 is a high-severity vulnerability in CVEProject cve-services, published on 25 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-31004 exists.

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-31004/ (Markdown: https://insights.sbomify.com/CVE-2022-31004/index.md)
```

## Sources

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

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