I contacted Proton VPN about the TunnelVision exploit and I got a response. I feel great about it, thank you Proton!

Hi,

Thank you for your patience.

Our engineers have conducted a thorough analysis of this threat, reconstructed it experimentally, and tested it on Proton VPN. Please note that the attack can only be carried out if the local network itself is compromised.

Regardless, we’re working on a fix for our Linux application that will provide full protection against it, and it’ll be released as soon as possible.

If there’s anything else that I can help you with in the meantime, please feel free to let me know.

Have a nice day!

  • Kid@sh.itjust.worksMEnglish
    192·
    6 months ago

    Please note that the attack can only be carried out if the local network itself is compromised.

      • ryannathans@aussie.zoneEnglish
        241·
        6 months ago

        To be fair if you used it on a public network like an airport or restaurant… yeah

        • 4am@lemm.eeEnglish
          23·
          6 months ago

          Yeah, it’s kind of incredible the responses I see to this story that are like “bro if they got as far as planting a rogue DHCP server on your network you were already owned anyway, yawn”

          Like, you do realize people use VPNs over unsecured WiFi all the time right? That’s one of the primary use cases. You can’t guarantee every network hasn’t been compromised.

          Armchair netsec quarterbacks need to get out more.

          • gencha@lemm.eeEnglish
            7·
            6 months ago

            If I learned one thing from TunnelVision, it’s how blindly people are operating right now. If you open a VPN tunnel, also ensure traffic is actually routed through it, especially if you don’t control the network. Adding a tunnel on top of the insecure network also does not protect your client from other malicious clients on that network. I feel like people have seen one too many VPN snake oil salesman on social media.

            • Socsa@sh.itjust.worksEnglish
              4·
              6 months ago

              I’ve been on this pedestal for years. Pop security YouTube has been overtly preying on rubes to sell shady VPN services for a decade now and it’s super cringe. There is no magic bullet to cyber security and it takes real effort and knowledge to be safe.

          • Socsa@sh.itjust.worksEnglish
            2·
            6 months ago

            I am skeptical of this being viable on public Wi-Fi tbh. You’d need to know ahead of time which VPN servers the target will attempt to contact, some information about the target ahead of time, and you need to DHCP poison the entire network prior to the target connecting. That would effectively bring down the network for all but two hosts - the attacker and target.

            I mean at that point, you can also just repeatedly deauth the target until it connects to your spoofed network and do whatever you want, and it would be way less obvious to an outside observer.

          • BarbecueCowboy@kbin.social
            1·
            6 months ago

            I think it’s because lot of us have been just kind of over-exposed to things like this. It’s like, yes, I’d imagine you could do a lot of interesting stuff if you’ve already compromised everything else first, thanks pen test. This one is not quite at that level, but I think we’re all just exhausted with similar ones, ya know.

            • atzanteol@sh.itjust.worksEnglish
              32·
              6 months ago

              Your derogatory tone and little-dick energy is hilariously over-the-top and just completely unwarranted. Go big or go home eh?

            • 4am@lemm.eeEnglish
              12·
              6 months ago

              Not a fucking thing you said matters if the exploit still exists because it can be used to get someone, somewhere.

              corporate policy

              Oh, there’s an air-tight solution. Let’s rely on everyone doing exactly the right thing every time, especially those nontechnical people. That never goes wrong.

              obviously you have years of experience in the field

              Not at all, but when there is a fucking CVE about it, blowharding about “eh it’s not really a big deal guy, trust me I know better” kinda makes me question the blowhard’s experience. I think I’ll go with the CVE and say that yeah, this is an issue that needs to be addressed.

              Also did you think my comment was a direct reply to yours? Have you not seen the multitude of other comments in other threads just writing this off like as if it can be ignored entirely? Yours, while flippant, was not even the worst of the bunch.

  • Socsa@sh.itjust.worksEnglish
    6·
    6 months ago

    I’m a bit confused how this is considered a new vulnerability. The IETF RFC which proposes option 121 literally states that malicious DHCP servers could be used to redirect traffic to malicious hosts, and I’m fairly confident that we learned about this exact thing in CCNA school in like 2003 (with regards to router configuration security).

    I suppose the application to a VPN attack might be relatively novel?