{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-32983 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-32983 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-32983 is a medium-severity vulnerability in n/a, published on 20 Jun 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-32983 and fix it if it is affected.\n\nWhat it is: CVE-2022-32983 is a medium-severity vulnerability in n/a, published on 20 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-32983 in the wild and no public exploit code.\n\nAffected product: n/a. 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-32983/ (Markdown: https://insights.sbomify.com/CVE-2022-32983/index.md)","id":"CVE-2022-32983","markdown":"https://insights.sbomify.com/CVE-2022-32983/index.md","name":"CVE-2022-32983","record":{"aliases":["DEBIAN-CVE-2022-32983","GHSA-p3g6-9xqh-3vvh","UBUNTU-CVE-2022-32983"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"DNS resolver","requires_auth":"none","summary":"Attackers can poison the DNS cache in Knot Resolver when filters limit forwarding, potentially redirecting users to malicious sites.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"knot_resolver","vendor":"nic"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-290","name":"Authentication Bypass by Spoofing"}],"description":"Knot Resolver through 5.5.1 may allow DNS cache poisoning when there is an attempt to limit forwarding actions by filters.","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":"Other in n/a","id":"CVE-2022-32983","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2022-32984"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2022-32981"},"products":["n/a"],"published":"2022-06-20","related":[{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2023-46317","kev_date_added":null,"published":"2023-10-22"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2023-26249","kev_date_added":null,"published":"2023-02-21"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2021-40083","kev_date_added":null,"published":"2021-08-25"},{"cvss_score":7.5,"headline":"Denial of service in knot-resolver","id":"CVE-2018-1110","kev_date_added":null,"published":"2021-03-30"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2020-12667","kev_date_added":null,"published":"2020-05-19"},{"cvss_score":7.5,"headline":"Other in knot-resolver","id":"CVE-2018-10920","kev_date_added":null,"published":"2018-08-02"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers can poison the DNS cache in Knot Resolver when filters limit forwarding, potentially redirecting users to malicious sites.","url":"https://insights.sbomify.com/CVE-2022-32983/"}