May 24, 2019

Apple closes two security vulnerabilities with release of Apple TV 5.2

Apple_TV_2nd_Generation(LiveHacking.Com) – Apple has released the a new firmware for its TV media box which adds the ability to play purchased iTunes music directly from iCloud along with Bluetooth keyboard support. The update also allows Apple TV users to send media from an Apple TV to AirPlay-enabled speakers and devices (including AirPort Express and other Apple TVs). At the same time as adding new functionality Apple has also closed two serious security holes.

The first vulnerability fixed is a issue which allowed user-mode process to access the first page of kernel memory. Nomrally the kernel has code to check that user-processes are not accessing kernel memory. However The checks were not being used if the length was smaller than one page. This issue was addressed through additional validation of the arguments to copyin and copyout.

The second securuiy flaw could allow a remote attacker on the same WiFi network to to cause an unexpected system termination. An out of bounds read issue exists in Broadcom’s BCM4325 and BCM4329 firmware’s handling of 802.11i information elements. This issue was addressed through additional validation of 802.11i information elements.

To check the version of the firmware on your device, select ”Settings -> General -> About”. Most users won’t need to do anything as Apple TV will regularly check for software updates. Alternatively, you may manually check for software updates by selecting ”Settings -> General -> Update Software”.

SMS fraud malware now targets OS X users

(LiveHacking.Com) –  SMS fraud is nothing new and is one of the preferred methods of generating income for malware writers on Android and on Windows. The Russian security firm Dr. Web has discovered a piece of malware which attempts to perpetrate SMS fraud on unsuspecting OS X users. Dubbed Trojan.SMSSend.3666, it  is the first program of its kind that targets Mac OS X.

With SMS fraud the malware writers attempt to subscribe victim’s to premium rate SMS services which charges high fees for useless messages. The Android variant is to cause the phone to send a message to one of these premium rate numbers.

The new Mac malware is a fake installer which can be downloaded under the guise of useful software. In this case, the Trojan pretends to be an installer for a program called VKMusic 4, a program meant for use on the VK social network. VK claims it is the largest European social network with more than a 100 million active users.

“In order to continue the ‘installation’ fraudsters ask that the victim enter their cellphone number into an appropriate field and then specify the code found in a reply SMS. By performing these actions the user agrees to terms of a chargeable subscription and a fee will be debited from their mobile phone account on a regular basis,” wrote Dr. Web.

Recent outbreaks of OS X malware have used vulnerabilities in Java, however this Trojan doesn’t use a known or unknown vulnerability, rather it is a simple social engineering ploy to trick the user into subscribing to a costly phone service. A relativity small number of OS X users will be affected as first it targets users of VK, second the OS X user needs to download the fake version of VKMusic from an underground web site.

It is anticipated that Apple’s XProtect malware utility will be updated to identify this new Trojan in due course.

New Apple TV software released with security fixes

(LiveHacking.Com) –  Apple has published V5.1.1 of its Apple TV software to fix two security issues. The software, which is available for Apple TV 2nd generation devices and later, addresses just two issues one of which could lead to arbitrary code execution.

The first issue fixes an information disclosure issue that existed in the handling of APIs related to kernel extensions. Responses containing a OSBundleMachOHeaders key may have included kernel addresses. These exposed addresses could help hackers bypass address space layout randomization protection. The exact same bug, which was found by Mark Dowd of Azimuth Security, Eric Monti of Square, and additional anonymous researchers, was fixed in iOS 6.0.1 earlier this month.

The second vulnerability fixed is part of WebKit. A time of check to time of use issue existed in the handling of JavaScript arrays. To exploit it a hacker would need a privileged network position and if successful it could cause an unexpected application termination or arbitrary code execution. Joost Pol and Daan Keuper of Certified Secure working with HP TippingPoint’s Zero Day Initiative are credited for the find and like the previous bug it was also fixed in iOS 6.0.1.

To check to see which version of of the OS your device is using , select ”Settings -> General -> About”. Most users won’t need to do anything as Apple TV will regularly check for software updates. Alternatively, you may manually check for software updates by selecting ”Settings -> General -> Update Software”.

In brief: Apple releases QuickTime 7.7.3 for Windows 7, Vista, XP SP2 or later

(LiveHacking.Com) – Apple has released an update to its popular QuickTime video player to address several vulnerabilites that existed when viewing a maliciously crafted file for a variery of different file types.

