Vulnerability Note VU#366544
Adtrustmedia PrivDog fails to validate SSL certificates
Original Release date: 23 Feb 2015 | Last revised: 26 Feb 2015
Adtrustmedia PrivDog fails to validate SSL certificates, making systems broadly vulnerable to HTTPS spoofing.
Adtrustmedia PrivDog is a Windows application that advertises "… safer, faster and more private web browsing." Privdog installs a Man-in-the-Middle (MITM) proxy as well as a new trusted root CA certificate. The MITM capabilities are provided by NetFilterSDK.com. Although the root CA certificate is generated at install time, resulting in a different certificate for each installation, Privdog does not use the SSL certificate validation capabilities that the NetFilter SDK provides. This means that web browsers will not display any warnings when a spoofed or MITM-proxied HTTPS website is visited. We have confirmed that PrivDog version 220.127.116.11 is affected.
Adtrustmedia PrivDog is promoted by the Comodo Group, which is an organization that offers SSL certificates and authentication solutions.
Users can test whether they are vulnerable to the PrivDog vulnerability and other similar vulnerabilities by visiting Filippo Valsorda’s SSL test page.
An attacker can spoof HTTPS sites and intercept HTTPS traffic without triggering browser certificate warnings in affected systems.
Apply an update
This issue is addressed in PrivDog 18.104.22.168. This version of PrivDog appears to disable SSL interception for connections where the upstream certificate is not valid. Alternatively, consider the following workaround:
Uninstalling PrivDog will remove the MITM proxy and the root CA certificate, thus restoring SSL validation to affected systems.
Vendor Information (Learn More)
VendorStatusDate NotifiedDate UpdatedAdTrustMediaAffected-23 Feb 2015
COMODO Security Solutions, Inc.Not Affected23 Feb 201526 Feb 2015
NetFilterSDK.comUnknown-23 Feb 2015If you are a vendor and your product is affected, let
CVSS Metrics (Learn More)
This vulnerability was publicly reported by Hanno Böck.
This document was written by Will Dormann.
22 Feb 2015
Date First Published:
23 Feb 2015
Date Last Updated:
26 Feb 2015
FeedbackIf you have feedback, comments, or additional information about this vulnerability, please send us email.