What is the severity of CVE-2016-6594?

CVE-2016-6594 is considered a high severity vulnerability due to its ability to allow remote attackers to bypass security measures.

How do I fix CVE-2016-6594?

To mitigate CVE-2016-6594, it is recommended to update to the latest versions of affected products as provided by Blue Coat.

What systems are affected by CVE-2016-6594?

CVE-2016-6594 affects Blue Coat Advanced Secure Gateway 6.6, CacheFlow 3.4, and ProxySG versions 6.5 and 6.6.

What are the consequences of CVE-2016-6594 exploitation?

Exploitation of CVE-2016-6594 can lead to unauthorized access, bypassing of user authentication, and evasion of payload scanning.

Is there a workaround for CVE-2016-6594?

Currently, applying the latest patches is the recommended approach to address CVE-2016-6594, but consult your security team for any temporary workarounds.

Vulnerability/
CVE-2016-6594

high

7.5

CWE

254

8/6/2017

6/8/2024

CVE-2016-6594

First published: Thu Jun 08 2017(Updated: )

Blue Coat Advanced Secure Gateway 6.6, CacheFlow 3.4, ProxySG 6.5 and 6.6 allows remote attackers to bypass blocked requests, user authentication, and payload scanning.

Credit: secure@symantec.com

Affected Software	Affected Version	How to fix
Broadcom Symantec Advanced Secure Gateway	=6.6
Bluecoat CacheFlow	=3.4
Bluecoat ProxySG	=6.5
Bluecoat ProxySG	=6.6

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-6594?
CVE-2016-6594 is considered a high severity vulnerability due to its ability to allow remote attackers to bypass security measures.
How do I fix CVE-2016-6594?
To mitigate CVE-2016-6594, it is recommended to update to the latest versions of affected products as provided by Blue Coat.
What systems are affected by CVE-2016-6594?
CVE-2016-6594 affects Blue Coat Advanced Secure Gateway 6.6, CacheFlow 3.4, and ProxySG versions 6.5 and 6.6.
What are the consequences of CVE-2016-6594 exploitation?
Exploitation of CVE-2016-6594 can lead to unauthorized access, bypassing of user authentication, and evasion of payload scanning.
Is there a workaround for CVE-2016-6594?
Currently, applying the latest patches is the recommended approach to address CVE-2016-6594, but consult your security team for any temporary workarounds.

agent/references
agent/type
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/severity
agent/weakness
agent/author
agent/event
agent/description
agent/first-publish-date
agent/source
agent/tags
agent/softwarecombine
collector/nvd-index
agent/software-canonical-lookup-request
vendor/bluecoat
canonical/broadcom symantec advanced secure gateway
version/broadcom symantec advanced secure gateway/6.6
canonical/bluecoat cacheflow
version/bluecoat cacheflow/3.4
canonical/bluecoat proxysg
version/bluecoat proxysg/6.5
version/bluecoat proxysg/6.6

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-2016-6594?
CVE-2016-6594 is considered a high severity vulnerability due to its ability to allow remote attackers to bypass security measures.
How do I fix CVE-2016-6594?
To mitigate CVE-2016-6594, it is recommended to update to the latest versions of affected products as provided by Blue Coat.
What systems are affected by CVE-2016-6594?
CVE-2016-6594 affects Blue Coat Advanced Secure Gateway 6.6, CacheFlow 3.4, and ProxySG versions 6.5 and 6.6.
What are the consequences of CVE-2016-6594 exploitation?
Exploitation of CVE-2016-6594 can lead to unauthorized access, bypassing of user authentication, and evasion of payload scanning.
Is there a workaround for CVE-2016-6594?
Currently, applying the latest patches is the recommended approach to address CVE-2016-6594, but consult your security team for any temporary workarounds.