What is the severity of CVE-2017-2536?

CVE-2017-2536 has been rated as a high severity vulnerability due to its potential for remote code execution.

How do I fix CVE-2017-2536?

To fix CVE-2017-2536, users should update their iOS devices, Safari browser, or tvOS to the latest version that addresses this vulnerability.

What products are affected by CVE-2017-2536?

CVE-2017-2536 affects iOS versions prior to 10.3.2, Safari versions prior to 10.1.1, and tvOS versions prior to 10.2.1.

What type of attacks can CVE-2017-2536 facilitate?

CVE-2017-2536 can facilitate remote code execution and may lead to denial of service through memory corruption.

Is there a workaround for CVE-2017-2536?

There is no official workaround for CVE-2017-2536; the recommended solution is to update to a patched version.

Vulnerability/
CVE-2017-2536

high

8.8

CWE

119

22/5/2017

5/8/2024

CVE-2017-2536: Buffer Overflow

First published: Mon May 22 2017(Updated: )

An issue was discovered in certain Apple products. iOS before 10.3.2 is affected. Safari before 10.1.1 is affected. tvOS before 10.2.1 is affected. The issue involves the "WebKit" component. It allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted web site.

Credit: product-security@apple.com

Affected Software	Affected Version	How to fix
Apple Safari	<=10.1
Apple iPhone OS	<=10.3.1
tvOS	<=10.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-2536?
CVE-2017-2536 has been rated as a high severity vulnerability due to its potential for remote code execution.
How do I fix CVE-2017-2536?
To fix CVE-2017-2536, users should update their iOS devices, Safari browser, or tvOS to the latest version that addresses this vulnerability.
What products are affected by CVE-2017-2536?
CVE-2017-2536 affects iOS versions prior to 10.3.2, Safari versions prior to 10.1.1, and tvOS versions prior to 10.2.1.
What type of attacks can CVE-2017-2536 facilitate?
CVE-2017-2536 can facilitate remote code execution and may lead to denial of service through memory corruption.
Is there a workaround for CVE-2017-2536?
There is no official workaround for CVE-2017-2536; the recommended solution is to update to a patched version.

agent/type
agent/softwarecombine
agent/references
agent/author
agent/severity
agent/weakness
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/apple
canonical/apple safari
version/apple safari/10.1
canonical/apple iphone os
version/apple iphone os/10.3.1
canonical/tvos
version/tvos/10.2

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.

Frequently Asked Questions

What is the severity of CVE-2017-2536?
CVE-2017-2536 has been rated as a high severity vulnerability due to its potential for remote code execution.
How do I fix CVE-2017-2536?
To fix CVE-2017-2536, users should update their iOS devices, Safari browser, or tvOS to the latest version that addresses this vulnerability.
What products are affected by CVE-2017-2536?
CVE-2017-2536 affects iOS versions prior to 10.3.2, Safari versions prior to 10.1.1, and tvOS versions prior to 10.2.1.
What type of attacks can CVE-2017-2536 facilitate?
CVE-2017-2536 can facilitate remote code execution and may lead to denial of service through memory corruption.
Is there a workaround for CVE-2017-2536?
There is no official workaround for CVE-2017-2536; the recommended solution is to update to a patched version.