Apple Safari Multiple Vulnerabilities

Multiple vulnerabilities have been identified in Apple Safari, which could be exploited by attackers to disclose sensitive information, bypass security restrictions, cause a denial of service or compromise an affected system.

1. Due to an error in CFNetwork when identifying the file type of certain local image files could be exploited by attackers to execute malicious JavaScript in the local context by tricking a user into downloading and opening a malicious image.

2. Due to CFNetwork creating temporary files insecurely when downloading files, which could allow malicious users to access another user's files as they are downloaded.

3. Due to memory corruption and integer overflow errors in CoreGraphics when processing malformed data, TrueType fonts, or PDF files, which could be exploited to crash an affected browser or execute arbitrary code.

4. Due to an uninitialized pointer in ImageIO when handling PNG images, which could be exploited to execute arbitrary code.

5. Due to implementation error in ICU when handling certain character encodings, which could be exploited to bypass cross-site scripting filters.

6. Due to errors in libxml

7. Due to an error when handling Extended Validation (EV) certificates, which could be exploited to bypass the revocation checking warning.

8. Due to an implementation error in the Private Browsing feature, which may cause cookies to remain on disk after Private Browsing ends, potentially leading to the disclosure of sensitive information.

9. Due to the "Reset" button for "Reset saved names and passwords" in the "Reset Safari..." menu option taking up to 30 seconds to clear the passwords, which could allow a user with access to the system in that time window to access the stored credentials.

10. Due to an error in the open-help-anchor URL handler, which may allow a maliciously crafted website to open local help files, leading to the disclosure of sensitive information or arbitrary code execution.

11. Due to the Safari Windows Installer causing Safari to run with elevated privileges for its initial launch.

12. Due to input validation, design, type conversion, memory corruption, uninitialized pointer, use-after-free, uninitialized memory access errors in WebKit, which could be exploited to gain knowledge of sensitive information, read arbitrary files, bypass security restrictions and the same-origin policy, spoof browser UI elements, conduct cross site scripting and forgery attacks, or compromise a vulnerable system.