{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2013-1323 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2013-1323 yet. Limit exposure of the affected software until one is available.","what":"CVE-2013-1323 is a critical vulnerability in n/a, published on 15 May 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-1323 and fix it if it is affected.\n\nWhat it is: CVE-2013-1323 is a critical vulnerability in n/a, published on 15 May 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-1323 in the wild and no public exploit code.\n\nAffected product: n/a. 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-1323/ (Markdown: https://insights.sbomify.com/CVE-2013-1323/index.md)","id":"CVE-2013-1323","markdown":"https://insights.sbomify.com/CVE-2013-1323/index.md","name":"CVE-2013-1323","record":{"aliases":["GHSA-q526-c3ch-x422"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Microsoft Publisher","requires_auth":"none","summary":"Remote attackers can execute arbitrary code by tricking users into opening a crafted Microsoft Publisher file due to improper NULL value handling.","user_interaction":"required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"publisher","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 Publisher 2003 SP3 does not properly handle NULL values for unspecified data items, which allows remote attackers to execute arbitrary code via a crafted Publisher file, aka \"Publisher Incorrect NULL Value Handling 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":"Null dereference in n/a","id":"CVE-2013-1323","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2013"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2013-1324"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2013-1322"},"products":["n/a"],"published":"2013-05-15","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2013-1318","kev_date_added":null,"published":"2013-05-15"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2013-1319","kev_date_added":null,"published":"2013-05-15"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2013-1320","kev_date_added":null,"published":"2013-05-15"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2013-1322","kev_date_added":null,"published":"2013-05-15"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2008-0102","kev_date_added":null,"published":"2008-02-12"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2007-1117","kev_date_added":null,"published":"2007-02-27"},{"cvss_score":9.3,"headline":"Null dereference in n/a","id":"CVE-2014-1759","kev_date_added":null,"published":"2014-04-08"}],"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 by tricking users into opening a crafted Microsoft Publisher file due to improper NULL value handling.","url":"https://insights.sbomify.com/CVE-2013-1323/"}