CWE
20
Advisory Published
Updated

CVE-2010-1690: Input Validation

First published: Fri May 07 2010(Updated: )

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.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
Microsoft Windows 2000=sp4
Microsoft Windows 2000=sp1
Microsoft Windows 2000=sp2
Microsoft Windows 2000=sp3
Microsoft Windows XP=sp3
Microsoft Windows XP=sp2
Microsoft Windows XP=sp1
Microsoft Windows Server=sp1
Microsoft Windows Server=sp2
Microsoft Windows Server=sp1
Microsoft Windows Server=sp2
Microsoft Windows Server=r2
Microsoft Exchange Server=2003-sp1
Microsoft Exchange Server=2003-sp2
Microsoft Exchange Server=2007-sp1
Microsoft Exchange Server=2003
Microsoft Exchange Server=2007
Microsoft Exchange Server=2010
Microsoft Exchange Server=2007-sp2

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2010-1690?

    CVE-2010-1690 has a high severity rating due to its potential to allow remote code execution through DNS query manipulation.

  • How do I fix CVE-2010-1690?

    To fix CVE-2010-1690, update the affected systems to the latest service packs or security updates provided by Microsoft.

  • What software is affected by CVE-2010-1690?

    CVE-2010-1690 affects Microsoft Windows 2000, Windows XP, Windows Server 2003, Windows Server 2008, and specific versions of Exchange Server.

  • What are the potential impacts of CVE-2010-1690?

    The potential impacts of CVE-2010-1690 include unauthorized access, data theft, and execution of arbitrary code on affected systems.

  • Is CVE-2010-1690 still relevant today?

    While CVE-2010-1690 is considered old, systems running outdated software versions remain vulnerable and should be updated.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203