The full list of fixes is as follows:

  • Viewing a maliciously crafted PICT file may lead to an unexpected application termination or arbitrary code executin.  A buffer overflow existed in the handling of REGION
  • records in PICT files along with a memory corruption issue that existed in the handling of PICT files.These issue were addressed through improved bounds checking.
  • Visiting a maliciously crafted website may lead to an unexpected application termination or arbitrary code execution.  A use after free issue existed in the QuickTime plugin’s handling of ‘_qtactivex_’ parameters within a HTML object element. This issue was addressed through improved memory handling.
  • Viewing a maliciously crafted QuickTime TeXML file may lead to an unexpected application termination or arbitrary code execution. A buffer overflow existed in the handling of the
  • transform attribute in text3GTrack elements. This issue was addressed through improved bounds checking.
  • Viewing a maliciously crafted QuickTime TeXML file may lead to an unexpected application termination or arbitrary code execution.  Multiple buffer overflows existed in the handling of
  • style elements in QuickTime TeXML files. These issues were addressed through improved bounds checking.
  • Visiting a maliciously crafted website may lead to an unexpected application termination or arbitrary code execution.  A buffer overflow existed in the QuickTime plugin’s handling of MIME types. This issue was addressed through improved bounds checking.
  • Visiting a maliciously crafted website may lead to an unexpected application termination or arbitrary code execution. A use after free issue existed in the QuickTime ActiveX control’s handling of the Clear() method. This issue was addressed through improved memory management.
  • Viewing a maliciously crafted Targa file may lead to an unexpected application termination or arbitrary code execution.  A buffer overflow existed in the handling of Targa image files. This issue was addressed through improved bounds checking.
  • Viewing a maliciously crafted movie file may lead to an unexpected application termination or arbitrary code execution. A buffer overflow existed in the handling of ‘rnet’ boxes in MP4 files. This issue was addressed through improved bounds checking.

QuickTime 7.7.3 may be downloaded from the QuickTime site: http://www.apple.com/quicktime/download/. Also more information will also be posted to the Apple Security Updates
web site: http://support.apple.com/kb/HT1222.

Apple releases iOS 6.0.1 and Safari 6.0.2

(LiveHacking.Com) – Apple has released updates for it mobile device operating system iOS and its OS X web browser Safari. Both releases fix a number of security bugs.

The WebKit related fixes are both the same for iOS and Safari. The first and biggest bug fixed is the use after free issue in the handling of SVG images which was used by Pinkie Pie to win $60,000 at Google’s Pwnium 2 contest. The other WebKit error is with the handling of JavaScript arrays. Both errors can lead to an unexpected application termination or arbitrary code execution.

The iOS 6.0.1 also contains two additional fixes: an information disclosure issue in the handling of APIs related to kernel extensions and a problem where a person with physical access to an iOS device may be able to access Passbook passes without entering a passcode.

The kernel API problem meant that maliciously crafted or compromised iOS applications may be able to determine addresses in the kernel and so possibly bypass address space layout randomization protection.

iOS 6.0.1 is now available iPhone 3GS and later, iPod touch (4th generation) and later, iPad 2 and later. Safari 6.0.2 is now available OS X Lion v10.7.5, OS X Lion Server v10.7.5, OS X Mountain Lion v10.8.2.

Information will also be posted to the Apple Security Updates web site: http://support.apple.com/kb/HT1222.

In brief: Apple updates Java after Oracle’s October patches

(LiveHacking.Com) – Apple has once again updated the versions of Java running on its Mac OS X operating system soon after Oracle released its patches. This is in contrast to the fiasco which took place earlier this year which Apple took until April 2012 to push out a patch that had been available to Windows users since February.

This time Apple has been quick off the mark. According to the security advisory: Multiple vulnerabilities exist in Java 1.6.0_35, the most serious of which may allow an untrusted Java applet to execute arbitrary code outside the Java sandbox. Visiting a web page containing a maliciously crafted untrusted Java applet may lead to arbitrary code execution with the privileges of the current user. These issues are addressed by updating to Java version 1.6.0_37.

Additionally, for OS X 10.6 and OS X 10.7 this update removes the Apple-provided Java applet plug-in from all web browsers. It also removes the Java Preferences application, which is no longer required to configure applet settings. For Mac users who need a Java plugin (and you really must need it, other wise don’t bother) click on the region labeled “Missing plug-in” to download the latest version of the Java applet plug-in directly from Oracle.

The update is available for the last three versions of Mac OS X: Mac OS X Snow Leopard v10.6.8, OS X Lion v10.7 or later, and OS X Mountain Lion v10.8 or later.

