Security
BadUSB: Clever but not novel
The annual Black Hat security conference often has eye-opening talks and demonstrations, but it also suffers from over-hyped presentations at times. The press coverage of this year's event was replete with references to the "BadUSB" talk that looked at the damage that can be caused by malicious USB devices. But, as discussions on the oss-security mailing list and elsewhere show, these ideas are not particularly new, nor especially surprising—at least to those who have been paying attention over the years.
The basic idea behind BadUSB is that USB devices have firmware that controls how they interact with the computers they get plugged into. If that firmware can be subverted—again, no real surprise that it can be—it can cause the USB device to do various surprising things: masquerade as a different kind of device (e.g. a storage device that acts like a keyboard), copy files, intercept file accesses to substitute malware, modify host network settings, and more. Changing the firmware of a USB device makes the device a persistent attack vector, but it is not just removable devices that are susceptible. Many systems, especially laptops, come with built-in USB devices (e.g. cameras). Infecting the firmware of those (which may not be as easy) would effectively persistently compromise the whole system.
But malicious USB devices are nothing new. In a Google+ post, Greg Kroah-Hartman pointed to the USB Rubber Ducky as an longstanding example of a programmable USB device that could used for malicious purposes. On the other side of the coin, Kees Cook used the Facedancer USB fuzzer to find lots of holes in the Linux USB stack (which have now been patched).
Whenever a USB device—a USB flash device, a phone for charging over USB, a mouse, or something more exotic—is plugged into a system, there is a fair amount of trust being placed in that device. If it claims to be an input device, the OS will treat it as such—even if it looks like a flash device to the user. That's part of where the problem lies; there are multiple types of USB devices that have different capabilities, but the type a device claims to be is not readily apparent from the outside. On the flip side, though, devices like the YubiKey can use that ability to do their job: presenting itself as a keyboard to input passwords.
Some of the attacks demonstrated and discussed at the Black Hat talk (slides [PDF], video [YouTube]) used the multi-function aspect of USB devices to inject commands as a keyboard or to redirect DNS queries when masquerading as network device (by replying to a DHCP request with the address of a malicious DNS server, but no default gateway, so traffic still routes over the existing network). The attacks presented are clever and, perhaps, not well-known, but they are hardly revolutionary—as some breathless articles might lead one to believe.
Dan Carpenter raised the issue on the oss-security mailing list, but the discussion there made it clear that there is nothing particularly new about BadUSB. In fact, Kroah-Hartman claimed:
In that thread, there were concerns about rewriting the firmware in the host controllers (the system hardware that handles USB communication), but no examples were offered (despite repeated requests). It is not just USB that suffers from these problems, however, as Dean Pierce (and others) pointed out; any bus or connector that allows hotplugging (e.g. Firewire, ExpressCard, Thunderbolt, even PCI) can have exactly the same issues. In fact, some of those hotpluggable devices can initiate direct memory access (DMA) operations, which leads to another whole level of attack possibilities.
But Pierce also wanted a way to disable USB hotplug, which is something
that the Linux kernel has provided for a long time. As Kroah-Hartman noted, you can turn off USB hotplug, but
"very few people take advantage of it
". This command:
echo "0" > /sys/module/usbcore/parameters/authorized_default
will turn off authorization for any USB devices that are plugged in,
effectively disabling any malfeasance that BadUSB (or anything else) might
attempt. In another message, he further
explained the values for authorized_default beyond the 0 used
above. The default -1 value
means that all plugged-in USB devices are authorized, except for
wireless network devices that must be explicitly authorized. The other
possible value is 1, which authorizes all USB devices that are
plugged in.
The only real benefit of all of the publicity around BadUSB (beyond Kroah-Hartman's tongue-in-cheek cost savings) is that it has raised the profile of this kind of attack. To those who are particularly security conscious or technically savvy, there may be nothing new here, but to many, including some with a lot of computer knowledge, BadUSB is surprising—even startling. So the publicity may lead to people being more careful with what devices they blithely plug into their systems.
It is pretty well established that allowing an attacker physical access to your system is not a path to happiness. In some sense, BadUSB just extends that idea further. Plugging random hardware into a system leaves you vulnerable to anything that hardware is capable of—whether you expect it or not.
Brief items
Security quotes of the week
Through suitable cryptanalysis and signal processing, we have extracted 4096-bit RSA keys and 3072-bit ElGamal keys from laptops, via each of these channels, as well as via power analysis and electromagnetic probing. Despite the GHz-scale clock rate of the laptops and numerous noise sources, the full attacks require a few seconds of measurements using Medium Frequency signals (around 2 MHz), or one hour using Low Frequency signals (up to 40 kHz).
Google boosting sites that use HTTPS
Google has announced that it is starting to look favorably on sites that use HTTPS. "We’ve seen positive results, so we’re starting to use HTTPS as a ranking signal. For now it's only a very lightweight signal—affecting fewer than 1% of global queries, and carrying less weight than other signals such as high-quality content—while we give webmasters time to switch to HTTPS. But over time, we may decide to strengthen it, because we’d like to encourage all website owners to switch from HTTP to HTTPS to keep everyone safe on the web."
New vulnerabilities
389-ds-base: information disclosure
| Package(s): | 389-ds-base | CVE #(s): | CVE-2014-3562 | ||||||||||||||||||||||||||||||||||||
| Created: | August 8, 2014 | Updated: | August 18, 2014 | ||||||||||||||||||||||||||||||||||||
| Description: | From the Red Hat advisory: "It was found that when replication was enabled for each attribute in 389 Directory Server, which is the default configuration, the server returned replicated metadata when the directory was searched while debugging was enabled. A remote attacker could use this flaw to disclose potentially sensitive information." | ||||||||||||||||||||||||||||||||||||||
| Alerts: |
| ||||||||||||||||||||||||||||||||||||||
ansible: code execution
| Package(s): | ansible | CVE #(s): | CVE-2014-4966 CVE-2014-4967 | ||||||||||||||||
| Created: | August 8, 2014 | Updated: | August 25, 2014 | ||||||||||||||||
| Description: | The ansible configuration management system suffers from two vaguely described privilege escalation vulnerabilities. | ||||||||||||||||||
| Alerts: |
| ||||||||||||||||||
chicken: code execution
| Package(s): | chicken | CVE #(s): | CVE-2014-3776 | ||||||||||||
| Created: | August 8, 2014 | Updated: | August 13, 2014 | ||||||||||||
| Description: | The chicken Scheme compiler suffers from a buffer overflow exploitable to cause denial of service (or worse) via a "#f" value in the NUM argument. | ||||||||||||||
| Alerts: |
| ||||||||||||||
drupal: denial of service
| Package(s): | drupal7 | CVE #(s): | CVE-2014-5265 CVE-2014-5266 CVE-2014-5267 | ||||||||||||||||||||||||||||
| Created: | August 11, 2014 | Updated: | September 26, 2014 | ||||||||||||||||||||||||||||
| Description: | From the Debian advisory:
A denial of service vulnerability was discovered in Drupal, a fully-featured content management framework. A remote attacker could exploit this flaw to cause CPU and memory exhaustion and the site's database to reach the maximum number of open connections, leading to the site becoming unavailable or unresponsive. More information can be found at https://www.drupal.org/SA-CORE-2014-004. Update: CVEs were assigned. See also the Red Hat bug report. | ||||||||||||||||||||||||||||||
| Alerts: |
| ||||||||||||||||||||||||||||||
drupal7-views: access control bypass
| Package(s): | drupal7-views | CVE #(s): | |||||||||
| Created: | August 11, 2014 | Updated: | August 13, 2014 | ||||||||
| Description: | From the Drupal advisory:
The module doesn't sufficiently check handler access when returning the list of handlers from view_plugin_display::get_handlers(). The most critical code (access plugins and field output) is unaffected - only area handlers, the get_field_labels() method, token replacement, and some relationship handling are susceptible. | ||||||||||
| Alerts: |
| ||||||||||
krb5: multiple vulnerabilities
| Package(s): | krb5 | CVE #(s): | CVE-2014-4341 CVE-2014-4342 CVE-2014-4343 CVE-2014-4344 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Created: | August 8, 2014 | Updated: | August 13, 2014 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description: | The krb5 system suffers from a failure to properly process malformed GSSAPI messages, a double-free bug, and a null pointer dereference, all of which can be used to force an application crash. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Alerts: |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
krb5: code execution
| Package(s): | krb5 | CVE #(s): | CVE-2014-4345 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Created: | August 11, 2014 | Updated: | October 14, 2014 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description: | From the Debian advisory:
CVE-2014-4345: When kadmind is configured to use LDAP for the KDC database, an authenticated remote attacker can cause it to perform an out-of-bounds write (buffer overflow). | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Alerts: |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
libav: multiple vulnerabilities
| Package(s): | libav | CVE #(s): | CVE-2011-3934 CVE-2011-3935 CVE-2011-3946 CVE-2013-0848 CVE-2013-0851 CVE-2013-0852 CVE-2013-0860 CVE-2013-0868 CVE-2013-3672 CVE-2013-3674 CVE-2014-2263 | ||||||||||||||||||||
| Created: | August 11, 2014 | Updated: | February 9, 2015 | ||||||||||||||||||||
| Description: | From the libav changelog for version 0.8.14:
vp3: Copy all 3 frames for thread updates (CVE-2011-3934) mpegts: Do not try to write a PMT larger than SECTION_SIZE (CVE-2014-2263) error_concealment: avoid using the picture if not fully setup (CVE-2013-0860) cdgraphics: switch to bytestream2 (CVE-2013-3674) huffyuvdec: check width size for yuv422p (CVE-2013-0848) mmvideo: check horizontal coordinate too (CVE-2013-3672) huffyuv: Check and propagate function return values (CVE-2013-0868) h264: prevent theoretical infinite loop in SEI parsing (CVE-2011-3946) pgssubdec: Check RLE size before copying (CVE-2013-0852) eamad: use the bytestream2 API instead of AV_RL (CVE-2013-0851) | ||||||||||||||||||||||
| Alerts: |
| ||||||||||||||||||||||
openssl: multiple vulnerabilities
| Package(s): | openssl | CVE #(s): | CVE-2014-3505 CVE-2014-3506 CVE-2014-3507 CVE-2014-3508 CVE-2014-3509 CVE-2014-3510 CVE-2014-3511 CVE-2014-3512 CVE-2014-5139 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Created: | August 7, 2014 | Updated: | December 29, 2014 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description: | The August 6, 2014 OpenSSL security advisory describes a number of newly fixed vulnerabilities:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Alerts: |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
openstack-keystone: privilege escalation
| Package(s): | openstack-keystone | CVE #(s): | CVE-2014-2828 CVE-2014-3476 | ||||||||
| Created: | August 8, 2014 | Updated: | October 23, 2014 | ||||||||
| Description: | Versions of openstack-keystone prior to 2013.2.4 suffer from a denial of service vulnerability due to failed input sanitization (CVE-2014-2828) and a privilege escalation vulnerability resulting from a failure to properly handle chained delegation (CVE-2014-3476). | ||||||||||
| Alerts: |
| ||||||||||
trafficserver: mysterious vulnerability
| Package(s): | trafficserver | CVE #(s): | CVE-2014-3525 | ||||||||||||
| Created: | August 8, 2014 | Updated: | July 6, 2015 | ||||||||||||
| Description: | According to this advisory, versions of Apache Traffic Server prior to 4.2.11 or 5.0.1 are affected by some sort of unspecified vulnerability. | ||||||||||||||
| Alerts: |
| ||||||||||||||
v8: denial of service
| Package(s): | v8 | CVE #(s): | |||||||||
| Created: | August 8, 2014 | Updated: | August 15, 2014 | ||||||||
| Description: | From the Fedora update: "A memory corruption vulnerability, which results in a denial-of-service, was identified in the versions of V8 that ship with Node.js 0.8 and 0.10. In certain circumstances, a particularly deep recursive workload that may trigger a GC and receive an interrupt may overflow the stack and result in a segmentation fault." | ||||||||||
| Alerts: |
| ||||||||||
wireshark: multiple vulnerabilities
| Package(s): | wireshark | CVE #(s): | CVE-2014-5164 CVE-2014-5165 CVE-2014-5163 CVE-2014-5161 CVE-2014-5162 | ||||||||||||||||||||||||||||||||
| Created: | August 8, 2014 | Updated: | September 2, 2014 | ||||||||||||||||||||||||||||||||
| Description: | Another set of dissector vulnerabilities has been fixed in wireshark; this time, the RLC, IrDA, Catapult DCT2000, GTP and GSM Management, and ASN.1 BER dissectors are affected. | ||||||||||||||||||||||||||||||||||
| Alerts: |
| ||||||||||||||||||||||||||||||||||
wordpress: multiple vulnerabilities
| Package(s): | wordpress | CVE #(s): | CVE-2014-5203 CVE-2014-5204 CVE-2014-5205 CVE-2014-5240 | ||||||||||||||||
| Created: | August 11, 2014 | Updated: | August 26, 2014 | ||||||||||||||||
| Description: | From the WordPress advisory:
This release fixes a possible denial of service issue in PHP’s XML processing, reported by Nir Goldshlager of the Salesforce.com Product Security Team. It was fixed by Michael Adams and Andrew Nacin of the WordPress security team and David Rothstein of the Drupal security team. This is the first time our two projects have coordinated joint security releases. WordPress 3.9.2 also contains other security changes:
Update: CVEs were added. | ||||||||||||||||||
| Alerts: |
| ||||||||||||||||||
Page editor: Jake Edge
Next page:
Kernel development>>
