{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2013-2598 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2013-2598 yet. Limit exposure of the affected software until one is available.","what":"CVE-2013-2598 is a medium-severity vulnerability in n/a, published on 31 Aug 2014. 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-2013-2598 and fix it if it is affected.\n\nWhat it is: CVE-2013-2598 is a medium-severity vulnerability in n/a, published on 31 Aug 2014. 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-2013-2598 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-2013-2598/ (Markdown: https://insights.sbomify.com/CVE-2013-2598/index.md)","id":"CVE-2013-2598","markdown":"https://insights.sbomify.com/CVE-2013-2598/index.md","name":"CVE-2013-2598","record":{"aliases":["GHSA-7g8r-68cm-p79r"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["security_bypass","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Qualcomm LK bootloader","requires_auth":"none","summary":"Attackers can bypass signature verification in the Qualcomm Little Kernel bootloader by crafting malicious boot-image headers, potentially enabling unauthorized code execution.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"android-msm","vendor":"codeaurora"}],"cvss":{"score":6.6,"severity":"medium","source":"nvd","vector":"AV:L/AC:L/Au:N/C:N/I:C/A:C","version":"2.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"app/aboot/aboot.c in the Little Kernel (LK) bootloader, as distributed with Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to overwrite signature-verification code via crafted boot-image load-destination header values that specify memory locations within bootloader memory.","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":"Security feature bypass in n/a","id":"CVE-2013-2598","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2013"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2013-2599"},"packages":[],"prev":{"headline":"Code Aurora ACDB Audio Driver Stack-based Buffer Overflow","id":"CVE-2013-2597"},"products":["n/a"],"published":"2014-08-31","related":[{"cvss_score":8.4,"headline":"Code Aurora ACDB Audio Driver Stack-based Buffer Overflow","id":"CVE-2013-2597","kev_date_added":"2022-09-15","published":"2014-08-31"},{"cvss_score":7.8,"headline":"Integer overflow in n/a","id":"CVE-2013-4736","kev_date_added":null,"published":"2014-02-10"},{"cvss_score":7.2,"headline":"Privilege escalation in n/a","id":"CVE-2013-2595","kev_date_added":null,"published":"2014-08-31"},{"cvss_score":7.2,"headline":"Privilege escalation in n/a","id":"CVE-2014-0972","kev_date_added":null,"published":"2014-08-01"},{"cvss_score":7.2,"headline":"Memory corruption in n/a","id":"CVE-2013-4738","kev_date_added":null,"published":"2014-02-03"},{"cvss_score":6.9,"headline":"Privilege escalation in n/a","id":"CVE-2013-6123","kev_date_added":null,"published":"2014-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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Attackers can bypass signature verification in the Qualcomm Little Kernel bootloader by crafting malicious boot-image headers, potentially enabling unauthorized code execution.","url":"https://insights.sbomify.com/CVE-2013-2598/"}