{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-57482 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-57482 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-57482 is a critical memory corruption vulnerability in n/a, published on 14 Jan 2025. 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-57482 and fix it if it is affected.\n\nWhat it is: CVE-2024-57482 is a critical memory corruption vulnerability in n/a, published on 14 Jan 2025. 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-57482 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-57482/ (Markdown: https://insights.sbomify.com/CVE-2024-57482/index.md)","id":"CVE-2024-57482","markdown":"https://insights.sbomify.com/CVE-2024-57482/index.md","name":"CVE-2024-57482","record":{"aliases":["GHSA-857v-mfgq-pf5h"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"H3C 5G network device","requires_auth":"none","summary":"Remote attackers can cause crashes or execute arbitrary commands on H3C N12 devices via a buffer overflow in the 5G processing function.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"n12_firmware","vendor":"h3c"}],"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":"H3C N12 V100R005 contains a buffer overflow vulnerability due to the lack of length verification in the 5G wireless network processing function. Attackers who successfully exploit this vulnerability can cause the remote target device to crash or execute arbitrary commands by sending a POST request to /bin/webs.","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-57482","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2024-57483"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2024-57480"},"products":["n/a"],"published":"2025-01-14","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-57471","kev_date_added":null,"published":"2025-01-14"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-57473","kev_date_added":null,"published":"2025-01-14"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-57479","kev_date_added":null,"published":"2025-01-14"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-57480","kev_date_added":null,"published":"2025-01-14"}],"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":"2026-07-05","vendors":["n/a"]},"summary":"Remote attackers can cause crashes or execute arbitrary commands on H3C N12 devices via a buffer overflow in the 5G processing function.","url":"https://insights.sbomify.com/CVE-2024-57482/"}