{"answers":{"affected":"It affects 5 products.","exploited":"There is no known exploitation of CVE-2010-1690 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2010-1690 yet. Limit exposure of the affected software until one is available.","what":"CVE-2010-1690 is a medium-severity vulnerability in Microsoft Exchange Server, published on 7 May 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-1690 and fix it if it is affected.\n\nWhat it is: CVE-2010-1690 is a medium-severity vulnerability in Microsoft Exchange Server, published on 7 May 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-1690 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-1690/ (Markdown: https://insights.sbomify.com/CVE-2010-1690/index.md)","id":"CVE-2010-1690","markdown":"https://insights.sbomify.com/CVE-2010-1690/index.md","name":"CVE-2010-1690","record":{"aliases":["GHSA-xc9g-2j8f-74wm"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Windows DNS Client","requires_auth":"none","summary":"Man-in-the-middle attackers can spoof DNS responses due to missing transaction ID verification in the Windows DNS client implementation.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"exchange_server","vendor":"microsoft"},{"product":"windows_2000","vendor":"microsoft"},{"product":"windows_server_2003","vendor":"microsoft"},{"product":"windows_server_2008","vendor":"microsoft"},{"product":"windows_xp","vendor":"microsoft"}],"cvss":{"score":6.4,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"The DNS implementation in smtpsvc.dll before 6.0.2600.5949 in Microsoft Windows 2000 SP4 and earlier, Windows XP SP3 and earlier, Windows Server 2003 SP2 and earlier, Windows Server 2008 SP2 and earlier, Windows Server 2008 R2, Exchange Server 2003 SP3 and earlier, Exchange Server 2007 SP2 and earlier, and Exchange Server 2010 does not verify that transaction IDs of responses match transaction IDs of queries, which makes it easier for man-in-the-middle attackers to spoof DNS responses, a different vulnerability than CVE-2010-0024 and CVE-2010-0025.","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":"Other in n/a","id":"CVE-2010-1690","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:exchange_server","products":["microsoft:exchange_server","microsoft:windows_2000","microsoft:windows_server_2003","microsoft:windows_server_2008","microsoft:windows_xp"],"type":"other","year":"2010"},"n_packages":0,"n_references":4,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2010-1691"},"packages":[],"prev":{"headline":"Weak cryptography in n/a","id":"CVE-2010-1689"},"products":["n/a"],"published":"2010-05-07","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-09-16","vendors":["n/a"]},"summary":"Man-in-the-middle attackers can spoof DNS responses due to missing transaction ID verification in the Windows DNS client implementation.","url":"https://insights.sbomify.com/CVE-2010-1690/"}