CVE-2021-40116

highPriorität · verfolgen · 30EPSS 0.014 · 72. PerzentilDEEURUUS
grimoire priorityP2 · Scheduled
Exploitable?
—
no known exploitation
Likely / severe?
1.39% (72nd) EPSS
CVSS 7.1 · high
Is it mine?
23 products
Prüfe deine Angriffsfläche
Who says so?
6 sources
cnnvd · enisa_euvd · fstec_bdu · cert_bund

EPSS · bewertet 2026-10-26

Multiple Cisco products are affected by a vulnerability in Snort rules that could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device.The vulnerability is due to improper handling of the Block with Reset or Interactive Block with Reset actions if a rule is configured without proper constraints. An attacker could exploit this vulnerability by sending a crafted IP packet to the affected device. A successful exploit could allow the attacker to cause through traffic to be dropped. Note: Only products with Snort3 configured and either a rule with Block with Reset or Interactive Block with Reset actions configured are vulnerable. Products configured with Snort2 are not vulnerable.

01

Behebungen

Hersteller-Fix, Mitigation oder Workaround, wie von den Quellen veröffentlicht.

Ein Hersteller-Fix ist verfügbar.

  • BehobenCisco Secure Firewall Threat Defense (FTD) Software 7.0.0 when installed on Cisco 3000 Series Industrial Security Appliances (ISA)cisco_csaf

    Cisco has released software updates that address this vulnerability.

    https://software.cisco.com
  • BehobenCisco Secure Firewall Threat Defense (FTD) Software 7.0.0 when installed on Cisco Firepower 1000 Seriescisco_csaf

    Cisco has released software updates that address this vulnerability.

    https://software.cisco.com
  • BehobenCisco Secure Firewall Threat Defense (FTD) Software 7.0.0 when installed on Cisco Firepower 2100 Seriescisco_csaf

    Cisco has released software updates that address this vulnerability.

    https://software.cisco.com
  • BehobenCisco Secure Firewall Threat Defense (FTD) Software 7.0.0 when installed on Cisco Firepower 4100 Seriescisco_csaf

    Cisco has released software updates that address this vulnerability.

    https://software.cisco.com
  • BehobenCisco Secure Firewall Threat Defense (FTD) Software 7.0.0 when installed on Cisco Firepower 9000 Seriescisco_csaf

    Cisco has released software updates that address this vulnerability.

    https://software.cisco.com
  • BehobenCisco Secure Firewall Threat Defense (FTD) Software 7.0.0 when installed on Cisco Secure Firewall Threat Defense Virtualcisco_csaf

    Cisco has released software updates that address this vulnerability.

    https://software.cisco.com
  • BehobenCisco Secure Firewall Threat Defense (FTD) Software 7.0.0.1 when installed on Cisco 3000 Series Industrial Security Appliances (ISA)cisco_csaf

    Cisco has released software updates that address this vulnerability.

    https://software.cisco.com
  • BehobenCisco Secure Firewall Threat Defense (FTD) Software 7.0.0.1 when installed on Cisco Firepower 1000 Seriescisco_csaf

    Cisco has released software updates that address this vulnerability.

    https://software.cisco.com
  • BehobenCisco Secure Firewall Threat Defense (FTD) Software 7.0.0.1 when installed on Cisco Firepower 2100 Seriescisco_csaf

    Cisco has released software updates that address this vulnerability.

    https://software.cisco.com
  • BehobenCisco Secure Firewall Threat Defense (FTD) Software 7.0.0.1 when installed on Cisco Firepower 4100 Seriescisco_csaf

    Cisco has released software updates that address this vulnerability.

    https://software.cisco.com
  • BehobenCisco Secure Firewall Threat Defense (FTD) Software 7.0.0.1 when installed on Cisco Firepower 9000 Seriescisco_csaf

    Cisco has released software updates that address this vulnerability.

    https://software.cisco.com
  • BehobenCisco Secure Firewall Threat Defense (FTD) Software 7.0.0.1 when installed on Cisco Secure Firewall Threat Defense Virtualcisco_csaf

    Cisco has released software updates that address this vulnerability.

    https://software.cisco.com
  • WorkaroundCisco Secure Firewall Threat Defense (FTD) Software 7.0.0 when installed on Cisco 3000 Series Industrial Security Appliances (ISA)cisco_csaf

    There are workarounds that addresses this vulnerability. While these workarounds have been deployed and were proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment. Note: There are three workarounds for this issue. Implementing any of the workarounds is sufficient. Two or more workarounds do not need to be implemented. Workaround 1 The first workaround is to change the Snort inspection engine from Snort3 to Snort2. See the configuration guide or support team for potential impacts. The steps to revert to Snort2 are as follows: Go to the FMC web interface Go to the Devices page and then the Device Management tab. Select the FTD device to check. Choose Edit. Go to the Device tab and look in the Inspection Engine area. Choose the Revert to Snort2 option. Workaround 2 The second workaround is to change all rule actions from Block with Reset or Interactive Block with Reset to another action. See the configuration guide or support team for potential impacts. The steps are as follows: Go to the FMC web interface Go to the Policies page and then the Access Control tab. Select the Policy to review and choose Edit. Find a rule that has a Reset action and choose Edit. Change the action from Block with Reset or Interactive Block with Reset to another action. Workaround 3 The third workaround involves narrowing the firewall reset rule to block TCP and/or UDP directly or by specifying an application that runs over UDP or TCP. See the Vulnerable Products ["#vp"] section for examples of vulnerable and non-vulnerable configurations.

  • WorkaroundCisco Secure Firewall Threat Defense (FTD) Software 7.0.0 when installed on Cisco Firepower 1000 Seriescisco_csaf

    There are workarounds that addresses this vulnerability. While these workarounds have been deployed and were proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment. Note: There are three workarounds for this issue. Implementing any of the workarounds is sufficient. Two or more workarounds do not need to be implemented. Workaround 1 The first workaround is to change the Snort inspection engine from Snort3 to Snort2. See the configuration guide or support team for potential impacts. The steps to revert to Snort2 are as follows: Go to the FMC web interface Go to the Devices page and then the Device Management tab. Select the FTD device to check. Choose Edit. Go to the Device tab and look in the Inspection Engine area. Choose the Revert to Snort2 option. Workaround 2 The second workaround is to change all rule actions from Block with Reset or Interactive Block with Reset to another action. See the configuration guide or support team for potential impacts. The steps are as follows: Go to the FMC web interface Go to the Policies page and then the Access Control tab. Select the Policy to review and choose Edit. Find a rule that has a Reset action and choose Edit. Change the action from Block with Reset or Interactive Block with Reset to another action. Workaround 3 The third workaround involves narrowing the firewall reset rule to block TCP and/or UDP directly or by specifying an application that runs over UDP or TCP. See the Vulnerable Products ["#vp"] section for examples of vulnerable and non-vulnerable configurations.

  • WorkaroundCisco Secure Firewall Threat Defense (FTD) Software 7.0.0 when installed on Cisco Firepower 2100 Seriescisco_csaf

    There are workarounds that addresses this vulnerability. While these workarounds have been deployed and were proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment. Note: There are three workarounds for this issue. Implementing any of the workarounds is sufficient. Two or more workarounds do not need to be implemented. Workaround 1 The first workaround is to change the Snort inspection engine from Snort3 to Snort2. See the configuration guide or support team for potential impacts. The steps to revert to Snort2 are as follows: Go to the FMC web interface Go to the Devices page and then the Device Management tab. Select the FTD device to check. Choose Edit. Go to the Device tab and look in the Inspection Engine area. Choose the Revert to Snort2 option. Workaround 2 The second workaround is to change all rule actions from Block with Reset or Interactive Block with Reset to another action. See the configuration guide or support team for potential impacts. The steps are as follows: Go to the FMC web interface Go to the Policies page and then the Access Control tab. Select the Policy to review and choose Edit. Find a rule that has a Reset action and choose Edit. Change the action from Block with Reset or Interactive Block with Reset to another action. Workaround 3 The third workaround involves narrowing the firewall reset rule to block TCP and/or UDP directly or by specifying an application that runs over UDP or TCP. See the Vulnerable Products ["#vp"] section for examples of vulnerable and non-vulnerable configurations.

  • WorkaroundCisco Secure Firewall Threat Defense (FTD) Software 7.0.0 when installed on Cisco Firepower 4100 Seriescisco_csaf

    There are workarounds that addresses this vulnerability. While these workarounds have been deployed and were proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment. Note: There are three workarounds for this issue. Implementing any of the workarounds is sufficient. Two or more workarounds do not need to be implemented. Workaround 1 The first workaround is to change the Snort inspection engine from Snort3 to Snort2. See the configuration guide or support team for potential impacts. The steps to revert to Snort2 are as follows: Go to the FMC web interface Go to the Devices page and then the Device Management tab. Select the FTD device to check. Choose Edit. Go to the Device tab and look in the Inspection Engine area. Choose the Revert to Snort2 option. Workaround 2 The second workaround is to change all rule actions from Block with Reset or Interactive Block with Reset to another action. See the configuration guide or support team for potential impacts. The steps are as follows: Go to the FMC web interface Go to the Policies page and then the Access Control tab. Select the Policy to review and choose Edit. Find a rule that has a Reset action and choose Edit. Change the action from Block with Reset or Interactive Block with Reset to another action. Workaround 3 The third workaround involves narrowing the firewall reset rule to block TCP and/or UDP directly or by specifying an application that runs over UDP or TCP. See the Vulnerable Products ["#vp"] section for examples of vulnerable and non-vulnerable configurations.

  • WorkaroundCisco Secure Firewall Threat Defense (FTD) Software 7.0.0 when installed on Cisco Firepower 9000 Seriescisco_csaf

    There are workarounds that addresses this vulnerability. While these workarounds have been deployed and were proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment. Note: There are three workarounds for this issue. Implementing any of the workarounds is sufficient. Two or more workarounds do not need to be implemented. Workaround 1 The first workaround is to change the Snort inspection engine from Snort3 to Snort2. See the configuration guide or support team for potential impacts. The steps to revert to Snort2 are as follows: Go to the FMC web interface Go to the Devices page and then the Device Management tab. Select the FTD device to check. Choose Edit. Go to the Device tab and look in the Inspection Engine area. Choose the Revert to Snort2 option. Workaround 2 The second workaround is to change all rule actions from Block with Reset or Interactive Block with Reset to another action. See the configuration guide or support team for potential impacts. The steps are as follows: Go to the FMC web interface Go to the Policies page and then the Access Control tab. Select the Policy to review and choose Edit. Find a rule that has a Reset action and choose Edit. Change the action from Block with Reset or Interactive Block with Reset to another action. Workaround 3 The third workaround involves narrowing the firewall reset rule to block TCP and/or UDP directly or by specifying an application that runs over UDP or TCP. See the Vulnerable Products ["#vp"] section for examples of vulnerable and non-vulnerable configurations.

  • WorkaroundCisco Secure Firewall Threat Defense (FTD) Software 7.0.0 when installed on Cisco Secure Firewall Threat Defense Virtualcisco_csaf

    There are workarounds that addresses this vulnerability. While these workarounds have been deployed and were proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment. Note: There are three workarounds for this issue. Implementing any of the workarounds is sufficient. Two or more workarounds do not need to be implemented. Workaround 1 The first workaround is to change the Snort inspection engine from Snort3 to Snort2. See the configuration guide or support team for potential impacts. The steps to revert to Snort2 are as follows: Go to the FMC web interface Go to the Devices page and then the Device Management tab. Select the FTD device to check. Choose Edit. Go to the Device tab and look in the Inspection Engine area. Choose the Revert to Snort2 option. Workaround 2 The second workaround is to change all rule actions from Block with Reset or Interactive Block with Reset to another action. See the configuration guide or support team for potential impacts. The steps are as follows: Go to the FMC web interface Go to the Policies page and then the Access Control tab. Select the Policy to review and choose Edit. Find a rule that has a Reset action and choose Edit. Change the action from Block with Reset or Interactive Block with Reset to another action. Workaround 3 The third workaround involves narrowing the firewall reset rule to block TCP and/or UDP directly or by specifying an application that runs over UDP or TCP. See the Vulnerable Products ["#vp"] section for examples of vulnerable and non-vulnerable configurations.

  • WorkaroundCisco Secure Firewall Threat Defense (FTD) Software 7.0.0.1 when installed on Cisco 3000 Series Industrial Security Appliances (ISA)cisco_csaf

    There are workarounds that addresses this vulnerability. While these workarounds have been deployed and were proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment. Note: There are three workarounds for this issue. Implementing any of the workarounds is sufficient. Two or more workarounds do not need to be implemented. Workaround 1 The first workaround is to change the Snort inspection engine from Snort3 to Snort2. See the configuration guide or support team for potential impacts. The steps to revert to Snort2 are as follows: Go to the FMC web interface Go to the Devices page and then the Device Management tab. Select the FTD device to check. Choose Edit. Go to the Device tab and look in the Inspection Engine area. Choose the Revert to Snort2 option. Workaround 2 The second workaround is to change all rule actions from Block with Reset or Interactive Block with Reset to another action. See the configuration guide or support team for potential impacts. The steps are as follows: Go to the FMC web interface Go to the Policies page and then the Access Control tab. Select the Policy to review and choose Edit. Find a rule that has a Reset action and choose Edit. Change the action from Block with Reset or Interactive Block with Reset to another action. Workaround 3 The third workaround involves narrowing the firewall reset rule to block TCP and/or UDP directly or by specifying an application that runs over UDP or TCP. See the Vulnerable Products ["#vp"] section for examples of vulnerable and non-vulnerable configurations.

  • WorkaroundCisco Secure Firewall Threat Defense (FTD) Software 7.0.0.1 when installed on Cisco Firepower 1000 Seriescisco_csaf

    There are workarounds that addresses this vulnerability. While these workarounds have been deployed and were proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment. Note: There are three workarounds for this issue. Implementing any of the workarounds is sufficient. Two or more workarounds do not need to be implemented. Workaround 1 The first workaround is to change the Snort inspection engine from Snort3 to Snort2. See the configuration guide or support team for potential impacts. The steps to revert to Snort2 are as follows: Go to the FMC web interface Go to the Devices page and then the Device Management tab. Select the FTD device to check. Choose Edit. Go to the Device tab and look in the Inspection Engine area. Choose the Revert to Snort2 option. Workaround 2 The second workaround is to change all rule actions from Block with Reset or Interactive Block with Reset to another action. See the configuration guide or support team for potential impacts. The steps are as follows: Go to the FMC web interface Go to the Policies page and then the Access Control tab. Select the Policy to review and choose Edit. Find a rule that has a Reset action and choose Edit. Change the action from Block with Reset or Interactive Block with Reset to another action. Workaround 3 The third workaround involves narrowing the firewall reset rule to block TCP and/or UDP directly or by specifying an application that runs over UDP or TCP. See the Vulnerable Products ["#vp"] section for examples of vulnerable and non-vulnerable configurations.

  • WorkaroundCisco Secure Firewall Threat Defense (FTD) Software 7.0.0.1 when installed on Cisco Firepower 2100 Seriescisco_csaf

    There are workarounds that addresses this vulnerability. While these workarounds have been deployed and were proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment. Note: There are three workarounds for this issue. Implementing any of the workarounds is sufficient. Two or more workarounds do not need to be implemented. Workaround 1 The first workaround is to change the Snort inspection engine from Snort3 to Snort2. See the configuration guide or support team for potential impacts. The steps to revert to Snort2 are as follows: Go to the FMC web interface Go to the Devices page and then the Device Management tab. Select the FTD device to check. Choose Edit. Go to the Device tab and look in the Inspection Engine area. Choose the Revert to Snort2 option. Workaround 2 The second workaround is to change all rule actions from Block with Reset or Interactive Block with Reset to another action. See the configuration guide or support team for potential impacts. The steps are as follows: Go to the FMC web interface Go to the Policies page and then the Access Control tab. Select the Policy to review and choose Edit. Find a rule that has a Reset action and choose Edit. Change the action from Block with Reset or Interactive Block with Reset to another action. Workaround 3 The third workaround involves narrowing the firewall reset rule to block TCP and/or UDP directly or by specifying an application that runs over UDP or TCP. See the Vulnerable Products ["#vp"] section for examples of vulnerable and non-vulnerable configurations.

  • WorkaroundCisco Secure Firewall Threat Defense (FTD) Software 7.0.0.1 when installed on Cisco Firepower 4100 Seriescisco_csaf

    There are workarounds that addresses this vulnerability. While these workarounds have been deployed and were proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment. Note: There are three workarounds for this issue. Implementing any of the workarounds is sufficient. Two or more workarounds do not need to be implemented. Workaround 1 The first workaround is to change the Snort inspection engine from Snort3 to Snort2. See the configuration guide or support team for potential impacts. The steps to revert to Snort2 are as follows: Go to the FMC web interface Go to the Devices page and then the Device Management tab. Select the FTD device to check. Choose Edit. Go to the Device tab and look in the Inspection Engine area. Choose the Revert to Snort2 option. Workaround 2 The second workaround is to change all rule actions from Block with Reset or Interactive Block with Reset to another action. See the configuration guide or support team for potential impacts. The steps are as follows: Go to the FMC web interface Go to the Policies page and then the Access Control tab. Select the Policy to review and choose Edit. Find a rule that has a Reset action and choose Edit. Change the action from Block with Reset or Interactive Block with Reset to another action. Workaround 3 The third workaround involves narrowing the firewall reset rule to block TCP and/or UDP directly or by specifying an application that runs over UDP or TCP. See the Vulnerable Products ["#vp"] section for examples of vulnerable and non-vulnerable configurations.

  • WorkaroundCisco Secure Firewall Threat Defense (FTD) Software 7.0.0.1 when installed on Cisco Firepower 9000 Seriescisco_csaf

    There are workarounds that addresses this vulnerability. While these workarounds have been deployed and were proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment. Note: There are three workarounds for this issue. Implementing any of the workarounds is sufficient. Two or more workarounds do not need to be implemented. Workaround 1 The first workaround is to change the Snort inspection engine from Snort3 to Snort2. See the configuration guide or support team for potential impacts. The steps to revert to Snort2 are as follows: Go to the FMC web interface Go to the Devices page and then the Device Management tab. Select the FTD device to check. Choose Edit. Go to the Device tab and look in the Inspection Engine area. Choose the Revert to Snort2 option. Workaround 2 The second workaround is to change all rule actions from Block with Reset or Interactive Block with Reset to another action. See the configuration guide or support team for potential impacts. The steps are as follows: Go to the FMC web interface Go to the Policies page and then the Access Control tab. Select the Policy to review and choose Edit. Find a rule that has a Reset action and choose Edit. Change the action from Block with Reset or Interactive Block with Reset to another action. Workaround 3 The third workaround involves narrowing the firewall reset rule to block TCP and/or UDP directly or by specifying an application that runs over UDP or TCP. See the Vulnerable Products ["#vp"] section for examples of vulnerable and non-vulnerable configurations.

  • WorkaroundCisco Secure Firewall Threat Defense (FTD) Software 7.0.0.1 when installed on Cisco Secure Firewall Threat Defense Virtualcisco_csaf

    There are workarounds that addresses this vulnerability. While these workarounds have been deployed and were proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment. Note: There are three workarounds for this issue. Implementing any of the workarounds is sufficient. Two or more workarounds do not need to be implemented. Workaround 1 The first workaround is to change the Snort inspection engine from Snort3 to Snort2. See the configuration guide or support team for potential impacts. The steps to revert to Snort2 are as follows: Go to the FMC web interface Go to the Devices page and then the Device Management tab. Select the FTD device to check. Choose Edit. Go to the Device tab and look in the Inspection Engine area. Choose the Revert to Snort2 option. Workaround 2 The second workaround is to change all rule actions from Block with Reset or Interactive Block with Reset to another action. See the configuration guide or support team for potential impacts. The steps are as follows: Go to the FMC web interface Go to the Policies page and then the Access Control tab. Select the Policy to review and choose Edit. Find a rule that has a Reset action and choose Edit. Change the action from Block with Reset or Interactive Block with Reset to another action. Workaround 3 The third workaround involves narrowing the firewall reset rule to block TCP and/or UDP directly or by specifying an application that runs over UDP or TCP. See the Vulnerable Products ["#vp"] section for examples of vulnerable and non-vulnerable configurations.

