Share.

    2 Kommentare

    1. Flashy-Whereas-3234 on

      Tldr; cloudflare Certificate url /.well-known/acme-challenge/{token} if hit by something other than cloudflare would let the request hit the protected server instead.

      The risk is seeing headers and exploiting known vulnerabilities of servers, as you can now hit a server that should have been entirely unreachable, but you still can’t hit different URLs unless you find another exploit to leverage.

      Security researchers were eager to make it sound worse than it was by demonstrating that this lets you – get this – exploit servers with existing vulnerabilities.

      Big oops.

    2. celeryandcucumber on

      Kudos for the person discovering this, as its one of the things someone typically will overlook.

      I still wish LetsEncrypt would publish IP ranges so those could be explicitly whitelisted for http-challenges.

    Leave A Reply