{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2018-8312 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-8312 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-8312 is a high-severity memory corruption vulnerability in Microsoft Office, published on 11 Jul 2018. 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-2018-8312 and fix it if it is affected.\n\nWhat it is: CVE-2018-8312 is a high-severity memory corruption vulnerability in Microsoft Office, published on 11 Jul 2018. 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-2018-8312 in the wild and no public exploit code.\n\nAffected product: Microsoft Office. 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-2018-8312/ (Markdown: https://insights.sbomify.com/CVE-2018-8312/index.md)","id":"CVE-2018-8312","markdown":"https://insights.sbomify.com/CVE-2018-8312/index.md","name":"CVE-2018-8312","record":{"aliases":["GHSA-jjxr-vhf2-g6pf"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Microsoft Office","requires_auth":"none","summary":"Attackers can execute arbitrary code remotely by exploiting a memory handling flaw in Microsoft Access.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"access","vendor":"microsoft"},{"product":"office","vendor":"microsoft"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[],"description":"A remote code execution vulnerability exists when Microsoft Access fails to properly handle objects in memory, aka \"Microsoft Access Remote Code Execution Vulnerability.\" This affects Microsoft Access, Microsoft Office.","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 Microsoft Access","id":"CVE-2018-8312","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:office","products":["microsoft:office"],"type":"memory_corruption","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Privilege escalation in Windows 10","id":"CVE-2018-8313"},"packages":[],"prev":{"headline":"Code injection in Microsoft Lync","id":"CVE-2018-8311"},"products":["Microsoft Access","Microsoft Office"],"published":"2018-07-11","related":[{"cvss_score":8.8,"headline":"Microsoft Office Excel Remote Code Execution","id":"CVE-2007-0671","kev_date_added":"2025-08-12","published":"2007-02-03"},{"cvss_score":10,"headline":"Code injection in n/a","id":"CVE-2000-0788","kev_date_added":null,"published":"2002-03-09"},{"cvss_score":9.3,"headline":"Security feature bypass in n/a","id":"CVE-2015-2503","kev_date_added":null,"published":"2015-11-11"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2013-3155","kev_date_added":null,"published":"2013-09-11"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2013-3156","kev_date_added":null,"published":"2013-09-11"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2013-3157","kev_date_added":null,"published":"2013-09-11"},{"cvss_score":9.3,"headline":"Code injection in n/a","id":"CVE-2010-0814","kev_date_added":null,"published":"2010-07-14"}],"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-05","vendors":["Microsoft"]},"summary":"Attackers can execute arbitrary code remotely by exploiting a memory handling flaw in Microsoft Access.","url":"https://insights.sbomify.com/CVE-2018-8312/"}