{"answers":{"affected":"It affects 28 products.","exploited":"There is no known exploitation of CVE-2020-16849 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-16849 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-16849 is a high-severity vulnerability in n/a, published on 30 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-16849 and fix it if it is affected.\n\nWhat it is: CVE-2020-16849 is a high-severity vulnerability in n/a, published on 30 Nov 2020. 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-2020-16849 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-2020-16849/ (Markdown: https://insights.sbomify.com/CVE-2020-16849/index.md)","id":"CVE-2020-16849","markdown":"https://insights.sbomify.com/CVE-2020-16849/index.md","name":"CVE-2020-16849","record":{"aliases":["GHSA-m3wc-g5cv-5v98"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Canon multifunction printer","requires_auth":"none","summary":"An unauthenticated network attacker can exploit an improper length parameter handling flaw in the IPv4/ICMPv4 component to expose sensitive information.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ir2202n_firmware","vendor":"canon"},{"product":"ir2204f_firmware","vendor":"canon"},{"product":"ir2204n_firmware","vendor":"canon"},{"product":"ir2206if_firmware","vendor":"canon"},{"product":"ir2206n_firmware","vendor":"canon"},{"product":"lbp113w_firmware","vendor":"canon"},{"product":"lbp151dw_firmware","vendor":"canon"},{"product":"lbp162dw_firmware","vendor":"canon"},{"product":"mf113w_firmware","vendor":"canon"},{"product":"mf212w_firmware","vendor":"canon"},{"product":"mf216n_firmware","vendor":"canon"},{"product":"mf217w_firmware","vendor":"canon"},{"product":"mf226dn_firmware","vendor":"canon"},{"product":"mf229dw_firmware","vendor":"canon"},{"product":"mf231_firmware","vendor":"canon"},{"product":"mf232w_firmware","vendor":"canon"},{"product":"mf237w_firmware","vendor":"canon"},{"product":"mf244dw_firmware","vendor":"canon"},{"product":"mf247dw_firmware","vendor":"canon"},{"product":"mf249dw_firmware","vendor":"canon"},{"product":"mf264dw_firmware","vendor":"canon"},{"product":"mf267dw_firmware","vendor":"canon"},{"product":"mf269dw_firmware","vendor":"canon"},{"product":"mf4570dn_firmware","vendor":"canon"},{"product":"mf4580dn_firmware","vendor":"canon"},{"product":"mf4780w_firmware","vendor":"canon"},{"product":"mf4870dn_firmware","vendor":"canon"},{"product":"mf4890dw_firmware","vendor":"canon"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[],"description":"An issue was discovered on Canon MF237w 06.07 devices. An \"Improper Handling of Length Parameter Inconsistency\" issue in the IPv4/ICMPv4 component, when handling a packet sent by an unauthenticated network attacker, may expose Sensitive Information.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2020-16849","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-2020-16850"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-16847"},"products":["n/a"],"published":"2020-11-30","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"An unauthenticated network attacker can exploit an improper length parameter handling flaw in the IPv4/ICMPv4 component to expose sensitive information.","url":"https://insights.sbomify.com/CVE-2020-16849/"}