Language Selection

English French German Italian Portuguese Spanish

Another Protocol Bites The Dust

Filed under
Security

For the last 6 weeks or so, a bunch of us have been working on a really serious issue in SSL. In short, a man-in-the-middle can use SSL renegotiation to inject an arbitrary prefix into any SSL session, undetected by either end.

To make matters even worse, through a piece of (in retrospect) incredibly bad design, HTTP servers will, under some circumstances, replay that arbitrary prefix in a new authentication context. For example, this is what happens if you configure Apache to require client certificates for one directory but not another. Once it emerges that your request is for a protected directory, a renegotiation will occur to obtain the appropriate client certificate, and then the original request (i.e. the stuff from the bad guy) gets replayed as if it had been authenticated by the client certificate. But it hasn’t.

Not that the picture is all rosy even when client certificates are not involved.




Vulnerability in SSL/TLS protocol

h-online.com: According to reports, vulnerabilities in the SSL/TLS protocol can be exploited by attackers to insert content into secure connections. If this is correct, it would affect HTTPS and all other protocols which use TLS for security, including IMAP. The precise effects of the problem are not discussed in the reports. It would, however, appear to be possible to manipulate HTML content from websites during data transfer and, for example, inject malicious code.

The crux of the problem is, rather than a flawed implementation, a design flaw in the TLS protocol when renegotiating parameters for an existing TLS connection. This occurs when, for example, a client wants to access a secure area on a web server which requires the requesting client certificates. When the server establishes that is the case, it begins a renegotiation to obtain the appropriate client certificate. The original request gets replayed during this renegotiation as if it had been authenticated by the client certificate, but it has not. The discoverer of the problem describes this as an "authentication gap".

Rest Here

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Leftovers: OSS

Development News

  • GCC 7 Moves Onto Only Regression/Doc Fixes, But Will Accept RISC-V & HSA's BRIG
    The GNU Compiler Collection (GCC) is entering its "stage four" development for GCC 7 with the stable GCC 7.1 release expected in March or April. Richard Biener announced today that GCC 7 is under stage four, meaning only regression and documentation fixes will be permitted until the GCC 7.1.0 stable release happens (yep, as per their peculiar versioning system, GCC 7.1 is the first stable release in the GCC 7 series).
  • 5 ways to expand your project's contributor base
    So many free and open source software projects were started to solve a problem, and people began to contribute to them because they too wanted a fix to what they encountered. End users of the project find it useful for their needs, and the project grows. And that shared purpose and focus attracts people to a project's community.
  • Weblate 2.10.1
    This is first security bugfix release for Weblate. This has to come at some point, fortunately the issue is not really severe. But Weblate got it's first CVE ID today, so it's time to address it in a bugfix release.

Intel Kabylake: Windows 10 vs. Linux OpenGL Performance

For those curious about the current Kabylake graphics performance between Windows 10 and Linux, here are some OpenGL benchmark results under each operating system. Windows 10 Pro x64 was tested and the Linux distributions for comparison were Ubuntu 16.10, Clear Linux, Antergos, Fedora 25 Xfce, and openSUSE Tumbleweed. Read more

Google's open-source Tilt Brush: Now you can create 3D movies in VR