{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-8151 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-8151 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-8151 is a medium-severity vulnerability in Microsoft Exchange Server, published on 9 May 2018. 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-2018-8151 and fix it if it is affected.\n\nWhat it is: CVE-2018-8151 is a medium-severity vulnerability in Microsoft Exchange Server, published on 9 May 2018. 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-2018-8151 in the wild and no public exploit code.\n\nAffected product: Microsoft Exchange Server. 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-8151/ (Markdown: https://insights.sbomify.com/CVE-2018-8151/index.md)","id":"CVE-2018-8151","markdown":"https://insights.sbomify.com/CVE-2018-8151/index.md","name":"CVE-2018-8151","record":{"aliases":["GHSA-gg4j-9c4p-ggfr"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Microsoft Exchange Server","requires_auth":"none","summary":"Attackers can exploit improper memory handling in Microsoft Exchange Server to disclose sensitive information.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"exchange_server","vendor":"microsoft"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"An information disclosure vulnerability exists when Microsoft Exchange improperly handles objects in memory, aka \"Microsoft Exchange Memory Corruption Vulnerability.\" This affects Microsoft Exchange Server. This CVE ID is unique from CVE-2018-8154.","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":"Information disclosure in Microsoft Exchange Server","id":"CVE-2018-8151","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:exchange_server","products":["microsoft:exchange_server"],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in Microsoft Exchange Server","id":"CVE-2018-8152"},"packages":[],"prev":{"headline":"Security feature bypass in Microsoft Office","id":"CVE-2018-8150"},"products":["Microsoft Exchange Server"],"published":"2018-05-09","related":[{"cvss_score":9.8,"headline":"Microsoft Exchange Server Privilege Escalation","id":"CVE-2024-21410","kev_date_added":"2024-02-15","published":"2024-02-13"},{"cvss_score":9.1,"headline":"Microsoft Exchange Server Remote Code Execution","id":"CVE-2021-34473","kev_date_added":"2021-11-03","published":"2021-07-14"},{"cvss_score":9.1,"headline":"Microsoft Exchange Server Remote Code Execution","id":"CVE-2021-26855","kev_date_added":"2021-11-03","published":"2021-03-02"},{"cvss_score":9,"headline":"Microsoft Exchange Server Privilege Escalation","id":"CVE-2021-34523","kev_date_added":"2021-11-03","published":"2021-07-14"},{"cvss_score":8.8,"headline":"Microsoft Exchange Server Deserialization of Untrusted Data","id":"CVE-2023-21529","kev_date_added":"2026-04-13","published":"2023-02-14"},{"cvss_score":8.8,"headline":"Microsoft Exchange Server Privilege Escalation","id":"CVE-2022-41080","kev_date_added":"2023-01-10","published":"2022-11-09"},{"cvss_score":8.8,"headline":"Microsoft Exchange Server Server-Side Request Forgery","id":"CVE-2022-41040","kev_date_added":"2022-09-30","published":"2022-10-03"}],"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-05","vendors":["Microsoft"]},"summary":"Attackers can exploit improper memory handling in Microsoft Exchange Server to disclose sensitive information.","url":"https://insights.sbomify.com/CVE-2018-8151/"}