Access member only content, take part in discussions with comments on blogs, news and reviews and receive all the latest security industry news directly to your inbox. Join now for free.
Processing registration... Please wait.
This process can take up to a minute to complete.
A confirmation email has been sent to your email address - SUPPLIED EMAIL HERE. Please click on the link in the email to verify your email address. You need to verify your email before you can start posting.
If you do not receive your confirmation email within the next few minutes, it may be because the email has been captured by a junk mail filter. Please ensure you add the domain @scmagazine.com.au to your white-listed senders.
Enterprises using Cyberoam deep packet inspection devices could have traffic intercepted by anyone using its shared certificate.
Tor Project security researcher Runa Sandvik and OpenSSL's Ben Laurie discovered the devices used the same Certificate Authority certificate and private key.
That gaffe made it possible for any DPI box to grab traffic from employees monitored by Cyberoam devices.
“It is therefore possible to intercept traffic from any victim (employee) of a Cyberoam device with any other Cyberoam device — or, indeed, to extract the key from the device and import it into other DPI devices, and use those for interception,” Sandvik said in an advisory.
“Victims should uninstall the Cyberoam CA certificate from their browsers and decline to complete any connection which gives a certificate warning.”
Sandvik and Laurie began researching the hole after a Tor user in Jordan reported seeing a fake Cyberoam certificate for the TorProject.org. They discovered the user’s traffic was intercepted by a Cyberoam device.
Trusted certificates had to be installed on employee machines, referred to as victims, in order for DPI to work. But that Cyberoam victims all installed the same trusted CA which would issue fake certificates was “a little surprising” Sandvik said.
The Tor boffin alerted Indian-based Cyberoam about the flaw (CVE-2012-3372) on June 30 and her intention to publish an advisory on July 3.
The company acknowledged the vulnerability and said it would investigate. The company has been contacted by SC for comment.
Users can delete the root CA by following these instructions.
Copyright © SC Magazine, Australia
To begin commenting right away, you can log in below or register an account if you don't yet have one. Please read our guidelines on commenting. Offending posts will be removed and your access may be suspended. Abusive or obscene language will not be tolerated. The comments below do not necessarily reflect the views or opinions of SC Magazine, Haymarket Media or its employees.