Cisco Bug: CSCzv09244 - Invalid identity based on SOCKS protocol if SOCKS is disabled
Feb 07, 2017
- Cisco Content Security Management Appliance
Known Affected Releases
8.0.0-387 8.1.0-000 8.1.1-000 8.1.2-000 8.2.0-000
Symptom: AsyncOS may allow creation of invalid Identities. The Identity will be published even though SOCKS is disabled, and the identity is therefore invalid. Conditions: This can occur when the following are true: - SOCKS Proxy is disabled on the Web Security appliance - SOCKS Proxy is enabled on the Security Management appliance - You create a custom identity in a Configuration Master that defines members based only on the SOCKS protocol.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases