CVE-2013-1001: Critical severity Apple iPhone OS vulnerability

Published May 19, 2013
·
Updated

WebKit, as used in Apple iTunes before 11.0.3, allows man-in-the-middle attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via vectors related to iTunes Store browsing, a different vulnerability than other WebKit CVEs listed in APPLE-SA-2013-05-16-1.

Affected Software

130 affected components
Apple iPhone OS<=6.1.4
Apple iPhone OS=1.0.0
Apple iPhone OS=1.0.1
Apple iPhone OS=1.0.2
Apple iPhone OS=1.1.0
Apple iPhone OS=1.1.1
Apple iPhone OS=1.1.2
Apple iPhone OS=1.1.3
Apple iPhone OS=1.1.4
Apple iPhone OS=1.1.5
Apple iPhone OS=2.0
Apple iPhone OS=2.0.0
Apple iPhone OS=2.0.1
Apple iPhone OS=2.0.2
Apple iPhone OS=2.1
Apple iPhone OS=2.1.1
Apple iPhone OS=2.2
Apple iPhone OS=2.2.1
Apple iPhone OS=3.0
Apple iPhone OS=3.0.1
Apple iPhone OS=3.1
Apple iPhone OS=3.1.2
Apple iPhone OS=3.1.3
Apple iPhone OS=3.2
Apple iPhone OS=3.2.1
Apple iPhone OS=3.2.2
Apple iPhone OS=4.0
Apple iPhone OS=4.0.1
Apple iPhone OS=4.0.2
Apple iPhone OS=4.1
Apple iPhone OS=4.2.1
Apple iPhone OS=4.2.5
Apple iPhone OS=4.2.8
Apple iPhone OS=4.3.0
Apple iPhone OS=4.3.1
Apple iPhone OS=4.3.2
Apple iPhone OS=4.3.3
Apple iPhone OS=4.3.5
Apple iPhone OS=5.0
Apple iPhone OS=5.0.1
Apple iPhone OS=5.1
Apple iPhone OS=5.1.1
Apple iPhone OS=6.0
Apple iPhone OS=6.0.1
Apple iPhone OS=6.0.2
Apple iPhone OS=6.1
Apple iPhone OS=6.1.2
Apple iPhone OS=6.1.3
Apple iTunes<=11.0.2
Apple iTunes=4.0.0
Apple iTunes=4.0.1
Apple iTunes=4.1.0
Apple iTunes=4.2.0
Apple iTunes=4.5
Apple iTunes=4.5.0
Apple iTunes=4.6
Apple iTunes=4.6.0
Apple iTunes=4.7
Apple iTunes=4.7.0
Apple iTunes=4.7.1
Apple iTunes=4.7.2
Apple iTunes=4.8.0
Apple iTunes=4.9.0
Apple iTunes=5.0
Apple iTunes=5.0.0
Apple iTunes=5.0.1
Apple iTunes=6.0.0
Apple iTunes=6.0.1
Apple iTunes=6.0.2
Apple iTunes=6.0.3
Apple iTunes=6.0.4
Apple iTunes=6.0.5
Apple iTunes=7.0.0
Apple iTunes=7.0.1
Apple iTunes=7.0.2
Apple iTunes=7.1.0
Apple iTunes=7.1.1
Apple iTunes=7.2.0
Apple iTunes=7.3.0
Apple iTunes=7.3.1
Apple iTunes=7.3.2
Apple iTunes=7.4
Apple iTunes=7.4.0
Apple iTunes=7.4.1
Apple iTunes=7.4.2
Apple iTunes=7.4.3
Apple iTunes=7.5
Apple iTunes=7.5.0
Apple iTunes=7.6
Apple iTunes=7.6.0
Apple iTunes=7.6.1
Apple iTunes=7.6.2
Apple iTunes=7.7
Apple iTunes=7.7.0
Apple iTunes=7.7.1
Apple iTunes=8.0.0
Apple iTunes=8.0.1
Apple iTunes=9.0.0
Apple iTunes=9.0.1
Apple iTunes=9.0.2
Apple iTunes=9.0.3
Apple iTunes=9.1
Apple iTunes=9.1.1
Apple iTunes=9.2
Apple iTunes=9.2.1
Apple iTunes=10.0
Apple iTunes=10.0.1
Apple iTunes=10.1
Apple iTunes=10.1.1
Apple iTunes=10.1.1.4
Apple iTunes=10.1.2
Apple iTunes=10.2
Apple iTunes=10.2.2.12
Apple iTunes=10.3
Apple iTunes=10.3.1
Apple iTunes=10.4
Apple iTunes=10.4.0.80
Apple iTunes=10.4.1
Apple iTunes=10.4.1.10
Apple iTunes=10.5
Apple iTunes=10.5.1
Apple iTunes=10.5.1.42
Apple iTunes=10.5.2
Apple iTunes=10.5.3
Apple iTunes=10.6
Apple iTunes=10.6.1
Apple iTunes=10.6.3
Microsoft Windows 7
Microsoft Windows Vista
Microsoft Windows XP

Event History

May 19, 2013
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2013-1001?

CVE-2013-1001 has a severity rating that indicates high risk due to the potential for remote code execution or denial of service.

2

How do I fix CVE-2013-1001?

To fix CVE-2013-1001, you should update your Apple iTunes to at least version 11.0.3 or the latest available version.

3

What systems are affected by CVE-2013-1001?

CVE-2013-1001 affects various versions of Apple iTunes and Apple iPhone OS, specifically versions before 11.0.3.

4

What type of attack does CVE-2013-1001 enable?

CVE-2013-1001 allows man-in-the-middle attackers to exploit vulnerabilities during iTunes Store browsing.

5

Can CVE-2013-1001 cause application crashes?

Yes, CVE-2013-1001 can lead to memory corruption, resulting in application crashes.

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