Astonishingly, the private keys were 4, 56, 66, 115, 155, 156, 230, 237.

exploiting compromised certificates requires an active adversary-in-the-middle attack, meaning the attacker must act as a proxy between two TLS parties and receive encrypted traffic, decrypt it, reencrypt it, and send it to the other party. Such capabilities, in some cases, are usually limited to only the most well-resourced attackers. People with control of a local network—at a coffee shop, university, or other organization—face much less of a challenge.

https://emudhra.we-have-a-problem.com/

Xkcd 221: int getRandomNumber() { return 4; // chosen by fair dice roll. guaranteed to be random. }

  • @thisbenzingring@lemmy.today
    link
    fedilink
    English
    272•
    edit-2
    23 days ago

    I think that this isn’t really getting the right attention, about what a massive WTF situation this is…

    its a 384 bit certificate and this is the private key

    00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:
    00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:
    00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:
    00:00:04

    that is just fucking NUTS

    • Scrubbles
      link
      fedilink
      English
      116•23 days ago

      Phew to think how close it is to my private key

    • @Fmstrat@lemmy.world
      link
      fedilink
      English
      43•
      edit-2
      22 days ago

      And 8 of them no less. The guess of this being test code leaking into prod is likely, but security focused companies need consequences for stuff like this. That being said:

      • @prime_number_314159@lemmy.world
        link
        fedilink
        English
        11•22 days ago

        Winning the lottery is (ballpark) 1 in 10^9, so generating a key below a million is like winning 11 lotteries in a row, while buying 1 ticket in each.

        They wouldn’t know how you’d done it, but I think you’d be arrested, with valid probable cause.

    • @Blackmist@feddit.uk
      link
      fedilink
      English
      10•
      edit-2
      22 days ago
      4E:65:76:65:72:20:67:6F:6E:6E:61:20:67:69:76:
      65:20:79:6F:75:20:75:70:20:4E:65:76:65:72:20:
      67:6F:6E:6E:61:20:6C:65:74:20:79:6F:75:20:64:
      6F:77:6E
      

      is much more secure.

    • @ramble81@lemmy.zip
      link
      fedilink
      English
      7•22 days ago

      I mean, yes, it’s entirely possible and within the realm of probability of getting that as a key. But realistically it’s very, very, fucking unlikely.

      • Kraiden
        link
        fedilink
        English
        10•22 days ago

        Ye, I’d struggle to believe ONE key getting generated like that, but 8 points to pure incompetence

        • @ramble81@lemmy.zip
          link
          fedilink
          English
          9•22 days ago

          Yes, be in is why having 8 of them total in the 2 digit range (I.e only using up to 6 bits of 384-bits) just screams incompetence of a hand generated key.