{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-21230 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-21230 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-21230 is a medium-severity vulnerability in org.nanohttpd:nanohttpd, published on 1 May 2022. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-21230 and fix it if it is affected.\n\nWhat it is: CVE-2022-21230 is a medium-severity vulnerability in org.nanohttpd:nanohttpd, published on 1 May 2022. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-21230 in the wild and no public exploit code.\n\nAffected product: org.nanohttpd:nanohttpd. 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-21230/ (Markdown: https://insights.sbomify.com/CVE-2022-21230/index.md)","id":"CVE-2022-21230","markdown":"https://insights.sbomify.com/CVE-2022-21230/index.md","name":"CVE-2022-21230","record":{"aliases":["GHSA-2r85-x9cf-8fcg","SNYK-JAVA-ORGNANOHTTPD-2422798"],"analysis":{"component_type":"library","fix_type":"configuration_change","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Java HTTP server library","requires_auth":"low_privilege","summary":"Local attackers can read sensitive HTTP request bodies from temporary files due to insecure file permissions in the NanoHTTPD library.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"nanohttpd","vendor":"nanohttpd"}],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[],"description":"This affects all versions of package org.nanohttpd:nanohttpd. Whenever an HTTP Session is parsing the body of an HTTP request, the body of the request is written to a RandomAccessFile when the it is larger than 1024 bytes. This file is created with insecure permissions that allow its contents to be viewed by all users on the host machine. **Workaround:** Manually specifying the -Djava.io.tmpdir= argument when launching Java to set the temporary directory to a directory exclusively controlled by the current user can fix this issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Information Exposure","id":"CVE-2022-21230","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"Prototype Pollution","id":"CVE-2022-21231"},"packages":[],"prev":{"headline":"Privilege escalation in Intel(R) NUC 9 Extreme Laptop Kit drivers","id":"CVE-2022-21229"},"products":["org.nanohttpd:nanohttpd"],"published":"2022-05-01","related":[{"cvss_score":6.1,"headline":"NanoHTTPD Cross-site Scripting vulnerability","id":"CVE-2020-13697","kev_date_added":null,"published":"2021-02-23"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["n/a"]},"summary":"Local attackers can read sensitive HTTP request bodies from temporary files due to insecure file permissions in the NanoHTTPD library.","url":"https://insights.sbomify.com/CVE-2022-21230/"}