{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2014-1670 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2014-1670 yet. Limit exposure of the affected software until one is available.","what":"CVE-2014-1670 is a medium-severity code injection vulnerability in n/a, published on 25 Jan 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2014-1670 and fix it if it is affected.\n\nWhat it is: CVE-2014-1670 is a medium-severity code injection vulnerability in n/a, published on 25 Jan 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2014-1670 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-2014-1670/ (Markdown: https://insights.sbomify.com/CVE-2014-1670/index.md)","id":"CVE-2014-1670","markdown":"https://insights.sbomify.com/CVE-2014-1670/index.md","name":"CVE-2014-1670","record":{"aliases":["GHSA-6w6g-qxcw-ffc5"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Bing Android app","requires_auth":"none","summary":"Remote attackers can install arbitrary APK files on Android devices via a crafted DNS response, requiring user interaction to trigger the vulnerability.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"bing","vendor":"microsoft"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"The Microsoft Bing application before 4.2.1 for Android allows remote attackers to install arbitrary APK files via vectors involving a crafted DNS response.","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":"Code injection in n/a","id":"CVE-2014-1670","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2014"},"n_packages":0,"n_references":6,"next":{"headline":"SQL injection in n/a","id":"CVE-2014-1671"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2014-1666"},"products":["n/a"],"published":"2014-01-25","related":[{"cvss_score":10,"headline":"Microsoft Bing Remote Code Execution Vulnerability","id":"CVE-2026-33819","kev_date_added":null,"published":"2026-04-23"},{"cvss_score":10,"headline":"Microsoft Bing Elevation of Privilege Vulnerability","id":"CVE-2026-32186","kev_date_added":null,"published":"2026-04-03"},{"cvss_score":8.6,"headline":"Microsoft Bing Remote Code Execution Vulnerability","id":"CVE-2025-21355","kev_date_added":null,"published":"2025-02-19"},{"cvss_score":6.5,"headline":"Microsoft Bing Tampering Vulnerability","id":"CVE-2026-26120","kev_date_added":null,"published":"2026-03-19"},{"cvss_score":6.5,"headline":"Cross-site scripting in Microsoft Bing Search for Android","id":"CVE-2020-1329","kev_date_added":null,"published":"2020-06-09"},{"cvss_score":4.7,"headline":"Microsoft Bing Search Spoofing Vulnerability","id":"CVE-2021-33753","kev_date_added":null,"published":"2021-07-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":"Remote attackers can install arbitrary APK files on Android devices via a crafted DNS response, requiring user interaction to trigger the vulnerability.","url":"https://insights.sbomify.com/CVE-2014-1670/"}