02

cvss

Technischer Schweregrad, 0–10. Eine Zeile je Quelle.

8.6
010

Basiswert 0–10 · höher = schwerwiegender · Vektor überfahren zum Auflösen⚠ Quellen uneinig · medium–high · 6.9–8.6

v2.07.1highAV:N/AC:M/Au:N/C:N/I:N/A:Cprimary · NVD / NIST USAusnutzbarkeit 8.6 · Auswirkung 6.9
v3.17.5highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Hprimary · NVD / NIST USAusnutzbarkeit 3.9 · Auswirkung 3.6
v3.18.6highAV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:Hsecondary · FSTEC (BDU) RU
v3.18.6highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:Hsecondary · ENISA EU
v3.18.6highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:Hsecondary · psirt@cisco.com USAusnutzbarkeit 3.9 · Auswirkung 4
v3.16.9mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:Usecondary · CVSS-BT (t0sche)
v3.18.6highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:Hsecondary · Cisco PSIRT US
03

SSVC

Eine Handlungsentscheidung — aus Ausnutzung und Auswirkung.

Exploitation: none · Automatable: yes · Technical Impact: partialcoordinatorcisa_ssvcUS
04

schwächen

Die CWE-Schwächeklassen, zu denen dies gehört.

CWE-241USCWE-241US
05

