Vulnerability Note VU#480428
Juniper ScreenOS is vulnerable to a denial of service from malformed SSL packets
Original Release date: 16 May 2014 | Last revised: 16 May 2014
Juniper ScreenOS 6.3, and possibly earlier versions, is vulnerable to a denial of service from malformed SSL packets.
Juniper ScreenOS 6.3, and possibly earlier versions, is vulnerable to a denial of service from malformed SSL packets. Additional details may be found in Juniper security advisory JSA10624.
A remote unauthenticated attacker may be able to produce an extended denial of service against a ScreenOS firewall by repeatedly sending malformed SSL/TLS packets to the device.
Apply an Update
Juniper security advisory JSA10624 recommends the following solution.
Juniper Networks has released patches to resolve this issue (see the links below):
Note: The fix will also be a part of ScreenOS 6.3.0r17 that is currently under developement.
ISG-2000 with IDP:
ISG-1000 with IDP:
KB16765 – "In which releases are vulnerabilities fixed?" describes which release vulnerabilities are fixed as per our End of Engineering and End of Life support policies.
If you are unable to patch, please consider the following workaround.
Juniper security advisory JSA10624 recommends the following workaround.
Due to the likelihood of the specific packet occurring during normal activity, Juniper recommends disabling WebUI (SSL) and WebAuth (SSL) until a software fix is available. This includes disabling WebUI (SSL) and WebAuth (SSL) even on internal and protected networks.
This issue is completely mitigated when WebUI (SSL) and WebAuth (SSL) is disabled.
Disabling SSL WebUI (HTTPS) is part of our best practices, as mentioned in KB29016.
Vendor Information (Learn More)
VendorStatusDate NotifiedDate UpdatedJuniper Networks, Inc.Affected-16 May 2014If you are a vendor and your product is affected, let
CVSS Metrics (Learn More)
Thanks to David Klein of DHK Enterprises for reporting this vulnerability.
This document was written by Jared Allar.
16 Apr 2014
Date First Published:
16 May 2014
Date Last Updated:
16 May 2014
FeedbackIf you have feedback, comments, or additional information about this vulnerability, please send us email.