As usual, you can also use this squid post to talk about the security stories in the news that I haven’t covered.
The original article/video can be found at Friday Squid Blogging: Striped Pyjama Squid Pet Sculpture
In the episode that aired on May 9th, about eight or nine minutes in, there’s a scene with a copy of Applied Cryptography prominently displayed on the coffee table. This isn’t the first time that my books have appeared on that TV show.
The original article/video can be found at Applied Cryptography on Elementary
Currently, many public web sites that allow access via IPv6 do so via proxies. This is seen as the “quick fix”, as it requires minimum changes to the site itself. As far as the web application is concerned, all incoming traffic is IPv4.
The most obvious issue here is logging, in that the application only “sees” the proxies IP address, unless it inspects headers added by the proxy, which will no point to (unreadable?) IPv6 addresses.
But there is another issue: SSL Certificates. If only IPv6 connections are passed via the proxy, you will end up with two different certificate: One for the proxy, and one for the web application (or the IPv4 proxy). It may also happen that the IPv6 and IPv4 site are considered two different hosts on the web server, requiring distinct configurations.
For example, at this point, “www.socialsecurity.gov” uses two different certificates. One for IPv6 and one for IPv4. The IPv6 certifiate is expired, while the IPv4 certificate is valid. This is in particularly painful as some simple comand line tools, like “openssl s_client' are still not able to work over IPv6. For my test, I used gnutls-cli, which works similar to openssl s_client but supports IPv6.
Excerpt from the result:
Next, lets try IPv4. A disadvantage of gnutls-cli is that you are not able to force an IPv4 connection, so I will just fall back to openssl here:
(c) SANS Internet Storm Center. http://isc.sans.edu Creative Commons Attribution-Noncommercial 3.0 United States License.
The original article/video can be found at SSL: Another reason not to ignore IPv6, (Fri, May 17th)
VU#774103: Linux kernel perf_swevent_enabled array out-of-bound access privilege escalation vulnerability
Vulnerability Note VU#774103
Linux kernel perf_swevent_enabled array out-of-bound access privilege escalation vulnerability
Original Release date: 17 May 2013 | Last revised: 17 May 2013
The Linux kernel’s Performance Events implementation is susceptible to an out-of-bounds array vulnerability that may be used by a local unprivileged user to escalate privileges.
The Linux kernel’s Performance Events implementation is susceptible to an out-of-bounds array vulnerability that may be used by a local unprivileged user to escalate privileges. Additional analysis of the vulnerability may be found in the Red Hat bug report. A public exploit is available that has been reported to work against some Linux distributions.
A local authenticated user may be able to exploit this vulnerability to escalate privileges.
Apply an Update
Other distributions may be affected but were not confirmed at the time of publication.
If you are unable to upgrade, please consider the following workaround.
Red Hat has provided mitigation advice in Red Hat Knowledge Solution 373743.
Vendor Information (Learn More)
|Vendor||Status||Date Notified||Date Updated|
|CentOS||Affected||-||17 May 2013|
|Debian GNU/Linux||Affected||-||17 May 2013|
|Red Hat, Inc.||Affected||-||17 May 2013|
|Ubuntu||Affected||-||17 May 2013|
|Fedora Project||Unknown||-||17 May 2013|
|Slackware Linux Inc.||Unknown||-||17 May 2013|
|SUSE Linux||Unknown||-||17 May 2013|
If you are a vendor and your product is affected, let
CVSS Metrics (Learn More)
Tommi Rantala discovered this vulnerability.
This document was written by Jared Allar.
14 May 2013
Date First Published:
17 May 2013
Date Last Updated:
17 May 2013
If you have feedback, comments, or additional information about this vulnerability, please send us email.
The original article/video can be found at VU#774103: Linux kernel perf_swevent_enabled array out-of-bound access privilege escalation vulnerability