CVE-2009-2062: Medium severity Safari vulnerability

Published Jun 15, 2009
·
Updated

Apple Safari before 3.2.2 processes a 3xx HTTP CONNECT response before a successful SSL handshake, which allows man-in-the-middle attackers to execute arbitrary web script, in an https site's context, by modifying this CONNECT response to specify a 302 redirect to an arbitrary https web site.

Affected Software

66 affected components
Safari=3.0.4b
Safari=1.3.0
Safari=1.0.3-85.8
Safari=2.0.3-417.9.3
Safari=1.3.2
Safari=2
Safari=1.1.1
Safari=3.0.4
Safari=1.2.2
Safari=3.0.1-beta
Safari=2.0.1
Safari=2.0.3
Safari=1.0.3
Safari=2.0.2
Safari=1.0.2
Safari=3.0.0
Safari=3.0.1
Safari=3.0.2
Safari=1.0
Safari=2.0.4_419.3
Safari=3.0.3b
Safari=3.1.1
Safari=1.3
Safari=3.1
Safari=2.0.3-417.9
Safari=1.2.5
Safari=2.0.3-417.9.2
Safari=3.2
Safari=3.0.3
Safari=2.0
Safari=1.2.4
Safari=1.0.1
Safari<=3.2.1
Safari=2.0.3-417.8
Safari=3.1.2
Safari=1.2.1
Safari=3.1.0b
Safari=1.0.3-85.8.1
Safari=3.1.0
Safari=1.0-beta
Safari=0.8
Safari=2.0.4
Safari=1.0-beta2
Safari=1.1
Safari=1.3.2-312.5
Safari=3.0.0b
Safari=1.3.1
Safari=2.0.0
Safari=3.2.0
Safari=1.1.0
Safari=3.0.2b
Safari=1.2
Safari=1.2.0
Safari=3.0.1b
Safari=2.0_pre
Safari=1.0.0b1
Safari=3.0
Safari=3.0.4_beta
Safari=3.0.3-522.15.5
Safari=2.0.3_417.9.3
Safari=1.0.0
Safari=1.2.3
Safari=1.3.2-312.6
Safari=3
Safari=1.0.0b2
Safari=0.9

Event History

Jun 15, 2009
CVE Published
via MITRE·07:00 PM
Data Sourced
via MITRE·07:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2009-2062?

CVE-2009-2062 is classified as a high-severity vulnerability due to its potential for man-in-the-middle attacks.

2

How do I fix CVE-2009-2062?

To fix CVE-2009-2062, it's recommended to upgrade to Apple Safari version 3.2.2 or later.

3

Which versions of Apple Safari are affected by CVE-2009-2062?

CVE-2009-2062 affects several versions of Apple Safari prior to 3.2.2.

4

What type of attack can be executed due to CVE-2009-2062?

CVE-2009-2062 allows man-in-the-middle attackers to execute arbitrary web scripts in an https site's context.

5

How was CVE-2009-2062 disclosed?

CVE-2009-2062 was disclosed through security research and documented in various security databases.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203