medium
6.8
CWE
119
Advisory Published
Updated

CVE-2013-5126: Buffer Overflow

First published: Thu Sep 19 2013(Updated: )

WebKit, as used in Apple iOS before 7, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted web site, a different vulnerability than other WebKit CVEs listed in APPLE-SA-2013-09-18-2.

Credit: product-security@apple.com

Affected SoftwareAffected VersionHow to fix
iPhone OS<=6.1.4
iPhone OS=1.0.0
iPhone OS=1.0.1
iPhone OS=1.0.2
iPhone OS=1.1.0
iPhone OS=1.1.1
iPhone OS=1.1.2
iPhone OS=1.1.3
iPhone OS=1.1.4
iPhone OS=1.1.5
iPhone OS=2.0
iPhone OS=2.0.0
iPhone OS=2.0.1
iPhone OS=2.0.2
iPhone OS=2.1
iPhone OS=2.1.1
iPhone OS=2.2
iPhone OS=2.2.1
iPhone OS=3.0
iPhone OS=3.0.1
iPhone OS=3.1
iPhone OS=3.1.2
iPhone OS=3.1.3
iPhone OS=3.2
iPhone OS=3.2.1
iPhone OS=3.2.2
iPhone OS=4.0
iPhone OS=4.0.1
iPhone OS=4.0.2
iPhone OS=4.1
iPhone OS=4.2.1
iPhone OS=4.2.5
iPhone OS=4.2.8
iPhone OS=4.3.0
iPhone OS=4.3.1
iPhone OS=4.3.2
iPhone OS=4.3.3
iPhone OS=4.3.5
iPhone OS=5.0
iPhone OS=5.0.1
iPhone OS=5.1
iPhone OS=5.1.1
iPhone OS=6.0
iPhone OS=6.0.1
iPhone OS=6.0.2
iPhone OS=6.1
iPhone OS=6.1.2
iPhone OS=6.1.3

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2013-5126?

    CVE-2013-5126 is classified as a critical vulnerability allowing remote code execution and denial of service.

  • How do I fix CVE-2013-5126?

    To fix CVE-2013-5126, update your Apple iOS to version 7.0 or later.

  • What devices are affected by CVE-2013-5126?

    CVE-2013-5126 affects Apple iOS versions prior to 7.0, including iPhone OS versions 1.0 through 6.1.3.

  • What are the potential impacts of CVE-2013-5126 if exploited?

    Exploitation of CVE-2013-5126 can lead to arbitrary code execution, memory corruption, and application crashes.

  • Is there a workaround for CVE-2013-5126 if I can't update my device?

    There is no known workaround for CVE-2013-5126, making it crucial to update to a safe version as soon as possible.

Company

Resources

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203