{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-27813 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-27813 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-27813 is a high-severity vulnerability in Motorola Mobile Radio, published on 19 Oct 2023. 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-27813 and fix it if it is affected.\n\nWhat it is: CVE-2022-27813 is a high-severity vulnerability in Motorola Mobile Radio, published on 19 Oct 2023. 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-27813 in the wild and no public exploit code.\n\nAffected product: Motorola Mobile Radio. 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-27813/ (Markdown: https://insights.sbomify.com/CVE-2022-27813/index.md)","id":"CVE-2022-27813","markdown":"https://insights.sbomify.com/CVE-2022-27813/index.md","name":"CVE-2022-27813","record":{"aliases":["GHSA-m8m2-8cm8-p8jv"],"analysis":{"component_type":"hardware_firmware","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Motorola mobile radio","requires_auth":"high_privilege","summary":"Attackers with control over one core can execute code on the other due to unconfigured memory protection units in Motorola MTM5000 firmware.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"NCSC-NL","cpe":[{"product":"mtm5400_firmware","vendor":"motorola"},{"product":"mtm5500_firmware","vendor":"motorola"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:H/A:H/E:F/RL:U/RC:C/CR:X/IR:X/AR:X/MAV:L/MAC:L/MPR:H/MUI:N/MS:C/MC:L/MI:H/MA:H","version":"3.1"},"cwes":[{"id":"CWE-1260","name":"Improper Handling of Overlap Between Protected Memory Ranges"}],"description":"Motorola MTM5000 series firmwares lack properly configured memory protection of pages shared between the OMAP-L138 ARM and DSP cores. The SoC provides two memory protection units, MPU1 and MPU2, to enforce the trust boundary between the two cores. Since both units are left unconfigured by the firmwares, an adversary with control over either core can trivially gain code execution on the other, by overwriting code located in shared RAM or DDR2 memory regions.","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":"Unconfigured memory protection modules in Motorola MTM5000","id":"CVE-2022-27813","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Exposure of Resource to Wrong Sphere in Simple-Wayland-HotKey-Daemon","id":"CVE-2022-27814"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2022-27812"},"products":["Mobile Radio"],"published":"2023-10-19","related":[{"cvss_score":9.6,"headline":"Format string vulnerability in AT+CTGL command in Motorola MTM5000","id":"CVE-2022-26941","kev_date_added":null,"published":"2023-10-19"},{"cvss_score":8.8,"headline":"Weak PRNG entropy source used for authentication challenge generation in Motorola MTM5000","id":"CVE-2022-26943","kev_date_added":null,"published":"2023-10-19"},{"cvss_score":8.2,"headline":"Multiple missing pointer validation checks in trusted execution module in Motorola MTM5000","id":"CVE-2022-26942","kev_date_added":null,"published":"2023-10-19"}],"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":"2024-08-03","vendors":["Motorola"]},"summary":"Attackers with control over one core can execute code on the other due to unconfigured memory protection units in Motorola MTM5000 firmware.","url":"https://insights.sbomify.com/CVE-2022-27813/"}