During installation, the router sent several data packets to an Amazon server in the US. These packets contained the configured SSID name and password in clear text, as well as some identification tokens for this network within a broader database and an access token for a user session that could potentially enable a MITM attack.

Linksys has refused to acknowledge/respond to the issue.

  • partial_accumenEnglish
    76•5 months ago

    Two important points raised:

    • Why is Linksys sending your Wifi details, as well as your private password, outside of your home
    • If they’re doing it, why are they sending your critically important private information unencrypted onto the public internet

    The answer to the first one may be semi-legit as these are mesh products. As in, the other nodes in the mesh will need this information, and it appears that Linksys has decided to store your security data in AWS for the other mesh nodes to retrieve it when you’re setting it up. I’d sure as hell like to know this before the product does this. Further, I’d much prefer to simply attached to each mesh node myself to input the secured credentials instead of sending them outside to the internet.

    There’s not excuse for Linksys sending the creds unencrypted onto the internet.

      • @[email protected]English
        13•5 months ago

        I’m just finding no confirmation that they send them unencrypted over the Internet

        Even if they were sending them with proper E2EE to their server, that would still be a huge fucking problem.

      • @[email protected]English
        5•5 months ago

        and I’ve seen “researchers” calling sending passwords over HTTPS “unencrypted.”

        That’s because the password is unencrypted.

        HTTPS will encrypt the channel and the data in flight, but the data is still unencrypted and anyone with a key that validated (assuming it actually checks for certificate validity) now has access to your unencrypted password. So yes, even over HTTPS it should be considered unencrypted.

        Whether or not they’re sending it over an encrypted channel, they’re still sending out an unencrypted password that they have no need for. Linksys has no reason to need the unencrypted password, and at best would only need a hashed password to accomplish whatever business case they’re sending that to solve. We have to assume that they’re also saving it in clear text given how they’re sending it in the clear as well.

        No password should ever leave your network unencrypted, no matter the data channel encryption. Anything less is negligence , and the vendor should not be trusted.

      • @[email protected]English
        5•5 months ago

        calling sending passwords over HTTPS “unencrypted.”

        The channel is encrypted, the content is not. It is a password, why would they need it?

        • @[email protected]English
          1•5 months ago

          Because now they have your login and password - not a hashed version they can only validate against, but the real thing that can be used to log into your network. They shouldn’t ever have it, aside from them being able to sell credentials this also means someone else could probably obtain access to all of them

      • @[email protected]English
        3•5 months ago

        How would they know that the device sends the SSID and password otherwise? If it was encrypted you would not be able to read the content of the packages.

        • NatanaelEnglish
          2•5 months ago

          If you get root on the device you can MITM it by extracting session keys

    • @[email protected]English
      2•5 months ago

      Even then, the other nodes would only need the hash of the password, not the password itself.

      • NatanaelEnglish
        2•5 months ago

        That depends entirely on the auth system, but you can use a separate credential to retrieve the password (using something like a PAKE algorithm)