curl before version 7.51.0 doesn’t parse the authority component of the URL correctly when the host name part ends with a ‘#’ character, and could instead be tricked into connecting to a different host. This may have security implications if you for example use an URL parser that follows the RFC to check for allowed domains before using curl to request them.
www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html
www.securityfocus.com/bid/94103
www.securitytracker.com/id/1037192
access.redhat.com/errata/RHSA-2018:2486
access.redhat.com/errata/RHSA-2018:3558
bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-8624
curl.haxx.se/docs/adv_20161102J.html
lists.apache.org/thread.html/r58af02e294bd07f487e2c64ffc0a29b837db5600e33b6e698b9d696b%40%3Cissues.bookkeeper.apache.org%3E
lists.apache.org/thread.html/rf4c02775860db415b4955778a131c2795223f61cb8c6a450893651e4%40%3Cissues.bookkeeper.apache.org%3E
lists.apache.org/thread.html/rfaa4d578587f52a9c4d176af516a681a712c664e3be440a4163691d5%40%3Ccommits.pulsar.apache.org%3E
security.gentoo.org/glsa/201701-47
www.tenable.com/security/tns-2016-21