{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-1318 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-1318 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-1318 is a critical code injection vulnerability in Microsoft Office, published on 19 Sep 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-2006-1318 and fix it if it is affected.\n\nWhat it is: CVE-2006-1318 is a critical code injection vulnerability in Microsoft Office, published on 19 Sep 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-2006-1318 in the wild and no public exploit code.\n\nAffected product: Microsoft Office. 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-2006-1318/ (Markdown: https://insights.sbomify.com/CVE-2006-1318/index.md)","id":"CVE-2006-1318","markdown":"https://insights.sbomify.com/CVE-2006-1318/index.md","name":"CVE-2006-1318","record":{"aliases":["GHSA-8jm2-g9m4-p7q2"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Microsoft Office","requires_auth":"none","summary":"Remote attackers can execute arbitrary code by tricking users into opening a malformed Office document with a specific control.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"office","vendor":"microsoft"}],"cvss":{"score":9.3,"severity":"critical","source":"nvd","vector":"AV:N/AC:M/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"Microsoft Office 2003 SP1 and SP2, Office XP SP3, Office 2000 SP3, Office 2004 for Mac, and Office X for Mac do not properly parse record lengths, which allows remote attackers to execute arbitrary code via a malformed control in an Office document, aka \"Microsoft Office Control Vulnerability.\"","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-2006-1318","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:office","products":["microsoft:office"],"type":"code_injection","year":"2006"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2006-1319"},"packages":[],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2006-1317"},"products":["n/a"],"published":"2014-09-19","related":[{"cvss_score":8.8,"headline":"Microsoft Office Memory Corruption","id":"CVE-2018-0798","kev_date_added":"2021-11-03","published":"2018-01-10"},{"cvss_score":8.8,"headline":"Microsoft Office Uninitialized Memory Use","id":"CVE-2015-1770","kev_date_added":"2022-03-28","published":"2015-06-10"},{"cvss_score":8.8,"headline":"Microsoft Word Malformed Object Pointer","id":"CVE-2006-2492","kev_date_added":"2022-06-08","published":"2006-05-20"},{"cvss_score":7.8,"headline":"Microsoft Office Memory Corruption","id":"CVE-2018-0802","kev_date_added":"2021-11-03","published":"2018-01-10"},{"cvss_score":7.8,"headline":"Microsoft Office Memory Corruption","id":"CVE-2017-11882","kev_date_added":"2021-11-03","published":"2017-11-15"},{"cvss_score":7.8,"headline":"Microsoft Office Remote Code Execution","id":"CVE-2017-8570","kev_date_added":"2022-02-25","published":"2017-07-11"},{"cvss_score":7.8,"headline":"Microsoft Office Use-After-Free","id":"CVE-2017-0261","kev_date_added":"2022-03-03","published":"2017-05-12"}],"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-07","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code by tricking users into opening a malformed Office document with a specific control.","url":"https://insights.sbomify.com/CVE-2006-1318/"}