Vulnerability Note VU#260780
NetNanny uses a shared private key and root CA
Original Release date: 20 Apr 2015 | Last revised: 07 May 2015
NetNanny uses a shared private key and root Certificate Authority (CA), making systems broadly vulnerable to HTTPS spoofing.
NetNanny installs a Man-in-the-Middle (MITM) proxy as well as a new trusted root CA certificate. The certificate used by NetNanny is shared among all installations of NetNanny. Furthermore, the private key used to generate the certificate is also shared and may be obtained in plaintext directly from the software. An attacker may use this shared private key to generate new certificates that would be signed by and therefore trusted by NetNanny. An affected user would not be alerted to a false malicious HTTPS website as NetNanny would trust the spoofed certificate. NetNanny has provided more information on this issue on their FAQ.
We have confirmed that NetNanny version 188.8.131.52 is affected. Other versions may also be affected.
For more information on the impact of this issue on SSL inspection, please see Will Dormann’s CERT/CC blog post on SSL Inspection.
An attacker can spoof HTTPS sites and intercept HTTPS traffic without triggering browser certificate warnings in affected systems.
ContentWatch has released NetNanny for Windows version 184.108.40.206 which addresses these issues. Affected users should update as soon as possible.
Disable SSL filtering and remove the certificate
Affected users can disable SSL filtering using the interface, and manually delete the certificate from the operating system’s certificate store. This prevents the issue described above while leaving most other features of NetNanny intact.
Uninstalling NetNanny removes the root CA certificate from the operating system’s certificate store.
Vendor Information (Learn More)
VendorStatusDate NotifiedDate UpdatedContent WatchAffected27 Mar 201505 May 2015If you are a vendor and your product is affected, let
CVSS Metrics (Learn More)
Thanks to Imran Ghory for reporting this issue to us.
This document was written by Garret Wassermann.
20 Apr 2015
Date First Published:
20 Apr 2015
Date Last Updated:
07 May 2015
FeedbackIf you have feedback, comments, or additional information about this vulnerability, please send us email.