{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2010-3230 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2010-3230 yet. Limit exposure of the affected software until one is available.","what":"CVE-2010-3230 is a critical vulnerability in Microsoft Excel, published on 13 Oct 2010. 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-2010-3230 and fix it if it is affected.\n\nWhat it is: CVE-2010-3230 is a critical vulnerability in Microsoft Excel, published on 13 Oct 2010. 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-2010-3230 in the wild and no public exploit code.\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-2010-3230/ (Markdown: https://insights.sbomify.com/CVE-2010-3230/index.md)","id":"CVE-2010-3230","markdown":"https://insights.sbomify.com/CVE-2010-3230/index.md","name":"CVE-2010-3230","record":{"aliases":["GHSA-p973-rq82-cpv6"],"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 document with crafted record information.","user_interaction":"required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"excel","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-189","name":null}],"description":"Integer overflow in Microsoft Excel 2002 SP3 allows remote attackers to execute arbitrary code via an Excel document with crafted record information, aka \"Excel Record Parsing Integer Overflow 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":"Integer overflow in n/a","id":"CVE-2010-3230","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:excel","products":["microsoft:excel"],"type":"integer_overflow","year":"2010"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2010-3231"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2010-3229"},"products":["n/a"],"published":"2010-10-13","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":"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 malicious Excel document with crafted record information.","url":"https://insights.sbomify.com/CVE-2010-3230/"}