{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2024-20131 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-20131 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-20131 is a medium-severity memory corruption vulnerability in Mediatek Nr16, published on 2 Dec 2024. 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-2024-20131 and fix it if it is affected.\n\nWhat it is: CVE-2024-20131 is a medium-severity memory corruption vulnerability in Mediatek Nr16, published on 2 Dec 2024. 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-2024-20131 in the wild and no public exploit code.\n\nAffected product: Mediatek Nr16. 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-2024-20131/ (Markdown: https://insights.sbomify.com/CVE-2024-20131/index.md)","id":"CVE-2024-20131","markdown":"https://insights.sbomify.com/CVE-2024-20131/index.md","name":"CVE-2024-20131","record":{"aliases":["GHSA-m396-rwgp-jw45"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"MediaTek modem firmware","requires_auth":"high_privilege","summary":"Local attackers with system privileges can escalate privileges via an incorrect bounds check in MediaTek modem firmware.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"MediaTek","cpe":[{"product":"nr16","vendor":"mediatek"},{"product":"nr17","vendor":"mediatek"}],"cvss":{"score":6.7,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"In Modem, there is a possible escalation of privilege due to an incorrect bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: MOLY01395886; Issue ID: MSV-1873.","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":"Memory corruption in MT2737, MT2739, MT6789, MT6813, MT6815, MT6835, MT6835T, MT6855, MT6878, MT6878T, MT6879, MT6886, MT6895, MT6895T, MT6896, MT6897, MT6899, MT6980, MT6980D, MT6983, MT6985, MT6986, MT6986D, MT6988, MT6989, MT6990, MT6991, MT8673, MT8676, MT8795T, MT8798","id":"CVE-2024-20131","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"mediatek:nr16","products":["mediatek:nr16"],"type":"memory_corruption","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in MT2737, MT6298, MT6879, MT6886, MT6895, MT6895T, MT6896, MT6980, MT6980D, MT6983, MT6985, MT6989, MT6990, MT8673, MT8676, MT8795T, MT8798","id":"CVE-2024-20132"},"packages":[],"prev":{"headline":"Memory corruption in MT6739, MT6761, MT6765, MT6768, MT6781, MT6789, MT6833, MT6835, MT6853, MT6855, MT6877, MT6878, MT6879, MT6883, MT6885, MT6886, MT6889, MT6893, MT6895, MT6896, MT6897, MT6983, MT6985, MT6989, MT8195, MT8676, MT8678, MT8696, MT8796","id":"CVE-2024-20130"},"products":["MT2737, MT2739, MT6789, MT6813, MT6815, MT6835, MT6835T, MT6855, MT6878, MT6878T, MT6879, MT6886, MT6895, MT6895T, MT6896, MT6897, MT6899, MT6980, MT6980D, MT6983, MT6985, MT6986, MT6986D, MT6988, MT6989, MT6990, MT6991, MT8673, MT8676, MT8795T, MT8798"],"published":"2024-12-02","related":[{"cvss_score":9.8,"headline":"Memory corruption in MT6813, MT6815, MT6835, MT6878, MT6897, MT6899, MT6986, MT6986D, MT6991, MT8792","id":"CVE-2024-20067","kev_date_added":null,"published":"2024-06-03"},{"cvss_score":8.8,"headline":"Memory corruption in MT2737, MT6813, MT6835, MT6835T, MT6878, MT6878M, MT6879, MT6886, MT6895, MT6895TT, MT6896, MT6897, MT6899, MT6980, MT6980D, MT6983, MT6983T, MT6985, MT6985T, MT6989, MT6989T, MT6990, MT6991, MT8673, MT8676, MT8678, MT8795T, MT8798, MT8863","id":"CVE-2025-20634","kev_date_added":null,"published":"2025-02-03"},{"cvss_score":7.5,"headline":"Memory corruption in MT6298, MT6813, MT6815, MT6835, MT6878, MT6879, MT6895, MT6895T, MT6896, MT6897, MT6899, MT6980, MT6980D, MT6983, MT6986, MT6986D, MT6990, MT6991, MT8673, MT8792, MT8798","id":"CVE-2024-20066","kev_date_added":null,"published":"2024-06-03"},{"cvss_score":6.7,"headline":"Memory corruption in MT2737, MT2739, MT6789, MT6813, MT6815, MT6835, MT6835T, MT6855, MT6878, MT6878T, MT6879, MT6886, MT6895, MT6895T, MT6896, MT6897, MT6899, MT6980, MT6980D, MT6983, MT6985, MT6986, MT6986D, MT6988, MT6989, MT6990, MT6991, MT8676, MT8678, MT8798, MT8863","id":"CVE-2024-20151","kev_date_added":null,"published":"2025-01-06"},{"cvss_score":6.7,"headline":"Memory corruption in MT2737, MT6298, MT6879, MT6886, MT6895, MT6895T, MT6896, MT6980, MT6980D, MT6983, MT6985, MT6989, MT6990, MT8673, MT8676, MT8795T, MT8798","id":"CVE-2024-20132","kev_date_added":null,"published":"2024-12-02"},{"cvss_score":6.7,"headline":"Memory corruption in MT6879, MT6886, MT6895, MT6895T, MT6896, MT6980, MT6983, MT8673, MT8676, MT8795T, MT8798","id":"CVE-2024-20133","kev_date_added":null,"published":"2024-12-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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-12-03","vendors":["MediaTek, Inc."]},"summary":"Local attackers with system privileges can escalate privileges via an incorrect bounds check in MediaTek modem firmware.","url":"https://insights.sbomify.com/CVE-2024-20131/"}