{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2013-1313 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2013-1313 yet. Limit exposure of the affected software until one is available.","what":"CVE-2013-1313 is a critical memory corruption vulnerability in Microsoft Windows Xp, published on 13 Feb 2013. 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-2013-1313 and fix it if it is affected.\n\nWhat it is: CVE-2013-1313 is a critical memory corruption vulnerability in Microsoft Windows Xp, published on 13 Feb 2013. 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-2013-1313 in the wild and no public exploit code.\n\nAffected product: Microsoft Windows Xp. 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-2013-1313/ (Markdown: https://insights.sbomify.com/CVE-2013-1313/index.md)","id":"CVE-2013-1313","markdown":"https://insights.sbomify.com/CVE-2013-1313/index.md","name":"CVE-2013-1313","record":{"aliases":["GHSA-fqjw-c53g-2jq8"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Windows OLE Automation","requires_auth":"none","summary":"Remote attackers can execute arbitrary code via a crafted RTF document due to improper memory allocation in Windows OLE Automation.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"windows_xp","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-399","name":null}],"description":"Object Linking and Embedding (OLE) Automation in Microsoft Windows XP SP3 does not properly allocate memory, which allows remote attackers to execute arbitrary code via a crafted RTF document, aka \"OLE Automation Remote Code Execution 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":"Memory corruption in n/a","id":"CVE-2013-1313","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:windows_xp","products":["microsoft:windows_xp"],"type":"memory_corruption","year":"2013"},"n_packages":0,"n_references":4,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2013-1314"},"packages":[],"prev":{"headline":"Use after free in n/a","id":"CVE-2013-1312"},"products":["n/a"],"published":"2013-02-13","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2012-1852","kev_date_added":null,"published":"2012-08-15"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2012-1853","kev_date_added":null,"published":"2012-08-15"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2009-0119","kev_date_added":null,"published":"2009-01-14"},{"cvss_score":10,"headline":"Integer overflow in n/a","id":"CVE-2007-1946","kev_date_added":null,"published":"2007-04-11"},{"cvss_score":10,"headline":"Hardcoded credentials in n/a","id":"CVE-2005-3595","kev_date_added":null,"published":"2005-11-16"},{"cvss_score":10,"headline":"Code injection in n/a","id":"CVE-2004-2289","kev_date_added":null,"published":"2005-08-04"}],"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 execute arbitrary code via a crafted RTF document due to improper memory allocation in Windows OLE Automation.","url":"https://insights.sbomify.com/CVE-2013-1313/"}