{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2003-0664 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2003-0664 yet. Limit exposure of the affected software until one is available.","what":"CVE-2003-0664 is a high-severity vulnerability in Microsoft Word, published on 4 Sep 2003. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2003-0664 and fix it if it is affected.\n\nWhat it is: CVE-2003-0664 is a high-severity vulnerability in Microsoft Word, published on 4 Sep 2003. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2003-0664 in the wild and no public exploit code.\n\nAffected product: Microsoft Word. 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-2003-0664/ (Markdown: https://insights.sbomify.com/CVE-2003-0664/index.md)","id":"CVE-2003-0664","markdown":"https://insights.sbomify.com/CVE-2003-0664/index.md","name":"CVE-2003-0664","record":{"aliases":["GHSA-vpf6-wrhg-p4jg"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Microsoft Word","requires_auth":"none","summary":"Attackers can bypass macro security in Microsoft Word to execute arbitrary code via malicious documents, requiring user interaction to open the file.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"word","vendor":"microsoft"},{"product":"works","vendor":"microsoft"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Microsoft Word 2002, 2000, 97, and 98(J) does not properly check certain properties of a document, which allows attackers to bypass the macro security model and automatically execute arbitrary macros via a malicious document.","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-2003-0664","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:word","products":["microsoft:word","microsoft:works"],"type":"security_feature_bypass","year":"2003"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2003-0665"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2003-0663"},"products":["n/a"],"published":"2003-09-04","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2004-0963","kev_date_added":null,"published":"2004-10-20"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2015-0065","kev_date_added":null,"published":"2015-02-11"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2014-1758","kev_date_added":null,"published":"2014-04-08"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2013-3891","kev_date_added":null,"published":"2013-10-09"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2013-3892","kev_date_added":null,"published":"2013-10-09"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2013-3856","kev_date_added":null,"published":"2013-09-11"},{"cvss_score":9.3,"headline":"Code injection in n/a","id":"CVE-2013-1335","kev_date_added":null,"published":"2013-05-15"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-08","vendors":["n/a"]},"summary":"Attackers can bypass macro security in Microsoft Word to execute arbitrary code via malicious documents, requiring user interaction to open the file.","url":"https://insights.sbomify.com/CVE-2003-0664/"}