CVE-2017-2450: Input Validation

Published Mar 27, 2017
·
Updated

CoreText. An out-of-bounds read was addressed through improved input validation.

Other sources

An issue was discovered in certain Apple products. iOS before 10.3 is affected. macOS before 10.12.4 is affected. tvOS before 10.2 is affected. watchOS before 3.2 is affected. The issue involves the "CoreText" component. It allows remote attackers to obtain sensitive information or cause a denial of service (out-of-bounds read and application crash) via a crafted font file.

Credit

John Villamil, Doyensec

Affected Software

5 affected componentsFixes available
Apple iOS<10.3
10.3
Apple iPhone OS<=10.2.1
Apple iOS and macOS<=10.12.3
Apple tvOS<=10.1.1
Apple WatchOS<=3.1.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Apple iOS and iPadOS to a version that resolves this vulnerability.

    Fixed in 10.3

Event History

Apr 2, 2017
CVE Published
via MITRE·01:36 AM
Data Sourced
via MITRE·01:36 AM
Description
Data Sourced
via NVD·01:59 AM
DescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

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-2017-2450?

CVE-2017-2450 has a high severity rating due to the potential for exploitation through out-of-bounds read vulnerabilities.

2

How do I fix CVE-2017-2450?

To fix CVE-2017-2450, update your affected Apple devices to at least iOS 10.3, macOS 10.12.4, tvOS 10.2, or watchOS 3.2.

3

Which Apple products are affected by CVE-2017-2450?

CVE-2017-2450 affects iOS devices before version 10.3, macOS before version 10.12.4, tvOS before version 10.2, and watchOS before version 3.2.

4

What vulnerability type is CVE-2017-2450 classified under?

CVE-2017-2450 is classified as an out-of-bounds read vulnerability within the CoreText component.

5

Is there a workaround for CVE-2017-2450?

No specific workaround is available for CVE-2017-2450; updating to the latest software version is recommended.

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