medium
4.3
CWE
200
Advisory Published
Updated

CVE-2010-0644: Infoleak

First published: Thu Feb 18 2010(Updated: )

Google Chrome before 4.0.249.89, when a SOCKS 5 proxy server is configured, sends DNS queries directly, which allows remote DNS servers to obtain potentially sensitive information about the identity of a client user via request logging, as demonstrated by a proxy server that was configured for the purpose of anonymity.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
Google Chrome (Trace Event)=2.0.172.8
Google Chrome (Trace Event)=0.3.154.3
Google Chrome (Trace Event)=3.0.182.2
Google Chrome (Trace Event)=0.2.149.30
Google Chrome (Trace Event)=0.4.154.31
Google Chrome (Trace Event)=1.0.154.39
Google Chrome (Trace Event)=2.0.172.38
Google Chrome (Trace Event)=1.0.154.59
Google Chrome (Trace Event)=0.2.149.27
Google Chrome (Trace Event)=1.0.154.53
Google Chrome (Trace Event)=0.4.154.33
Google Chrome (Trace Event)=2.0.170.0
Google Chrome (Trace Event)=1.0.154.43
Google Chrome (Trace Event)=1.0.154.42
Google Chrome (Trace Event)=2.0.169.1
Google Chrome (Trace Event)=2.0.172.33
Google Chrome (Trace Event)=3.0.195.24
Google Chrome (Trace Event)=3.0.195.33
Google Chrome (Trace Event)=1.0.154.52
Google Chrome (Trace Event)=2.0.172.27
Google Chrome (Trace Event)=1.0.154.65
Google Chrome (Trace Event)=2.0.157.2
Google Chrome (Trace Event)=0.4.154.18
Google Chrome (Trace Event)=0.2.149.29
Google Chrome (Trace Event)=2.0.157.0
Google Chrome (Trace Event)=0.2.152.1
Google Chrome (Trace Event)=0.3.154.0
Google Chrome (Trace Event)<=4.0.249.78
Google Chrome (Trace Event)=0.2.153.1
Google Chrome (Trace Event)=2.0.172.2
Google Chrome (Trace Event)=3.0.195.21
Google Chrome (Trace Event)=2.0.169.0
Google Chrome (Trace Event)=1.0.154.36
Google Chrome (Trace Event)=2.0.172
Google Chrome (Trace Event)=2.0.172.30
Google Chrome (Trace Event)=3.0.193.2-beta
Google Chrome (Trace Event)=2.0.156.1
Google Chrome (Trace Event)=3.0.195.32
Google Chrome (Trace Event)=1.0.154.46
Google Chrome (Trace Event)=3.0.190.2
Google Chrome (Trace Event)=0.4.154.22
Google Chrome (Trace Event)=2.0.159.0
Google Chrome (Trace Event)=2.0.158.0
Google Chrome (Trace Event)=2.0.172.28
Google Chrome (Trace Event)=2.0.172.31
Google Chrome (Trace Event)=1.0.154.48
Google Chrome (Trace Event)=2.0.172.37
Google Chrome<=4.0.249.78
Google Chrome=0.2.149.27
Google Chrome=0.2.149.29
Google Chrome=0.2.149.30
Google Chrome=0.2.152.1
Google Chrome=0.2.153.1
Google Chrome=0.3.154.0
Google Chrome=0.3.154.3
Google Chrome=0.4.154.18
Google Chrome=0.4.154.22
Google Chrome=0.4.154.31
Google Chrome=0.4.154.33
Google Chrome=1.0.154.36
Google Chrome=1.0.154.39
Google Chrome=1.0.154.42
Google Chrome=1.0.154.43
Google Chrome=1.0.154.46
Google Chrome=1.0.154.48
Google Chrome=1.0.154.52
Google Chrome=1.0.154.53
Google Chrome=1.0.154.59
Google Chrome=1.0.154.65
Google Chrome=2.0.156.1
Google Chrome=2.0.157.0
Google Chrome=2.0.157.2
Google Chrome=2.0.158.0
Google Chrome=2.0.159.0
Google Chrome=2.0.169.0
Google Chrome=2.0.169.1
Google Chrome=2.0.170.0
Google Chrome=2.0.172
Google Chrome=2.0.172.2
Google Chrome=2.0.172.8
Google Chrome=2.0.172.27
Google Chrome=2.0.172.28
Google Chrome=2.0.172.30
Google Chrome=2.0.172.31
Google Chrome=2.0.172.33
Google Chrome=2.0.172.37
Google Chrome=2.0.172.38
Google Chrome=3.0.182.2
Google Chrome=3.0.190.2
Google Chrome=3.0.193.2-beta
Google Chrome=3.0.195.21
Google Chrome=3.0.195.24
Google Chrome=3.0.195.32
Google Chrome=3.0.195.33

Remedy

http://googlechromereleases.blogspot.com/2010/02/stable-channel-update.html

Remedy

http://www.vupen.com/english/advisories/2010/0361

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.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

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

    CVE-2010-0644 has a moderate severity level due to the potential exposure of sensitive information through direct DNS queries.

  • How do I fix CVE-2010-0644?

    To fix CVE-2010-0644, update Google Chrome to version 4.0.249.89 or later.

  • What versions of Google Chrome are affected by CVE-2010-0644?

    CVE-2010-0644 affects all versions of Google Chrome prior to 4.0.249.89.

  • What is the impact of CVE-2010-0644 on user privacy?

    CVE-2010-0644 can allow remote DNS servers to log user requests, potentially compromising user privacy.

  • Is there a workaround for CVE-2010-0644 if I cannot update?

    A workaround for CVE-2010-0644 is to configure the browser to avoid using any SOCKS 5 proxy servers.

Company

Resources

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