What is the severity of CVE-2017-3887?

The severity of CVE-2017-3887 is considered high due to its potential to cause a denial of service.

How do I fix CVE-2017-3887?

To fix CVE-2017-3887, upgrade your Cisco Firepower Threat Defense software to the latest version as recommended by Cisco.

Who is affected by CVE-2017-3887?

CVE-2017-3887 affects users of Cisco Firepower Threat Defense software versions 6.0.1, 6.1.0, and 6.2.0.

What type of attack is possible with CVE-2017-3887?

CVE-2017-3887 allows an unauthenticated remote attacker to trigger a denial of service condition.

Is there a workaround for CVE-2017-3887?

There is no specific workaround for CVE-2017-3887; applying the recommended software updates is necessary.

Vulnerability/
CVE-2017-3887

medium

5.9

CWE

755

7/4/2017

3/10/2019

CVE-2017-3887

First published: Fri Apr 07 2017(Updated: )

A vulnerability in the detection engine that handles Secure Sockets Layer (SSL) packets for Cisco Firepower System Software could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition because the Snort process unexpectedly restarts. This vulnerability affects Cisco Firepower System Software prior to the first fixed release when it is configured with an SSL Decrypt-Resign policy. More Information: CSCvb62292. Known Affected Releases: 6.0.1 6.1.0 6.2.0. Known Fixed Releases: 6.2.0 6.1.0.2.

Credit: ykramarz@cisco.com

Affected Software	Affected Version	How to fix
Cisco Firepower Threat Defense	=6.0.1
Cisco Firepower Threat Defense	=6.1.0
Cisco Firepower Threat Defense	=6.2.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-3887?
The severity of CVE-2017-3887 is considered high due to its potential to cause a denial of service.
How do I fix CVE-2017-3887?
To fix CVE-2017-3887, upgrade your Cisco Firepower Threat Defense software to the latest version as recommended by Cisco.
Who is affected by CVE-2017-3887?
CVE-2017-3887 affects users of Cisco Firepower Threat Defense software versions 6.0.1, 6.1.0, and 6.2.0.
What type of attack is possible with CVE-2017-3887?
CVE-2017-3887 allows an unauthenticated remote attacker to trigger a denial of service condition.
Is there a workaround for CVE-2017-3887?
There is no specific workaround for CVE-2017-3887; applying the recommended software updates is necessary.

agent/references
agent/type
agent/last-modified-date
collector/nvd-index
agent/software-canonical-lookup-request
agent/author
agent/severity
agent/weakness
agent/softwarecombine
agent/description
agent/first-publish-date
agent/tags
agent/event
vendor/cisco
canonical/cisco firepower threat defense
version/cisco firepower threat defense/6.0.1
version/cisco firepower threat defense/6.1.0
version/cisco firepower threat defense/6.2.0

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-3887?
The severity of CVE-2017-3887 is considered high due to its potential to cause a denial of service.
How do I fix CVE-2017-3887?
To fix CVE-2017-3887, upgrade your Cisco Firepower Threat Defense software to the latest version as recommended by Cisco.
Who is affected by CVE-2017-3887?
CVE-2017-3887 affects users of Cisco Firepower Threat Defense software versions 6.0.1, 6.1.0, and 6.2.0.
What type of attack is possible with CVE-2017-3887?
CVE-2017-3887 allows an unauthenticated remote attacker to trigger a denial of service condition.
Is there a workaround for CVE-2017-3887?
There is no specific workaround for CVE-2017-3887; applying the recommended software updates is necessary.