{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-3490 exists.","fix":"No fix has been published for CVE-2007-3490 yet. Limit exposure of the affected software until one is available.","what":"CVE-2007-3490 is a high-severity memory corruption vulnerability in Microsoft Excel, published on 29 Jun 2007. 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-2007-3490 and fix it if it is affected.\n\nWhat it is: CVE-2007-3490 is a high-severity memory corruption vulnerability in Microsoft Excel, published on 29 Jun 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-3490 exists.\n\nAffected product: Microsoft Excel. 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-2007-3490/ (Markdown: https://insights.sbomify.com/CVE-2007-3490/index.md)","id":"CVE-2007-3490","markdown":"https://insights.sbomify.com/CVE-2007-3490/index.md","name":"CVE-2007-3490","record":{"aliases":["GHSA-gv8q-4r76-rh77"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Microsoft Excel","requires_auth":"none","summary":"Remote attackers can execute arbitrary code by tricking users into opening a malicious Excel file, requiring user interaction to exploit.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"excel","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":"Unspecified vulnerability in Microsoft Excel 2003 SP2 allows remote attackers to have an unknown impact via unspecified vectors, possibly related to the sheet name, as demonstrated by 2670.xls.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2007-06-27","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2007-06-27","kind":"exploitdb","ref":"4121","stars":null,"title":"Microsoft Excel 2000/2003 - Sheet Name (PoC)"}],"tier":"weaponised"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2007-3490","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:excel","products":["microsoft:excel"],"type":"memory_corruption","year":"2007"},"n_packages":0,"n_references":7,"next":{"headline":"Memory corruption in n/a","id":"CVE-2007-3491"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2007-3489"},"products":["n/a"],"published":"2007-06-29","related":[{"cvss_score":8.8,"headline":"Microsoft Excel Remote Code Execution","id":"CVE-2019-1297","kev_date_added":"2022-03-03","published":"2019-09-11"},{"cvss_score":8.8,"headline":"Microsoft Office Remote Code Execution","id":"CVE-2009-0238","kev_date_added":"2026-04-14","published":"2009-02-25"},{"cvss_score":7.8,"headline":"Microsoft Office Security Feature Bypass","id":"CVE-2016-7262","kev_date_added":"2022-03-03","published":"2016-12-20"},{"cvss_score":7.8,"headline":"Microsoft Excel Featheader Record Memory Corruption","id":"CVE-2009-3129","kev_date_added":"2022-03-03","published":"2009-11-11"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2008-0081","kev_date_added":null,"published":"2008-01-16"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2015-6040","kev_date_added":null,"published":"2015-12-09"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2015-6122","kev_date_added":null,"published":"2015-12-09"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"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 malicious Excel file, requiring user interaction to exploit.","url":"https://insights.sbomify.com/CVE-2007-3490/"}