medium
4.3
CWE
264
Advisory Published
Updated

CVE-2013-5149

First published: Thu Sep 19 2013(Updated: )

The Push Notifications subsystem in Apple iOS before 7 provides the push-notification token to an app without user approval, which allows attackers to obtain sensitive information via an app that employs a crafted push-notification registration process.

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-5149?

    CVE-2013-5149 is classified as a moderate severity vulnerability that allows unauthorized access to push notifications.

  • How do I fix CVE-2013-5149?

    To fix CVE-2013-5149, update your Apple iOS device to version 7 or later.

  • Which versions of Apple iOS are affected by CVE-2013-5149?

    CVE-2013-5149 affects all versions of Apple iOS prior to 7, including versions 1.0 through 6.1.4.

  • What type of information can be compromised due to CVE-2013-5149?

    CVE-2013-5149 can potentially expose sensitive user information through malicious push notification registrations.

  • Is there a workaround for CVE-2013-5149?

    There is no known workaround for CVE-2013-5149; the only solution is to update to iOS 7 or higher.

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