Apple releases OS X Server v2.1.1 to fix problems in PostgreSQL & Jabber

(LiveHacking.Com) – Apple has released OS X Server v2.1.1 to address multiple vulnerabilities in PostgreSQL and fix an issue with the Jabber server’s handling of dialback result messages. Before Mac OS X 10.7, Apple sold a separate server edition of OS X, but now it is a separate set of server add-ons which can be bought directly from Apple’s online Mac App Store. OS X Server 2.1.1 is an update of that add-on component.

OS X Server adds the following capabilities to OS X: File sharing for Mac, PC, and iPad; Wiki Server; Profile Manager; Provide a Time Machine backup destination for Mac computers on your network; Standards-based SMTP, IMAP, and POP server; Calendar Server; Contacts Server; Messages Server; Encrypted VPN connections for Mac, iPad, iPhone, and PC; and Xsan

PostgreSQL
PostgreSQL has been updated to version 9.1.5 to address multiple vulnerabilities, the most serious of which may allow database users to read files from the file system with the privileges of the database server role account. Further information is available via the PostgreSQL web site at http://www.postgresql.org/docs/9.1/static/release-9-1-5.html.

Messages Server
An issue existed in the Jabber server’s handling of dialback result messages. An attacker may cause the Jabber server to disclose information intended for users of federated servers. This issue was addressed through improved handling of dialback result messages.

From a security standpoint, OS X Server v2.1.1 includes the security updates of OS X Mountain Lion v10.8.2.

What’s New in Version 2.1.1

  • Managing DHCP service from within the Server application
  • iOS 6 device management support in Profile Manager
  • Using the Server application to create a large number of users or groups
  • Authenticating with Calendar Server when using an Active Directory account
  • Renewing certificates for use with the Apple Push Notification Service
  • Configuring DNS entries with second level domains and aliases
  • Retaining network, DNS and PHP settings installing or upgrading OS X Server
  • Migrating from Lion Server and Snow Leopard Server

Apple TV updated with security fixes

(LiveHacking.Com) – Apple has released V5.1 of its Apple TV software to add some new features, like Photo Stream sharing, new screen savers and a way to switch iTunes accounts, as well as to address some security issues.

Apple TV 5.1, which is available for Apple TV 2nd generation devices and later, addresses 21 separate issues some of which could lead to arbitrary code execution.

The first issues resolves a problem with the handling of Sorenson encoded movie files where viewing a maliciously crafted movie file may lead to an
unexpected application termination or arbitrary code execution. The same issue was fixed by Apple in Quicktime 7.7.2 and iOS 6. Apple also fixed problems when viewing a maliciously crafted TIFF files, PNG files and JPEG files.

Multiple vulnerabilities existed in libxml and JavaScriptCore the most serious of which may lead to an unexpected application termination or arbitrary code execution. The result is that an attacker with a privileged network position may cause an unexpected application termination or arbitrary code execution. These issues were fix by using the latest versions of these libraries.

Apple also fixed a problem with how may broadcast MAC addresses of previously accessed networks per the DNAv4 protocol. This issue was addressed by disabling DNAv4 on unencrypted Wi-Fi networks.

To check to see which version of of the OS your device is using , select “Settings -> General -> About”. Most users won’t need to do anything as Apple TV will regularly check for software updates. Alternatively, you may manually check for software updates by selecting “Settings -> General -> Update Software”.

In brief: Apples releases updates for OS X and Safari

(LiveHacking.Com) – Having released iOS 6 with a large number of security fixes, Apple has now released an update to OS X and a new verison of Safari. For OS X, Mountain Lion has been updated to v10.8.2, Lion jumps to v10.7.5 and for OS X 10.6 Snow Leopard Apple has released Security Update 2012-004. Safari has recevied a minor update to 6.0.1 to address a range of security issues.

The updates to OS X upgrade or fix a number of low level OS X components including:

  • Apache has been updated to version 2.2.22 to address several vulnerabilities, the most serious of which may lead to a denial of service.
  • A reachable assertion issue existed in the handling of DNS records. This issue was addressed by updating to BIND 9.7.6-P1.
  • PHP is updated to version 5.3.15 to address multiple vulnerabilities, the most serious of which may lead to arbitrary code execution.

Other components updated include: CoreText, DirectoryService, ImageIO, Kernel, Mail and QuickTime.

