Bluetooth ExpoitsSummary.
========
A recent posting from A.L. Digital suggests that security flaws exist in Bluetooth, while not describing the vulnerabilities in any technical detail. This email concerns itself specifically with the vulnerabilities related to retrieval of personal information from devices.
Some of the attacks described have been known about for some time and discussed (or hinted at) in public before, at BlackHat/Defcon (Las Vegas) by FX of Phenoelit (More Embedded Systems), at Defcon by Bruce Potter of Shmoo and most recently by Alexander Grimm, Marcel Holtmann and Andreas Vedral at the Wireless Technologies Congress.
Detail.
=======
It is incorrect to assume that these vulnerabilities exist because of a lack of security in Bluetooth itself. These vulnerabilities are purely the result of design errors in the host devices, and Bluetooth is simply the transport mechanism over which the attacks can be carried out. The vulnerabilities occur in some of the OBEX profiles used by manufacturers to transfer arbitrary information via Bluetooth.
In particular the OBEX Push Profile is often unprotected whereas the OBEX FTP profile is not. The name of the profile is also misleading as you would believe that the OBEX Push would only allow files to be uploaded. However the profile also allows information retrieval.
The OBEX vulnerabilities can be divided into two categories, PUT and GET. As is implied from the names, they refer to information being sent to or returned by the host device. Both PUT and GET actions can be restricted by the need to pair, however some manufacturers have chosen to remove this restriction to add extra features, such as vCard exchanging.
It should be noted here that OBEX is protocol independent and it is
possible to exploit the vulnerabilities via IrDA and even via serial
connection. It should also be noted that OBEX does have the ability to manage authentication. However, this is not used by any of the devices we have tested over the past three months.
The rest of the information contained here will be based on un-paired and un-trusted devices attacking a target device.
Much more information can be obtained from many devices by physical contact or social engineering, however this is not a deficiency in Bluetooth or the host device. Due to the prompt given by some devices, it is possible to trick the user into pairing. However this is a form of social engineering.
These vulnerabilities exist whether the Bluetooth device is in
discoverable mode or not.
Vulnerabilities.
=================
OBEX PUT vulnerabilities.
-------------------------
This series of attacks relates to the movement of information towards the target device. These attacks are based upon information extracted from the IrMC specification, which describes several interesting files.
The IrMC specification can be found at:
http://www.irda.org/standards/pubs/IrMC_v1p1Specs_Errata001024.zip
These files are often accessible via unprotected Bluetooth profiles. While they can be viewed on protected profiles, some manufacturers choose to also enable this via un-protected profiles such as "OBEX Push". OBEX also has a DELETE action, which is a PUT with an empty body, by pushing to each of the phone book entries it would be possible to overwrite or delete all
of the phone book entries. A solution for manufacturers would be to separate the PUT functions into specific profiles and not allow the same actions via all profiles.
OBEX GET vulnerabilities.
-------------------------
While similar to the PUT vulnerabilities, these present a much more of a serious threat including invasion of privacy. All vulnerable files are mentioned in the IrMC specification.
Once again these files are usually only accessible via protected Bluetooth profiles, however, it appears that some manufacturers have used the same code to implement the un-protected services and thus the files are visible.
Fixes.
======
1) Only enable Bluetooth when absolutely necessary.
2) Place the device in non-discoverable mode. While this does not correct the fault, it is harder to find the target device. There can be problems with this, some Nokia devices fail will to connect properly when hidden.
3) Refuse any pair attempt or content transfer unless it is from a known and trusted device/source.
The ultimate fix is for manufacturers to provide a greater separation of services, an attitude that seems to have been taken with the Ericsson T610.
Current state of alerts.
========================
The information relating to these vulnerabilities has been in the public domain for some time. However, until the recent bugtraq and full disclosure posts, the consequences of these issues was not widely advertised. A number of affected vendors have already been contacted with varied degrees of response.
Researchers.
============
Mark Rowe, Pentest Limited.
Tim Hurman, Pentest Limited.
Contact: bluetooth at pentest.co.uk
Red Hat Security AdvisorySynopsis: Updated glibc packages provide security and bug fixes
Advisory ID: RHSA-2003:325-01
Issue date: 2003-11-12
Updated on: 2003-11-13
Product: Red Hat Linux
Keywords: netlink getgrouplist
Cross references:
Obsoletes: RHSA-2003:212
CVE Names: CAN-2003-0689 CAN-2003-0859
- ---------------------------------------------------------------------
1. Topic:
Updated glibc packages that resolve vulnerabilities and address several bugs
are now available.
2. Relevant releases/architectures:
Red Hat Linux 7.1 - i386, i686
Red Hat Linux 7.2 - i386, i686, ia64
Red Hat Linux 7.3 - i386, i686
Red Hat Linux 8.0 - i386, i686
Red Hat Linux 9 - i386, i686
3. Problem description:
The glibc packages contain GNU libc, which provides standard system libraries.
A bug in the getgrouplist function can cause a buffer overflow if
the size of the group list is too small to hold all the user's groups.
This overflow can cause segmentation faults in user applications, which may
have security implications, depending on the application in question. This
vulnerability exists only when an administrator has placed a user in a
number of groups larger than that expected by an application. Therefore,
there is no risk in instances where users are members of few groups. The
Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned
the name CAN-2003-0689 to this issue.
Herbert Xu reported that various applications can accept spoofed messages
sent on the kernel netlink interface by other users on the local machine.
This could lead to a local denial of service attack. In Red Hat Linux 9
and later, the glibc function getifaddrs uses netlink and could therefore
be vulnerable to this issue. The Common Vulnerabilities and Exposures
project (cve.mitre.org) has assigned the name CAN-2003-0859 to this issue.
In addition to the security issues, a number of other bugs were fixed.
Users are advised to upgrade to these erratum packages, which contain a
patch that checks that netlink messages actually came from the kernel, a
backported security patch for the getgroups list vulnerability, and patches
for the various bug fixes.
[Update 2003-11-13]: The packages for Red Hat Linux 9 have been updated
for compatibility with kernels not provided by Red Hat.
4. Solution:
Before applying this update, make sure all previously released errata
relevant to your system have been applied.
To update all RPMs for your particular architecture, run the following
command at a shell prompt:
rpm -Fvh [filenames]
where [filenames] is a list of the RPMs you wish to upgrade. On the i686
architecture, *.i686.rpm packages should be installed where available
rather than *.i386.rpm.
If you are unsure which architecture you are on, run the following
command at a shell prompt:
rpm -q --qf '%{arch}\n' glibc
Only those RPMs which are currently installed will be updated. Those RPMs
which are not installed but included in the list will not be updated.
Note that you can also use wildcards (*.rpm) if your current directory
only contains the desired RPMs.
Please note that this update is also available via Red Hat Network. Many
people find this an easier way to apply updates. To use Red Hat Network,
launch the Red Hat Update Agent with the following command:
up2date
This will start an interactive process that will result in the appropriate
RPMs being upgraded on your system.
If up2date fails to connect to Red Hat Network due to SSL Certificate
Errors, you need to install a version of the up2date client with an updated
certificate. The latest version of up2date is available from the Red Hat
FTP site and may also be downloaded directly from the RHN website:
https://rhn.redhat.com/help/latest-up2date.pxt
5. Bug IDs fixed (http://bugzilla.redhat.com/bugzilla for more info):
54697 - nscd locks immediately if started with -t 1 and nss_ldap is used
83973 - Wrong sort order for uk_UA locale
85994 - SIGSEGV in malloc: __morecore clobbered by perror conflict with _IO_check_libio
86032 - trailing spaces in /etc/ld.so.conf entries are not ignored
88409 - strxfrm() overruns buffer by indexing with uninitialized value
88456 - glibc-2.3.2-27.9.i686.rpm does not rpm -Fvh properly.
88978 - locale ja_JP.EUC-JP has two undefined bytes [buffer overrun]
89448 - getaddrinfo segv - unitialized structure?
90002 - binary compatibility for '_res' broken in glibc 2.3.x
90036 - race/deadlock in fork() with signal handler.
90077 - fopen@GLIBC_2_0 corrupts memory arena by buffer overrun
90301 - Programs fail at exit if compiled with gcc and cxa_atexit
90987 - sprintf() is limited to 2^26 bytes.
91567 - setegid sets saved gid
97814 - "Incorrectly built binary which accesses errno..." message in elf/rtld.c needs some way to be silenced.
97828 - Sudo returns segmentation fault
98966 - ldconfig automatically prepends /usr/lib and /lib to search order
101261 - getnameinfo fails to to reverse lookup on IPv6 addresses
101691 - CAN-2003-0689 Buffer overrun in getgrouplist function in initgroups.c
102709 - NPTL pthread_cond_broadcast hangs.
103727 - LD_PROFILE=libc.so.6 and sprof give seg fault
105348 - Closing socket breaks the cancellation type of current thread
107846 - locale utility is broken on big-endian 64-bit platforms
108634 - Signal handler installation races with signal, glibc-2.3.2
109904 - problems after [RHSA-2003:325-01] glibc upgrades
109918 - executable code in .data in ld.so renders system unusable for PaX users
6. RPMs required:
Red Hat Linux 7.1:
SRPMS:
ftp://updates.redhat.com/7.1/en/os/SRPMS/glibc-2.2.4-33.src.rpm
i386:
ftp://updates.redhat.com/7.1/en/os/i386/glibc-2.2.4-33.i386.rpm
ftp://updates.redhat.com/7.1/en/os/i386/glibc-common-2.2.4-33.i386.rpm
ftp://updates.redhat.com/7.1/en/os/i386/glibc-devel-2.2.4-33.i386.rpm
ftp://updates.redhat.com/7.1/en/os/i386/glibc-profile-2.2.4-33.i386.rpm
ftp://updates.redhat.com/7.1/en/os/i386/nscd-2.2.4-33.i386.rpm
i686:
ftp://updates.redhat.com/7.1/en/os/i686/glibc-2.2.4-33.i686.rpm
Red Hat Linux 7.2:
SRPMS:
ftp://updates.redhat.com/7.2/en/os/SRPMS/glibc-2.2.4-33.src.rpm
i386:
ftp://updates.redhat.com/7.2/en/os/i386/glibc-2.2.4-33.i386.rpm
ftp://updates.redhat.com/7.2/en/os/i386/glibc-common-2.2.4-33.i386.rpm
ftp://updates.redhat.com/7.2/en/os/i386/glibc-devel-2.2.4-33.i386.rpm
ftp://updates.redhat.com/7.2/en/os/i386/glibc-profile-2.2.4-33.i386.rpm
ftp://updates.redhat.com/7.2/en/os/i386/nscd-2.2.4-33.i386.rpm
i686:
ftp://updates.redhat.com/7.2/en/os/i686/glibc-2.2.4-33.i686.rpm
ia64:
ftp://updates.redhat.com/7.2/en/os/ia64/glibc-2.2.4-33.ia64.rpm
ftp://updates.redhat.com/7.2/en/os/ia64/glibc-common-2.2.4-33.ia64.rpm
ftp://updates.redhat.com/7.2/en/os/ia64/glibc-devel-2.2.4-33.ia64.rpm
ftp://updates.redhat.com/7.2/en/os/ia64/glibc-profile-2.2.4-33.ia64.rpm
ftp://updates.redhat.com/7.2/en/os/ia64/nscd-2.2.4-33.ia64.rpm
Red Hat Linux 7.3:
SRPMS:
ftp://updates.redhat.com/7.3/en/os/SRPMS/glibc-2.2.5-44.src.rpm
i386:
ftp://updates.redhat.com/7.3/en/os/i386/glibc-2.2.5-44.i386.rpm
ftp://updates.redhat.com/7.3/en/os/i386/glibc-common-2.2.5-44.i386.rpm
ftp://updates.redhat.com/7.3/en/os/i386/glibc-debug-2.2.5-44.i386.rpm
ftp://updates.redhat.com/7.3/en/os/i386/glibc-debug-static-2.2.5-44.i386.rpm
ftp://updates.redhat.com/7.3/en/os/i386/glibc-devel-2.2.5-44.i386.rpm
ftp://updates.redhat.com/7.3/en/os/i386/glibc-profile-2.2.5-44.i386.rpm
ftp://updates.redhat.com/7.3/en/os/i386/glibc-utils-2.2.5-44.i386.rpm
ftp://updates.redhat.com/7.3/en/os/i386/nscd-2.2.5-44.i386.rpm
i686:
ftp://updates.redhat.com/7.3/en/os/i686/glibc-2.2.5-44.i686.rpm
ftp://updates.redhat.com/7.3/en/os/i686/glibc-debug-2.2.5-44.i686.rpm
Red Hat Linux 8.0:
SRPMS:
ftp://updates.redhat.com/8.0/en/os/SRPMS/glibc-2.3.2-4.80.8.src.rpm
i386:
ftp://updates.redhat.com/8.0/en/os/i386/glibc-2.3.2-4.80.8.i386.rpm
ftp://updates.redhat.com/8.0/en/os/i386/glibc-common-2.3.2-4.80.8.i386.rpm
ftp://updates.redhat.com/8.0/en/os/i386/glibc-debug-2.3.2-4.80.8.i386.rpm
ftp://updates.redhat.com/8.0/en/os/i386/glibc-debug-static-2.3.2-4.80.8.i386.rpm
ftp://updates.redhat.com/8.0/en/os/i386/glibc-devel-2.3.2-4.80.8.i386.rpm
ftp://updates.redhat.com/8.0/en/os/i386/glibc-profile-2.3.2-4.80.8.i386.rpm
ftp://updates.redhat.com/8.0/en/os/i386/glibc-utils-2.3.2-4.80.8.i386.rpm
ftp://updates.redhat.com/8.0/en/os/i386/nscd-2.3.2-4.80.8.i386.rpm
i686:
ftp://updates.redhat.com/8.0/en/os/i686/glibc-2.3.2-4.80.8.i686.rpm
ftp://updates.redhat.com/8.0/en/os/i686/glibc-debug-2.3.2-4.80.8.i686.rpm
Red Hat Linux 9:
SRPMS:
ftp://updates.redhat.com/9/en/os/SRPMS/glibc-2.3.2-27.9.7.src.rpm
i386:
ftp://updates.redhat.com/9/en/os/i386/glibc-2.3.2-27.9.7.i386.rpm
ftp://updates.redhat.com/9/en/os/i386/glibc-common-2.3.2-27.9.7.i386.rpm
ftp://updates.redhat.com/9/en/os/i386/glibc-debug-2.3.2-27.9.7.i386.rpm
ftp://updates.redhat.com/9/en/os/i386/glibc-devel-2.3.2-27.9.7.i386.rpm
ftp://updates.redhat.com/9/en/os/i386/glibc-profile-2.3.2-27.9.7.i386.rpm
ftp://updates.redhat.com/9/en/os/i386/glibc-utils-2.3.2-27.9.7.i386.rpm
ftp://updates.redhat.com/9/en/os/i386/nscd-2.3.2-27.9.7.i386.rpm
i686:
ftp://updates.redhat.com/9/en/os/i686/glibc-2.3.2-27.9.7.i686.rpm
ftp://updates.redhat.com/9/en/os/i686/nptl-devel-2.3.2-27.9.7.i686.rpm
Red Hat Security AdvisorySynopsis: Updated Ethereal packages fix security issues
Advisory ID: RHSA-2003:323-01
Issue date: 2003-11-10
Updated on: 2003-11-10
Product: Red Hat Linux
Keywords: ethereal SOCKS buffer overflow
Cross references:
Obsoletes: RHSA-2003:203
CVE Names: CAN-2003-0925 CAN-2003-0926 CAN-2003-0927
- ---------------------------------------------------------------------
1. Topic:
Updated Ethereal packages that fix a number of exploitable security issues
are now available.
2. Relevant releases/architectures:
Red Hat Linux 7.2 - i386, ia64
Red Hat Linux 7.3 - i386
Red Hat Linux 8.0 - i386
Red Hat Linux 9 - i386
3. Problem description:
Ethereal is a program for monitoring network traffic.
A number of security issues affect Ethereal. By exploiting these issues,
it may be possible to make Ethereal crash or run arbitrary code by
injecting a purposefully-malformed packet onto the wire or by convincing
someone to read a malformed packet trace file.
A buffer overflow in Ethereal 0.9.15 and earlier allows remote attackers
to cause a denial of service and possibly execute arbitrary code via a
malformed GTP MSISDN string. The Common Vulnerabilities and Exposures
project (cve.mitre.org) has assigned the name CAN-2003-0925 to
this issue.
Ethereal 0.9.15 and earlier allows remote attackers to cause a denial of
service (crash) via certain malformed ISAKMP or MEGACO packets. The Common
Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name
CAN-2003-0926 to this issue.
A heap-based buffer overflow in Ethereal 0.9.15 and earlier allows
remote attackers to cause a denial of service (crash) and possibly
execute arbitrary code via the SOCKS dissector. The Common Vulnerabilities
and Exposures project (cve.mitre.org) has assigned the name CAN-2003-0927
to this issue.
Users of Ethereal should update to these erratum packages containing
Ethereal version 0.9.16, which is not vulnerable to these issues.
4. Solution:
Before applying this update, make sure all previously released errata
relevant to your system have been applied.
Please note that this update is available via Red Hat Network. To use Red
Hat Network, launch the Red Hat Update Agent with the following command:
up2date
This will start an interactive process that will result in the appropriate
RPMs being upgraded on your system.
5. RPMs required:
Red Hat Linux 7.2:
SRPMS:
ftp://updates.redhat.com/7.2/en/os/SRPMS/ethereal-0.9.16-0.72.1.src.rpm
i386:
ftp://updates.redhat.com/7.2/en/os/i386/ethereal-0.9.16-0.72.1.i386.rpm
ftp://updates.redhat.com/7.2/en/os/i386/ethereal-gnome-0.9.16-0.72.1.i386.rpm
ia64:
ftp://updates.redhat.com/7.2/en/os/ia64/ethereal-0.9.16-0.72.1.ia64.rpm
ftp://updates.redhat.com/7.2/en/os/ia64/ethereal-gnome-0.9.16-0.72.1.ia64.rpm
Red Hat Linux 7.3:
SRPMS:
ftp://updates.redhat.com/7.3/en/os/SRPMS/ethereal-0.9.16-0.73.1.src.rpm
i386:
ftp://updates.redhat.com/7.3/en/os/i386/ethereal-0.9.16-0.73.1.i386.rpm
ftp://updates.redhat.com/7.3/en/os/i386/ethereal-gnome-0.9.16-0.73.1.i386.rpm
Red Hat Linux 8.0:
SRPMS:
ftp://updates.redhat.com/8.0/en/os/SRPMS/ethereal-0.9.16-0.80.1.src.rpm
i386:
ftp://updates.redhat.com/8.0/en/os/i386/ethereal-0.9.16-0.80.1.i386.rpm
ftp://updates.redhat.com/8.0/en/os/i386/ethereal-gnome-0.9.16-0.80.1.i386.rpm
Red Hat Linux 9:
SRPMS:
ftp://updates.redhat.com/9/en/os/SRPMS/ethereal-0.9.16-0.90.1.src.rpm
i386:
ftp://updates.redhat.com/9/en/os/i386/ethereal-0.9.16-0.90.1.i386.rpm
ftp://updates.redhat.com/9/en/os/i386/ethereal-gnome-0.9.16-0.90.1.i386.rpm
6. Verification:
MD5 sum Package Name
- --------------------------------------------------------------------------
51b11630b7e941a445b9e5b3c78bad71 7.2/en/os/SRPMS/ethereal-0.9.16-0.72.1.src.rpm
d82608ed91c6eedf65727684c6db5305 7.2/en/os/i386/ethereal-0.9.16-0.72.1.i386.rpm
4f77f1ff00345c5ac17fab320d266623 7.2/en/os/i386/ethereal-gnome-0.9.16-0.72.1.i386.rpm
6dd40a5f31ab113ba0e0165f8c1a50e4 7.2/en/os/ia64/ethereal-0.9.16-0.72.1.ia64.rpm
d7b8d27500bdb6a81b1b2040c994299a 7.2/en/os/ia64/ethereal-gnome-0.9.16-0.72.1.ia64.rpm
1851780c3ca9c4b41154fde464f7baa5 7.3/en/os/SRPMS/ethereal-0.9.16-0.73.1.src.rpm
3606cb008369c2d23de53e595c1e4a3b 7.3/en/os/i386/ethereal-0.9.16-0.73.1.i386.rpm
8db80d03f546cf633ff2346e57ff4492 7.3/en/os/i386/ethereal-gnome-0.9.16-0.73.1.i386.rpm
ea4799792230ece8074d766371e377f5 8.0/en/os/SRPMS/ethereal-0.9.16-0.80.1.src.rpm
3f794942c054cc80e211e235d2bd80a6 8.0/en/os/i386/ethereal-0.9.16-0.80.1.i386.rpm
eb651ff758ac8e58e5edbac838930df8 8.0/en/os/i386/ethereal-gnome-0.9.16-0.80.1.i386.rpm
45868a8ab244bee8b26454bd64c8894c 9/en/os/SRPMS/ethereal-0.9.16-0.90.1.src.rpm
b0397b5f2745d05ebc9775bcf46ae26f 9/en/os/i386/ethereal-0.9.16-0.90.1.i386.rpm
f29f45d6e0c2f5eba2fb524df3ead36d 9/en/os/i386/ethereal-gnome-0.9.16-0.90.1.i386.rpm
These packages are GPG signed by Red Hat for security. Our key is
available from https://www.redhat.com/security/keys.html
You can verify each package with the following command:
rpm --checksig -v
If you only wish to verify that each package has not been corrupted or
tampered with, examine only the md5sum with the following command:
md5sum
7. References:
http://www.ethereal.com/appnotes/enpa-sa-00011.html
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2003-0925
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2003-0926
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2003-0927
8. Contact:
The Red Hat security contact is . More contact
details at https://www.redhat.com/solutions/security/news/contact.htm
