troubleshooting/tutorials/security
06/07/2004, 4:45pm, EDT
Monday, June 7th
Apple fixes URI exploits with security update
Apple today released Security Update 2004-06-07, which fixes the 'critical' URI security exploits noted over the past several weeks: "[It] delivers a number of security enhancements and is recommended for all Macintosh users. This update includes the following components: DiskImages, LaunchServices, Safari, and Terminal, Mac OS X will now present an approval alert when an application is to be run for the first time either by opening a document or clicking on a URL related to the application."
- LaunchServices (CVE-ID: CAN-2004-0538) Impact: LaunchServices automatically registers applications, which could be used to cause the system to run unexpected applications. Discussion: LaunchServices is a system component that discovers and opens applications. This system component has been modified to only open applications that have previously been explicitly run on the system. Attempts to run an application that has not previously been explicitly run will result in a user alert. Further information is available in this article.
Component: DiskImageMounter (No CVE ID--"this is only an additional preventative measure") Impact: The disk:// URI type mounts an anonymous remote file system using the http protocol. Discussion: The registration of the disk:// URI type is removed from the system as a preventative measure against attempts to automatically mount remote disk image file systems.
- Safari (CAN-2004-0539)
Impact: The "Show in Finder" button would open certain downloaded files, in some cases executing downloaded applications.
Discussion: The "Show in Finder" button will now reveal files in a Finder window and will no longer attempt to open them. This modification is only available for Mac OS X v10.3.4 "Panther" and Mac OS X Server v10.3.4 "Panther" systems as the issue does not apply to Mac OS X v10.2.8 "Jaguar" or Mac OS X Server v10.2.8 "Jaguar".
- Terminal (CVE-ID: Not applicable)
Impact: Attempts to use a telnet:// URI with an alternate port number fail. Discussion: A modification has been made to allow the specification of an alternate port number in a telnet:// URI. This restores functionality that was removed with the recent fix for CAN-2004-0485.
Filed under: troubleshooting
,
, 18
,
,
,
,
,

subscribe to comments
for this article
Just kidding...
G4/400 AGP
OS 10.3.4
I'm not seeing an APE requirement with Security Update 2004-06-07. ; )