{"answers":{"affected":"It affects 23 products.","exploited":"There is no known exploitation of CVE-2022-45163 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-45163 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-45163 is a medium-severity vulnerability in n/a, published on 18 Nov 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-45163 and fix it if it is affected.\n\nWhat it is: CVE-2022-45163 is a medium-severity vulnerability in n/a, published on 18 Nov 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-45163 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-45163/ (Markdown: https://insights.sbomify.com/CVE-2022-45163/index.md)","id":"CVE-2022-45163","markdown":"https://insights.sbomify.com/CVE-2022-45163/index.md","name":"CVE-2022-45163","record":{"aliases":["GHSA-rrqq-ffjh-mjxv"],"analysis":{"component_type":"hardware_firmware","fix_type":"configuration_change","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"NXP i.MX microcontrollers","requires_auth":"none","summary":"Physically proximate attackers can leak memory contents from NXP i.MX devices via the Serial Download Protocol port in cold and warm boot attacks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"i.mx_6_firmware","vendor":"nxp"},{"product":"i.mx_6dual_firmware","vendor":"nxp"},{"product":"i.mx_6duallite_firmware","vendor":"nxp"},{"product":"i.mx_6dualplus_firmware","vendor":"nxp"},{"product":"i.mx_6quad_firmware","vendor":"nxp"},{"product":"i.mx_6quadplus_firmware","vendor":"nxp"},{"product":"i.mx_6solo_firmware","vendor":"nxp"},{"product":"i.mx_6sololite_firmware","vendor":"nxp"},{"product":"i.mx_6solox_firmware","vendor":"nxp"},{"product":"i.mx_6ull_firmware","vendor":"nxp"},{"product":"i.mx_6ultralite_firmware","vendor":"nxp"},{"product":"i.mx_6ulz_firmware","vendor":"nxp"},{"product":"i.mx_7dual_firmware","vendor":"nxp"},{"product":"i.mx_7solo_firmware","vendor":"nxp"},{"product":"i.mx_7ulp_firmware","vendor":"nxp"},{"product":"i.mx_8m_mini_firmware","vendor":"nxp"},{"product":"i.mx_8m_quad_firmware","vendor":"nxp"},{"product":"i.mx_8m_vybrid_firmware","vendor":"nxp"},{"product":"i.mx_rt1010_firmware","vendor":"nxp"},{"product":"i.mx_rt1015_firmware","vendor":"nxp"},{"product":"i.mx_rt1020_firmware","vendor":"nxp"},{"product":"i.mx_rt1050_firmware","vendor":"nxp"},{"product":"i.mx_rt1060_firmware","vendor":"nxp"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AC:L/AV:P/A:N/C:H/I:N/PR:N/S:C/UI:N","version":"3.1"},"cwes":[{"id":"CWE-203","name":"Observable Discrepancy"}],"description":"An information-disclosure vulnerability exists on select NXP devices when configured in Serial Download Protocol (SDP) mode: i.MX RT 1010, i.MX RT 1015, i.MX RT 1020, i.MX RT 1050, i.MX RT 1060, i.MX 6 Family, i.MX 7Dual/Solo, i.MX 7ULP, i.MX 8M Quad, i.MX 8M Mini, and Vybrid. In a device security-enabled configuration, memory contents could potentially leak to physically proximate attackers via the respective SDP port in cold and warm boot attacks. (The recommended mitigation is to completely disable the SDP mode by programming a one-time programmable eFUSE. Customers can contact NXP for additional 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-2022-45163","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Missing authorization in n/a","id":"CVE-2022-45164"},"packages":[],"prev":{"headline":"Exposure of vSphere's CPI and CSI credentials in Rancher","id":"CVE-2022-45157"},"products":["n/a"],"published":"2022-11-18","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-30","vendors":["n/a"]},"summary":"Physically proximate attackers can leak memory contents from NXP i.MX devices via the Serial Download Protocol port in cold and warm boot attacks.","url":"https://insights.sbomify.com/CVE-2022-45163/"}