Cisco Cyber Vision vulnerability

What happened

Multiple Cisco products are affected by a vulnerability in the Snort 3 HTTP Decoder that could allow an unauthenticated, remote attacker to cause the disclosure of possible sensitive data or cause the Snort 3 Detection Engine to crash. This vulnerability is due to an error in the logic of buffer handling when the MIME fields of the HTTP header are parsed. This can result in a buffer under-read. An attacker could exploit this vulnerability by sending crafted HTTP packets through an established connection that is parsed by Snort 3. A successful exploit could allow the attacker to induce one of two possible outcomes: the unexpected restarting of the Snort 3 Detection Engine, which could cause a denial of service (DoS) condition, or information disclosure of sensitive information in the Snort 3 data stream. Due to the under-read condition, it is possible that sensitive information that is not valid connection data could be returned.

Affected versions

Cisco Cyber Vision: 3.0.0; 3.0.2; 3.0.3; 3.0.1; 3.1.0; 3.0.4; 3.1.1; 3.1.2; 3.2.0; 3.0.5; 3.2.1; 3.0.6; 3.2.2; 3.2.3; 3.2.4; 4.0.0; 4.0.1; 4.0.2; 4.0.3; 4.1.0; 4.1.1; 4.1.2; 4.1.3; 4.1.4; 4.2.0; 4.2.1; 4.1.5; 4.2.2; 4.2.X; 4.2.3; 4.2.4; 4.2.6; 4.1.6; 4.3.0; 4.3.1; 4.3.2; 4.3.3; 4.4.0; 4.4.1; 4.4.2; 4.4.3; 4.1.7; 5.0.0; 5.0.1; 5.0.2; 5.1.0; 5.1.1; 5.1.2; 5.1.3; 5.2.0; 5.2.1; 7.4.1; 7.4.1.1; 7.6.0; 7.4.2; 7.4.2.1; 7.7.0; 7.4.2.2; 7.6.1; 7.4.2.3; 7.4.2.4; 3.17.1S; 16.12.3; 16.12.4; 17.3.1a; 16.6.6; 16.12.2; 3.17.0S; 16.6.5; 17.2.1r; 17.1.1; 16.6.7a; 16.6.1; 16.12.1a; 17.3.2; 17.4.1a; 16.12.5; 17.5.1; 16.6.9; 17.3.3; 17.5.1a; 17.3.4; 17.3.4a; 17.4.2; 17.4.1b; 17.6.1a; 16.6.10; 17.7.1a; 16.12.6; 17.6.2; 17.8.1a; 16.12.7; 17.3.5; 17.6.3; 17.6.3a; 17.7.2; 17.9.1a; 17.6.4; 17.3.6; 16.12.8; 17.3.7; 17.9.2a; 17.6.5; 17.11.1a; 17.12.1a; 17.6.6; 17.3.8; 17.3.8a; 17.6.6a; 17.12.2; 17.12.3; 17.6.7; 17.12.3a; 17.12.4; 17.6.8; 17.6.8a; 17.12.4a; 17.15.2c; 17.12.4b; 17.15.2a; 17.12.5; 17.15.3a; 17.15.3; 17.12.5b; 17.15.4 Fixed: See vendor advisory.

Why it matters

Review the vendor advisory and exposure of the affected product to determine operational impact.

Detection & mitigation

• Apply vendor-provided updates or mitigations.
• Review affected product exposure and access logs.