{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-48984 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-48984 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-48984 is a critical memory corruption vulnerability in n/a, published on 20 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-48984 and fix it if it is affected.\n\nWhat it is: CVE-2024-48984 is a critical memory corruption vulnerability in n/a, published on 20 Nov 2024. 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-2024-48984 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-2024-48984/ (Markdown: https://insights.sbomify.com/CVE-2024-48984/index.md)","id":"CVE-2024-48984","markdown":"https://insights.sbomify.com/CVE-2024-48984/index.md","name":"CVE-2024-48984","record":{"aliases":["GHSA-p8x9-vqx9-g5pw"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"MBed OS","requires_auth":"none","summary":"A buffer overflow in MBed OS HCI report parsing allows attackers to potentially execute arbitrary code or cause a denial of service via crafted input.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mbed_os","vendor":"arm"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-120","name":"Buffer Copy without Checking Size of Input"}],"description":"An issue was discovered in MBed OS 6.16.0. When parsing hci reports, the hci parsing software dynamically determines the length of a list of reports by reading a byte from an input stream. It then fetches the length of the first report, uses it to calculate the beginning of the second report, etc. In doing this, it tracks the largest report so it can later allocate a buffer that fits every individual report (but only one at a time). It does not, however, validate that these addresses are all contained within the buffer passed to hciEvtProcessLeExtAdvReport. It is then possible, though unlikely, that the buffer designated to hold the reports is allocated in such a way that one of these out-of-bounds length fields is contained within the new buffer. When the (n-1)th report is copied, it overwrites the length field of the nth report. This now corrupted length field is then used for a memcpy into the new buffer, which may lead to a buffer overflow.","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 n/a","id":"CVE-2024-48984","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2024-48985"},"packages":[],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2024-48983"},"products":["n/a"],"published":"2024-11-20","related":[{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2020-12883","kev_date_added":null,"published":"2020-06-18"},{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2020-12884","kev_date_added":null,"published":"2020-06-18"},{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2020-12886","kev_date_added":null,"published":"2020-06-18"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2020-12885","kev_date_added":null,"published":"2020-06-18"},{"cvss_score":7,"headline":"Memory corruption in n/a","id":"CVE-2024-22905","kev_date_added":null,"published":"2024-04-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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-11-25","vendors":["n/a"]},"summary":"A buffer overflow in MBed OS HCI report parsing allows attackers to potentially execute arbitrary code or cause a denial of service via crafted input.","url":"https://insights.sbomify.com/CVE-2024-48984/"}