Safari has also been updated including a large set of fixes for WebKit. OS X Mountain Lion v10.8.2  automatically updates Safari to Safari 6.0.1.

Plethora of security updates in iOS 6

(LiveHacking.Com) – Yesterday Apple launched the latest version of its mobile operating system for the iPhone, iPad and iPod Touch. iOS 6 brings new features like Facebook integration and is the default OS for the new iPhone 5 which starts shipping on Friday. The new OS also includes lots of important security fixes.

Included in the fixes is an update to WebKit, the open source HTML rendering engine which Apple created and is also used in Google Chrome. Apple updated iTunes recently with a very similar set of WebKit fixes as those found in iOS 6. Apple describes the WebKit vulnerabilities by saying that “Visiting a maliciously crafted website may lead to an unexpected application termination or arbitrary code execution.” Which it explains is due to “multiple memory corruption issues existed in WebKit. These issues are addressed through improved memory handling.”

Other WebKit fixes also include several cross-site scripting fixes and better URL handling. According to Apple the Unicode fonts embedded in Safari could can been used to create a URL which contains look-alike characters. These look-alike characters can be used by a malicious website to direct the user to a spoofed site that visually appears to be a legitimate domain.

Apple also spent some time fixing issues with passcode which can be set from within iOS to stop unwanted access to the device. This included a design flaw in the support for viewing photos that were taken while the screen was locked. Previously to determine which photos should be displayed the passcode lock checked the time at which the device was locked and compared it to the time that a photo was taken. However, by spoofing the current time an attacker could gain access to photos that were taken before the device was locked. To fix this, iOS now explicitly keeps track of the photos that were taken while the device was locked.

