IDNA 2003 makes curl use wrong host
When curl is built with libidn to handle International Domain Names (IDNA), it translates them to puny code for DNS resolving using the IDNA 2003 standard, while IDNA 2008 is the modern and up-to-date IDNA standard. This misalignment causes problems with for example domains using the German ß character (known as the Unicode Character `LATIN SMALL LETTER SHARP S`) which is used at times in the `.de` TLD and is translated differently in the two IDNA standards, leading to users potentially and unknowingly issuing network transfer requests to the wrong host. For example, `straße.de` is translated into `strasse.de` using IDNA 2003 but is translated into `xn--strae-oqa.de` using IDNA 2008. Needless to say, those hostnames could well resolve to different addresses and be two completely independent servers. IDNA 2008 is mandatory for `.de` domains. curl is not alone with this problem, as there is currently a big flux in the world of network user-agents about which IDNA version to support and use. This name problem exists for DNS-using protocols in curl, but only when built to use libidn.
02 / AFFECTED SOFTWARE
Affected packages
139 explicit affected versions
165 explicit affected versions
03 / CONNECTIONS
Connected vulnerabilities
04 / EVIDENCE
Source records
curl before version 7.51.0 uses outdated IDNA 2003 standard to handle International Domain Names and this may lead users to potentially and unknowingly issue network transfer requests to the wrong host.
When curl is built with libidn to handle International Domain Names (IDNA), it translates them to puny code for DNS resolving using the IDNA 2003 standard, while IDNA 2008 is the modern and up-to-date IDNA standard. This misalignment causes problems with for example domains using the German ß character (known as the Unicode Character `LATIN SMALL LETTER SHARP S`) which is used at times in the `.de` TLD and is translated differently in the two IDNA standards, leading to users potentially and unknowingly issuing network transfer requests to the wrong host. For example, `straße.de` is translated into `strasse.de` using IDNA 2003 but is translated into `xn--strae-oqa.de` using IDNA 2008. Needless to say, those hostnames could well resolve to different addresses and be two completely independent servers. IDNA 2008 is mandatory for `.de` domains. curl is not alone with this problem, as there is currently a big flux in the world of network user-agents about which IDNA version to support and use. This name problem exists for DNS-using protocols in curl, but only when built to use libidn.
05 / REFERENCES
Further evidence
- http://www.securityfocus.com/bid/94107
- http://www.securitytracker.com/id/1037192
- https://access.redhat.com/errata/RHSA-2018:2486
- https://access.redhat.com/errata/RHSA-2018:3558
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-8625
- https://curl.haxx.se/CVE-2016-8625.patch
- https://curl.haxx.se/docs/adv_20161102K.html
- https://lists.apache.org/thread.html/r58af02e294bd07f487e2c64ffc0a29b837db5600e33b6e698b9d696b%40%3Cissues.bookkeeper.apache.org%3E
- https://lists.apache.org/thread.html/rf4c02775860db415b4955778a131c2795223f61cb8c6a450893651e4%40%3Cissues.bookkeeper.apache.org%3E
- https://security.gentoo.org/glsa/201701-47
- https://www.tenable.com/security/tns-2016-21