{"answers":{"affected":"It affects 6 products.","exploited":"There is no known exploitation of CVE-2010-0025 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2010-0025 yet. Limit exposure of the affected software until one is available.","what":"CVE-2010-0025 is a medium-severity vulnerability in Microsoft Exchange Server, published on 14 Apr 2010. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2010-0025 and fix it if it is affected.\n\nWhat it is: CVE-2010-0025 is a medium-severity vulnerability in Microsoft Exchange Server, published on 14 Apr 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2010-0025 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-2010-0025/ (Markdown: https://insights.sbomify.com/CVE-2010-0025/index.md)","id":"CVE-2010-0025","markdown":"https://insights.sbomify.com/CVE-2010-0025/index.md","name":"CVE-2010-0025","record":{"aliases":["GHSA-hx33-6cv9-3m88"],"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":"Remote attackers can read fragments of email messages by sending invalid SMTP commands followed by STARTTLS, affecting Microsoft Exchange and Windows SMTP services.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"exchange_server","vendor":"microsoft"},{"product":"windows_2000","vendor":"microsoft"},{"product":"windows_2003_server","vendor":"microsoft"},{"product":"windows_server_2003","vendor":"microsoft"},{"product":"windows_server_2008","vendor":"microsoft"},{"product":"windows_xp","vendor":"microsoft"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The SMTP component in Microsoft Windows 2000 SP4, XP SP2 and SP3, Server 2003 SP2, and Server 2008 Gold, SP2, and R2, and Exchange Server 2000 SP3, does not properly allocate memory for SMTP command replies, which allows remote attackers to read fragments of e-mail messages by sending a series of invalid commands and then sending a STARTTLS command, aka \"SMTP Memory Allocation 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":"Information disclosure in n/a","id":"CVE-2010-0025","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:exchange_server","products":["microsoft:exchange_server","microsoft:windows_2000","microsoft:windows_2003_server","microsoft:windows_server_2003","microsoft:windows_server_2008","microsoft:windows_xp"],"type":"information_disclosure","year":"2010"},"n_packages":0,"n_references":4,"next":{"headline":"Denial of service in n/a","id":"CVE-2010-0026"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2010-0024"},"products":["n/a"],"published":"2010-04-14","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-07","vendors":["n/a"]},"summary":"Remote attackers can read fragments of email messages by sending invalid SMTP commands followed by STARTTLS, affecting Microsoft Exchange and Windows SMTP services.","url":"https://insights.sbomify.com/CVE-2010-0025/"}