Other fixes are:

  • CFNetwork – An issue existed in CFNetwork’s handling of malformed URLs. CFNetwork may send requests to an incorrect hostname, resulting in the disclosure of sensitive information. This issue was addressed through improvements to URL handling.
  • CoreGraphics – Multiple vulnerabilities existed in FreeType, the most serious of which may lead to arbitrary code execution when processing a maliciously crafted font. These issues were addressed by updating FreeType to version 2.4.9. Further information is available via the FreeType site at http://www.freetype.org/
  • CoreMedia – An uninitialized memory access existed in the handling of Sorenson encoded movie files. This issue was addressed through improved memory initialization.
  • DHCP – Upon connecting to a Wi-Fi network, iOS may broadcast MAC addresses of previously accessed networks per the DNAv4 protocol. This issue was addressed by disabling DNAv4 on unencrypted Wi-Fi networks.
  • ImageIO – A buffer overflow existed in libtiff’s handling of ThunderScan encoded TIFF images. This issue was addressed by updating libtiff to version 3.9.5.
  • ImageIO – Multiple memory corruption issues existed in libpng’s handling of PNG images. These issues were addressed through improved validation of PNG images.
  • ImageIO – A double free issue existed in ImageIO’s handling of JPEG images. This issue was addressed through improved memory management.
  • ImageIO – An integer overflow issue existed in libTIFF’s handling of TIFF images. This issue was addressed through improved validation of TIFF images.
  • International Components for Unicode – A stack buffer overflow existed in the handling of ICU locale IDs. This issue was addressed through improved bounds checking.
  • IPSec – A buffer overflow existed in the handling of racoon configuration files. This issue was addressed through improved bounds checking.
  • Kernel – An invalid pointer dereference issue existed in the kernel’s handling of packet filter ioctls. This may allow an attacker to alter kernel memory. This issue was addressed through improved error handling.
  • Kernel – An uninitialized memory access issue existed in the Berkeley Packet Filter interpreter, which led to the disclosure of memory content. This issue was addressed through improved memory initialization.
  • libxml – Multiple vulnerabilities existed in libxml, the most serious of which may lead to an unexpected application termination or arbitrary code execution. These issues were addressed by applying the relevant upstream patches.
  • Mail – A logic issue existed in Mail’s handling of attachments. If a subsequent mail attachment used the same Content-ID as a previous one, the previous attachment would be displayed, even in the case where the 2 mails originated from different senders. This could facilitate some spoofing or phishing attacks. This issue was addressed through improved handling of attachments.
  • Mail – A logic issue existed in Mail’s use of Data Protection on email attachments. This issue was addressed by properly setting the Data Protection class for email attachments.
  • Mail – S/MIME signed messages displayed the untrusted ‘From’ address, instead of the name associated with the message signer’s identity. This issue was addressed by displaying the address associated with the message signer’s identity when it is available.
  • Messages – When a user had multiple email addresses associated with iMessage, replying to a message may have resulted in the reply being sent from a different email address. This may disclose another email address associated to the user’s account. This issue was addressed by always replying from the email address the original message was sent to.
  • Office – Viewer An information disclosure issue existed in the support for viewing Microsoft Office files. When viewing a document, the Office Viewer would write a temporary file containing data from the viewed document to the temporary directory of the invoking process. For an application that uses data protection or other encryption to protect the user’s files, this could lead to information disclosure. This issue was addressed by avoiding creation of temporary files when viewing Office documents.
  • OpenGL – Multiple memory corruption issues existed in the handling of GLSL compilation. These issues were addressed through improved validation of GLSL shaders.
  • Passcode Lock – A logic issue existed with the display of the “Slide to Power Off” slider on the lock screen. This issue was addressed through improved lock state management.
  • Passcode Lock – A logic issue existed in the termination of FaceTime calls from the lock screen. This issue was addressed through improved lock state management.
  • Passcode Lock – A design issue existed in the support for viewing photos that were taken at the lock screen. In order to determine which photos to permit access to, the passcode lock consulted the time at which the device was locked and compared it to the time that a photo was taken. By spoofing the current time, an attacker could gain access to photos that were taken before the device was locked. This issues was addressed by explicitly keeping track of the photos that were taken while the device was locked.
  • Passcode Lock – A logic issue existed in the Emergency Dialer screen, which permitted FaceTime calls via Voice Dialing on the locked device. This could also disclose the user’s contacts via contact suggestions. This issue was addressed by disabling Voice Dialing on the Emergency Dialer screen.
  • Passcode Lock Using the camera from the screen lock could in some cases interfere with automatic lock functionality, allowing a person with physical access to the device to bypass the Passcode Lock screen. This issue was addressed through improved lock state management.
  • Passcode Lock – A state management issue existed in the handling of the screen lock. This issue was addressed through improved lock state management.
  • Restrictions – After disabling Restrictions, iOS may not ask for the user’s password during a transaction. This issue was addressed by additional enforcement of purchase authorization.
  • Safari – Websites could use a Unicode character to create a lock icon in the page title. This icon was similar in appearance to the icon used to indicate a secure connection, and could have lead the user to believe a secure connection had been established. This issue was addressed by removing these characters from page titles.
  • Safari – Password input elements with the autocomplete attribute set to “off” were being autocompleted. This issue was addressed through improved handling of the autocomplete attribute.
  • System Logs – Sandboxed apps had read access to /var/log directory, which may allow them to obtain sensitive information contained in system logs. This issue was addressed by denying sandboxed apps access to the /var/log directory.
  • Telephony – Messages displayed the return address of an SMS message as the sender. Return addresses may be spoofed. This issue was addressed by always displaying the originating address instead of the return address.
  • Telephony – An off-by-one buffer overflow existed in the handling of SMS user data headers. This issue was addressed through improved bounds checking.
  • UIKit – Applications that use UIWebView may leave unencrypted files on the file system even when a passcode is enabled. This issue was addressed through improved use of data protection.
  • WebKit – A cross-origin issue existed in the handling of CSS property values. This issue was addressed through improved origin tracking.
  • WebKit – A cross-origin issue existed in the handling of iframes in popup windows. This issue was addressed through improved origin tracking.
  • WebKit – A cross-origin issue existed in the handling of iframes and fragment identifiers. This issue was addressed through improved origin tracking.
  • WebKit – The International Domain Name (IDN) support and Unicode fonts embedded in Safari could have been used to create a URL which contains look-alike characters. These could have been used in a malicious website to direct the user to a spoofed site that visually appears to be a legitimate domain. This issue was addressed by supplementing WebKit’s list of known look-alike characters. Look- alike characters are rendered in Punycode in the address bar.
  • WebKit – A canonicalization issue existed in the handling of URLs. This may have led to cross-site scripting on sites which use the location.href property. This issue was addressed through improved canonicalization of URLs.
  • WebKit – An HTTP header injection issue existed in the handling of WebSockets. This issue was addressed through improved WebSockets URI sanitization.
  • WebKit – A state management issue existed in the handling of session history. Navigations to a fragment on the current page may cause Safari to display incorrect information in the URL bar. This issue was addressed through improved session state tracking.
  • WebKit – An uninitialized memory access issue existed in the handling of SVG images. This issue was addressed through improved memory initialization.