Skip to content

Product

Cisco UTD SNORT IPS Engine Software vulnerabilities

29 published CVES affecting Cisco UTD SNORT IPS Engine Software, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
29
Critical
2
High
5
Medium
22
Low
0
Unscored
0
CISA KEV
0

Latest Cisco UTD SNORT IPS Engine Software CVEs

Newest publication first · page 1 of 2

  1. MediumCVSS 5.3 EPSS 0.53%

    Multiple Cisco products are affected by a vulnerability in the Snort 3 Detection Engine that could allow an unauthenticated, remote attacker to cause the detection engine to unexpectedly restart, resulting in a denial of service (DoS) condition. The vulnerability is due to a flaw...

  2. MediumCVSS 5.8 EPSS 0.56%

    Multiple Cisco products are affected by a vulnerability in the Snort 3 Detection Engine that could allow an unauthenticated, remote attacker to cause the Snort 3 Detection Engine to restart, resulting in an interruption of packet inspection. This vulnerability is due to incomplet...

  3. MediumCVSS 5.3 EPSS 0.60%

    Multiple Cisco products are affected by a vulnerability in the processing of DCE/RPC requests that could allow an unauthenticated, remote attacker to cause the Snort 3 Detection Engine to leak sensitive information or to restart, resulting in an interruption of packet inspection....

  4. MediumCVSS 5.8 EPSS 0.67%

    Multiple Cisco products are affected by a vulnerability in the processing of DCE/RPC requests that could allow an unauthenticated, remote attacker to cause the Snort 3 Detection Engine to leak sensitive information or to restart, resulting in an interruption of packet inspection....

  5. MediumCVSS 5.8 EPSS 1.1%

    Multiple Cisco products are affected by a vulnerability in the Snort detection engine that could allow an unauthenticated, remote attacker to bypass a configured file policy for HTTP. The vulnerability is due to incorrect handling of specific HTTP header parameters. An attacker c...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.