{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-31004 exists.","fix":"No fix has been published for CVE-2022-31004 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2022-31004 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-31004 exists.\n\nAffected product: CVEProject cve-services. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-31004/ (Markdown: https://insights.sbomify.com/CVE-2022-31004/index.md)","id":"CVE-2022-31004","markdown":"https://insights.sbomify.com/CVE-2022-31004/index.md","name":"CVE-2022-31004","record":{"aliases":[],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"CVE Services API","requires_auth":"none","summary":"Attackers with disk access can read plaintext production secrets logged by the CVE Services API due to improper handling of random keys.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"cve-services","vendor":"mitre"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"},{"id":"CWE-779","name":"Logging of Excessive Data"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Potential secrets being logged to disk in CVE Services","id":"CVE-2022-31004","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Integer Overflow in Vapor's HTTP Range Request","id":"CVE-2022-31005"},"packages":[],"prev":{"headline":"Heap-based Buffer Overflow and Out-of-bounds Write in Sofia-SIP","id":"CVE-2022-31003"},"products":["cve-services"],"published":"2022-05-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-22","vendors":["CVEProject"]},"summary":"Attackers with disk access can read plaintext production secrets logged by the CVE Services API due to improper handling of random keys.","url":"https://insights.sbomify.com/CVE-2022-31004/"}