betroffene Produkte (23)

Betroffene Produkte und Versionsbereiche.

20 von 23 angezeigt
06

Advisories (2)

Hersteller- und Ökosystem-Meldungen dazu.

  • WID-SEC-W-2023-0335Cisco Firepower und Snort: Mehrere Schwachstellen ermöglichen Denial of ServiceDeutsch2021-10-27csaf · cert_bundDE

    Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Cisco Firepower und Snort ausnutzen, um einen Denial of Service Angriff durchzuführen.

  • cisco-sa-snort-dos-RywH7ezMMultiple Cisco Products Snort Rule Denial of Service Vulnerability2021-10-27csaf · cisco_csafUS

    Multiple Cisco products are affected by a vulnerability in Snort rules that could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device. The vulnerability is due to improper handling of the Block with Reset or Interactive Block with Reset actions if a rule is configured without proper constraints. An attacker could exploit this vulnerability by sending a crafted IP packet to the affected device. A successful exploit could allow the attacker to cause through traffic to be dropped. Note: Only products with Snort3 configured and either a rule with Block with Reset or Interactive Block with Reset actions configured are vulnerable. Products configured with Snort2 are not vulnerable. Cisco has released software updates that address this vulnerability. There are workarounds that address this vulnerability. This advisory is part of the October 2021 release of the Cisco ASA, FTD, and FMC Security Advisory Bundled publication. For a complete list of the advisories and links to them, see Cisco Event Response: October 2021 Cisco ASA, FMC, and FTD Software Security Advisory Bundled Publication ["https://sec.cloudapps.cisco.com/security/center/viewErp.x?alertId=ERP-74773"].

07

auch bekannt als (4)

Weitere Namen und Kennungen dieser Entität.

08

quellen

Welche Quellen diesen Datensatz belegen und wann.

cnnvdenisa_euvdfstec_bducert_bundcisco_csafnvdNVDCVE.orgMITRE
veröffentlicht 2021-10-27geändert 2026-08-11
09

Referenzen (7)

Externe Belege — Patches, Meldungen, Analysen.

scry

Angreifer nutzen Schwachstellen wie diese gegen im Internet exponierte Dienste aus. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.

Kostenloser Scan