TLS proxies: Insecure by design, say boffins

Home antivirus is rubbish, so you don't use it on your work PCs. Do you?


Have you ever suspected filters that decrypt traffic of being insecure? Canadian boffins agree with you, and have said that TLS proxies – commonly deployed in both business and home networks for traffic inspection – open up cans of worms.

“Not a single TLS proxy implementation is secure with respect to all of our tests, sometimes leading to trivial server impersonation under an active man-in-the-middle attack, as soon as the product is installed on a system," wrote Xavier de Carné de Carnavalet and Mohammad Mannan of the Concordia Institute of Systems Engineering in Montreal.

The trio's paper (PDF) goes on to say that users could be exposed to man-in-the-middle attacks or other CA-based impersonations.

While the researchers focused their attention on consumer anti-virus and Web filtering products, The Register reckons at least one of their warnings is borne out in the enterprise space.

It's not enough that vulnerabilities like POODLE and FREAK are patched by project maintainers, for example: customers of downstream products that happen to use the buggy software have to wait until their specific patches are available.

As de Carnavalet and Mannan write, outdated proxies might “lack support for safe protocol versions and cipher suites, undermining the significant effort spent on securing web browsers.“

The researchers tested eight antivirus and four parental control products (all for Windows), and two products that import a CA root certificate, checking their vulnerability for MITM attacks.

The depressing assertion:

We found that four products are vulnerable to full server impersonation under an active man-in-the-middle (MITM) attack out-of-the-box, and two more if TLS filtering is enabled. Several of these tools also mislead browsers into believing that a TLS connection is more secure than it actually is, by e.g., artificially upgrading a server’s TLS version at the client.

There's also the matter of how products protect their root certificates' private key. It's not pretty, as the table below shows.

Location Protection Access
Avast CAPI Exportable key Admin
AVG Config file Obfuscation Unknown
BitDefender DER file Hardcoded passphrase User
BullGuard AV DER reg key Hardcoded passphrase User
BullGuard IS DER reg key Hardcoded passphrase User
CYBERsitter CER file Plaintext User
Dr Web CAPI-cert1 Exportable key Admin
ESET CAPI Non-exportable key Admin
G DATA Registry Obfuscated encryption User
Kaspersky DER file Plaintext User
KinderGate CER file Plaintext User
Net Nanny Database Modified SQL Cipher User
PC Pandora CAPI-cert Non-exportable key Admin
ZoneAlarm DER file Plaintext User

Although key recovery was non-trivial, the authors note “we retrieved four passphrase-protected private keys and a key stored in a custom encrypted SQLCipher database”.

Here's another treat: “The version of Kaspersky we analyzed in March 2015 continues to act as a TLS proxy when a 30-day trial period is expired; however, after the license expiration, it accepts all certificates, including the invalid ones”. Although fixed later, people who installed the pre-fix product and never uninstalled it are therefore MITM-vulnerability.

For the home user, de Carnavalet reckons filters that simply block domain names are probably effective enough.

The Register keenly hopes de Carnavalet and Mannan get the chance to repeat their tests against corporate proxies, and will keep some popcorn for just such an event. ®

Similar topics


Other stories you might like

  • Stolen university credentials up for sale by Russian crooks, FBI warns
    Forget dark-web souks, thousands of these are already being traded on public bazaars

    Russian crooks are selling network credentials and virtual private network access for a "multitude" of US universities and colleges on criminal marketplaces, according to the FBI.

    According to a warning issued on Thursday, these stolen credentials sell for thousands of dollars on both dark web and public internet forums, and could lead to subsequent cyberattacks against individual employees or the schools themselves.

    "The exposure of usernames and passwords can lead to brute force credential stuffing computer network attacks, whereby attackers attempt logins across various internet sites or exploit them for subsequent cyber attacks as criminal actors take advantage of users recycling the same credentials across multiple accounts, internet sites, and services," the Feds' alert [PDF] said.

    Continue reading
  • Big Tech loves talking up privacy – while trying to kill privacy legislation
    Study claims Amazon, Apple, Google, Meta, Microsoft work to derail data rules

    Amazon, Apple, Google, Meta, and Microsoft often support privacy in public statements, but behind the scenes they've been working through some common organizations to weaken or kill privacy legislation in US states.

    That's according to a report this week from news non-profit The Markup, which said the corporations hire lobbyists from the same few groups and law firms to defang or drown state privacy bills.

    The report examined 31 states when state legislatures were considering privacy legislation and identified 445 lobbyists and lobbying firms working on behalf of Amazon, Apple, Google, Meta, and Microsoft, along with industry groups like TechNet and the State Privacy and Security Coalition.

    Continue reading
  • SEC probes Musk for not properly disclosing Twitter stake
    Meanwhile, social network's board rejects resignation of one its directors

    America's financial watchdog is investigating whether Elon Musk adequately disclosed his purchase of Twitter shares last month, just as his bid to take over the social media company hangs in the balance. 

    A letter [PDF] from the SEC addressed to the tech billionaire said he "[did] not appear" to have filed the proper form detailing his 9.2 percent stake in Twitter "required 10 days from the date of acquisition," and asked him to provide more information. Musk's shares made him one of Twitter's largest shareholders. The letter is dated April 4, and was shared this week by the regulator.

    Musk quickly moved to try and buy the whole company outright in a deal initially worth over $44 billion. Musk sold a chunk of his shares in Tesla worth $8.4 billion and bagged another $7.14 billion from investors to help finance the $21 billion he promised to put forward for the deal. The remaining $25.5 billion bill was secured via debt financing by Morgan Stanley, Bank of America, Barclays, and others. But the takeover is not going smoothly.

    Continue reading

Biting the hand that feeds IT © 1998–2022