var-200908-0248
Vulnerability from variot
The Cisco Firewall Services Module (FWSM) 2.x, 3.1 before 3.1(16), 3.2 before 3.2(13), and 4.0 before 4.0(6) for Cisco Catalyst 6500 switches and Cisco 7600 routers allows remote attackers to cause a denial of service (traffic-handling outage) via a series of malformed ICMP messages. Attackers can exploit this issue to cause the vulnerable module to fail to respond to further traffic, resulting in a denial-of-service condition. This issue is tracked by Cisco Bug ID CSCsz97207. ----------------------------------------------------------------------
Do you have VARM strategy implemented?
(Vulnerability Assessment Remediation Management)
If not, then implement it through the most reliable vulnerability intelligence source on the market.
Implement it through Secunia.
SOLUTION: Update to version 3.1(16), 3.2(13), or 4.0(6).
Users of version 2.x should migrate to either 3.x or 4.x.
PROVIDED AND/OR DISCOVERED BY: Reported by the vendor.
Subscribe: http://secunia.com/advisories/secunia_security_advisories/
Definitions: (Criticality, Where etc.) http://secunia.com/advisories/about_secunia_advisories/
Please Note: Secunia recommends that you verify all advisories you receive by clicking the link. Secunia NEVER sends attached files with advisories. Secunia does not advise people to install third party patches, only use those supplied by the vendor. The vulnerability may cause the FWSM to stop forwarding traffic and may be triggered while processing multiple, crafted ICMP messages.
There are no known instances of intentional exploitation of this vulnerability. However, Cisco has observed data streams that appear to trigger this vulnerability unintentionally.
Cisco has released free software updates that address this vulnerability.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090819-fwsm.shtml.
Affected Products
Vulnerable Products
All non-fixed 2.x, 3.x and 4.x versions of the FWSM software are affected by this vulnerability.
To determine the version of the FWSM software that is running, issue the "show module" command-line interface (CLI) command from Cisco IOS Software or Cisco Catalyst Operating System Software to identify what modules and sub-modules are installed in the system.
The following example shows a system with an FWSM (WS-SVC-FWM-1) installed in slot 4.
switch#show module Mod Ports Card Type Model Serial No.
1 48 SFM-capable 48 port 10/100/1000mb RJ45 WS-X6548-GE-TX SAxxxxxxxxx 4 6 Firewall Module WS-SVC-FWM-1 SAxxxxxxxxx 5 2 Supervisor Engine 720 (Active) WS-SUP720-BASE SAxxxxxxxxx 6 2 Supervisor Engine 720 (Hot) WS-SUP720-BASE SAxxxxxxxxx
After locating the correct slot, issue the "show module " command to identify the software version that is running.
switch#show module 4 Mod Ports Card Type Model Serial No.
4 6 Firewall Module WS-SVC-FWM-1 SAxxxxxxxxx
Mod MAC addresses Hw Fw Sw Status
4 0003.e4xx.xxxx to 0003.e4xx.xxxx 3.0 7.2(1) 3.2(3) Ok
The preceding example shows that the FWSM is running software version 3.2(3) as indicated by the column under "Sw".
Note: Recent versions of Cisco IOS Software will show the software version of each module in the output from the "show module" command; therefore, executing the "show module " command is not necessary.
If a Virtual Switching System (VSS) is used to allow two physical Cisco Catalyst 6500 Series Switches to operate as a single logical virtual switch, the "show module switch all" command can display the software version of all FWSMs that belong to switch 1 and switch 2. The output from this command will be similar to the output from the "show module " but will include module information for the modules in each switch in the VSS.
Alternatively, version information can be obtained directly from the FWSM through the "show version" command, as shown in the following example.
FWSM#show version FWSM Firewall Version 3.2(3)
Customers who use the Cisco Adaptive Security Device Manager (ASDM) to manage their devices can find the version of the software displayed in the table in the login window or in the upper left corner of the ASDM window. The version notation is similar to the following example.
FWSM Version: 3.2(3)
Products Confirmed Not Vulnerable
Other Cisco products that offer firewall services, including Cisco IOS Software, Cisco ASA 5500 Series Adaptive Security Appliances, and Cisco PIX Security Appliances, are not affected by this vulnerability.
No other Cisco products are currently known to be affected by this vulnerability. The FWSM offers firewall services with stateful packet filtering and deep packet inspection.
A vulnerability exists in the Cisco FWSM Software that may cause the FWSM to stop forwarding traffic between interfaces, or stop processing traffic that is directed at the FWSM (management traffic) after multiple, crafted ICMP messages are processed by the FWSM. Any traffic that transits or is directed towards the FWSM is affected, regardless of whether ICMP inspection ("inspect icmp" command under Class configuration mode) is enabled.
The FWSM stops processing traffic because one of the Network Processors (NPs) that is used by the FWSM to handle traffic may use all available execution threads while handling a specific type of crafted ICMP messages. This behavior limits the execution threads that are available to handle additional traffic.
Administrators may be able to determine if the FWSM has been affected by this vulnerability by issuing the "show np 2 stats" command. If this command produces output showing various counters and their values, as shown in the example CLI output that follows, the FWSM has not been affected by the vulnerability. If the command returns a single line that reads "ERROR: np_logger_query request for FP Stats failed", the FWSM may have been affected by the vulnerability.
FWSM#show np 2 stats
Fast Path 64 bit Global Statistics Counters (NP-2)
-
PKT_MNG: total packets (dot1q) rcvd : 10565937 PKT_MNG: total packets (dot1q) sent : 4969517 PKT_MNG: total packets (dot1q) dropped : 65502 PKT_MNG: TCP packets received : 0 PKT_MNG: UDP packets received : 4963509 PKT_MNG: ICMP packets received : 0 PKT_MNG: ARP packets received : 2 PKT_MNG: other protocol pkts received : 0 PKT_MNG: default (no IP/ARP) dropped : 0 SESS_MNG: sessions created : 18 SESS_MNG: sessions embryonic to active : 0 [...]
An FWSM that stops processing traffic as a result of this vulnerability will need to be reloaded. Note that unless the FWSM software is updated to a non-vulnerable version, or crafted ICMP messages are blocked (see the Workarounds section for details), the FWSM can still be subject to exploitation (intentional or otherwise) after a reload.
If an FWSM that is configured for failover operation encounters this issue, the active FWSM may not properly fail over to the standby FWSM.
IPv6 (in particular ICMPv6) cannot trigger this vulnerability.
Vulnerability Scoring Details +----------------------------
Cisco has provided scores for the vulnerability in this advisory based on the Common Vulnerability Scoring System (CVSS). The CVSS scoring in this Security Advisory is done in accordance with CVSS version 2.0.
CVSS is a standards-based scoring method that conveys vulnerability severity and helps determine urgency and priority of response.
Cisco has provided a base and temporal score. Customers can then compute environmental scores to assist in determining the impact of the vulnerability in individual networks.
Cisco has provided a FAQ to answer additional questions regarding CVSS at:
http://www.cisco.com/web/about/security/intelligence/cvss-qandas.html
Cisco has also provided a CVSS calculator to help compute the environmental impact for individual networks at:
http://intellishield.cisco.com/security/alertmanager/cvss
- NP 2 threads lock due to processing crafted ICMP message (CSCsz97207)
CVSS Base Score - 7.8 Access Vector - Network Access Complexity - Low Authentication - None Confidentiality Impact - None Integrity Impact - None Availability Impact - Complete
CVSS Temporal Score - 6.4 Exploitability - Functional Remediation Level - Official-Fix Report Confidence - Confirmed
Impact
Successful exploitation of the vulnerability may cause the FWSM to stop forwarding traffic between interfaces (transit traffic), and stop processing traffic directed at the FWSM (management traffic). If the FWSM is configured for failover operation, the active FWSM may not fail over to the standby FWSM.
Software Versions and Fixes
When considering software upgrades, also consult http://www.cisco.com/go/psirt and any subsequent advisories to determine exposure and a complete upgrade solution.
In all cases, customers should exercise caution to be certain the devices to be upgraded contain sufficient memory and that current hardware and software configurations will continue to be supported properly by the new release. If the information is not clear, contact the Cisco Technical Assistance Center (TAC) or your contracted maintenance provider for assistance.
Each row of the FWSM software table below describes a major FWSM software train and the earliest possible release within that train that contains the fix (the "First Fixed Release") and the anticipated date of availability (if not currently available) in the "First Fixed Release" column. A device running a release that is earlier than the release in a specific column (less than the First Fixed Release) is known to be vulnerable. The release should be upgraded at least to the indicated release or a later version (greater than or equal to the First Fixed Release label).
+---------------------------------------+ | Major | First Fixed Release | | Release | | |------------+--------------------------| | 2.x | Vulnerable; migrate to | | | 3.x or 4.x | |------------+--------------------------| | 3.1 | 3.1(16) | |------------+--------------------------| | 3.2 | 3.2(13) | |------------+--------------------------| | 4.0 | 4.0(6) | +---------------------------------------+
Fixed FWSM software can be downloaded from the Software Center on cisco.com by visiting http://www.cisco.com/public/sw-center/index.shtml and navigating to "Security" > "Cisco Catalyst 6500 Series Firewall Services Module" > "Firewall Services Module (FWSM) Software".
Workarounds
There are no workarounds for this vulnerability. Access control lists (ACLs) that are deployed on the FWSM itself to block through-the-device or to-the-device ICMP messages are not effective to prevent this vulnerability. However, blocking unnecessary ICMP messages on screening devices or on devices in the path to the FWSM will prevent the FWSM from triggering the vulnerability. For example, the following ACL, when deployed on a Cisco IOS device in front of the FWSM, will prevent crafted ICMP messages from reaching the FWSM, and thus protect the FWSM from triggering the vulnerability:
access-list 101 permit icmp any any echo access-list 101 permit icmp any any echo-reply access-list 101 permit icmp any any traceroute access-list 101 permit icmp any any packet-too-big access-list 101 permit icmp any any time-exceeded access-list 101 permit icmp any any host-unreachable access-list 101 permit icmp any any unreachable access-list 101 deny icmp any any access-list 101 permit ip any any
This sample ACL is allowing certain ICMP messages that are vital for network troubleshooting and for proper operation of the network. It is safe to allow any other ICMP messages for which the Cisco IOS Software "access-list" command has named ICMP type keywords. ACLs like the one in the preceding example may also be deployed on non-Cisco IOS devices, such as the Cisco PIX and ASA security appliances, although the ACL syntax on non-Cisco IOS devices may not support all the named ICMP type keywords that the Cisco IOS ACL syntax supports. However, on non-Cisco IOS devices, it is safe to permit all ICMP messages for which there are named ICMP type keywords in the ACL syntax.
As mentioned in the Details section, if the FWSM has stopped processing traffic due to this vulnerability, the FWSM will require a reload.
Additional mitigations that can be deployed on Cisco devices within the network are available in the Cisco Applied Mitigation Bulletin companion document for this advisory, which is available at the following link:
http://www.cisco.com/warp/public/707/cisco-amb-20090819-fwsm.shtml.
Obtaining Fixed Software
Cisco has released free software updates that address this vulnerability. Prior to deploying software, customers should consult their maintenance provider or check the software for feature set compatibility and known issues specific to their environment.
Customers may only install and expect support for the feature sets they have purchased. By installing, downloading, accessing or otherwise using such software upgrades, customers agree to be bound by the terms of Cisco's software license terms found at http://www.cisco.com/en/US/docs/general/warranty/English/EU1KEN_.html, or as otherwise set forth at Cisco.com Downloads at http://www.cisco.com/public/sw-center/sw-usingswc.shtml.
Do not contact psirt@cisco.com or security-alert@cisco.com for software upgrades.
Customers with Service Contracts
Customers with contracts should obtain upgraded software through their regular update channels. For most customers, this means that upgrades should be obtained through the Software Center on Cisco's worldwide website at http://www.cisco.com.
Customers using Third Party Support Organizations
Customers whose Cisco products are provided or maintained through prior or existing agreements with third-party support organizations, such as Cisco Partners, authorized resellers, or service providers should contact that support organization for guidance and assistance with the appropriate course of action in regards to this advisory.
The effectiveness of any workaround or fix is dependent on specific customer situations, such as product mix, network topology, traffic behavior, and organizational mission. Due to the variety of affected products and releases, customers should consult with their service provider or support organization to ensure any applied workaround or fix is the most appropriate for use in the intended network before it is deployed.
Customers without Service Contracts
Customers who purchase direct from Cisco but do not hold a Cisco service contract, and customers who purchase through third-party vendors but are unsuccessful in obtaining fixed software through their point of sale should acquire upgrades by contacting the Cisco Technical Assistance Center (TAC). TAC contacts are as follows.
- +1 800 553 2447 (toll free from within North America)
- +1 408 526 7209 (toll call from anywhere in the world)
- e-mail: tac@cisco.com
Customers should have their product serial number available and be prepared to give the URL of this notice as evidence of entitlement to a free upgrade. Free upgrades for non-contract customers must be requested through the TAC.
Refer to http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html for additional TAC contact information, including localized telephone numbers, and instructions and e-mail addresses for use in various languages.
Exploitation and Public Announcements
The Cisco PSIRT is not aware of any public announcements or malicious use of the vulnerability described in this advisory, but Cisco is aware of customers that have encountered this vulnerability during normal network operation.
This vulnerability was discovered during the handling of customer support cases.
Status of this Notice: FINAL
THIS DOCUMENT IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR USE. YOUR USE OF THE INFORMATION ON THE DOCUMENT OR MATERIALS LINKED FROM THE DOCUMENT IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS DOCUMENT AT ANY TIME.
A stand-alone copy or Paraphrase of the text of this document that omits the distribution URL in the following section is an uncontrolled copy, and may lack important information or contain factual errors.
Distribution
This advisory is posted on Cisco's worldwide website at:
http://www.cisco.com/warp/public/707/cisco-sa-20090819-fwsm.shtml
In addition to worldwide web posting, a text version of this notice is clear-signed with the Cisco PSIRT PGP key and is posted to the following e-mail and Usenet news recipients.
- cust-security-announce@cisco.com
- first-bulletins@lists.first.org
- bugtraq@securityfocus.com
- vulnwatch@vulnwatch.org
- cisco@spot.colorado.edu
- cisco-nsp@puck.nether.net
- full-disclosure@lists.grok.org.uk
- comp.dcom.sys.cisco@newsgate.cisco.com
Future updates of this advisory, if any, will be placed on Cisco's worldwide website, but may or may not be actively announced on mailing lists or newsgroups. Users concerned about this problem are encouraged to check the above URL for any updates.
Revision History
+------------------------------------------------------------+ | Revision 1.0 | 2009-August-19 | Initial public release | +------------------------------------------------------------+
Cisco Security Procedures
Complete information on reporting security vulnerabilities in Cisco products, obtaining assistance with security incidents, and registering to receive security information from Cisco, is available on Cisco's worldwide website at http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html . This includes instructions for press inquiries regarding Cisco security notices. All Cisco security advisories are available at http://www.cisco.com/go/psirt.
+-------------------------------------------------------------------- Copyright 2008-2009 Cisco Systems, Inc. All rights reserved. +--------------------------------------------------------------------
Updated: Aug 19, 2009 Document ID: 110460 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkqMMFYACgkQ86n/Gc8U/uA2jACeLVA38jWbQv4AGpSCvOPVJjgR NqUAniMoiEUkV/JIDlo1xA0ztaO6jCFR =2Tm1 -----END PGP SIGNATURE-----
Show details on source website{
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/VARIoTentry#",
"affected_products": {
"@id": "https://www.variotdbs.pl/ref/affected_products"
},
"configurations": {
"@id": "https://www.variotdbs.pl/ref/configurations"
},
"credits": {
"@id": "https://www.variotdbs.pl/ref/credits"
},
"cvss": {
"@id": "https://www.variotdbs.pl/ref/cvss/"
},
"description": {
"@id": "https://www.variotdbs.pl/ref/description/"
},
"exploit_availability": {
"@id": "https://www.variotdbs.pl/ref/exploit_availability/"
},
"external_ids": {
"@id": "https://www.variotdbs.pl/ref/external_ids/"
},
"iot": {
"@id": "https://www.variotdbs.pl/ref/iot/"
},
"iot_taxonomy": {
"@id": "https://www.variotdbs.pl/ref/iot_taxonomy/"
},
"patch": {
"@id": "https://www.variotdbs.pl/ref/patch/"
},
"problemtype_data": {
"@id": "https://www.variotdbs.pl/ref/problemtype_data/"
},
"references": {
"@id": "https://www.variotdbs.pl/ref/references/"
},
"sources": {
"@id": "https://www.variotdbs.pl/ref/sources/"
},
"sources_release_date": {
"@id": "https://www.variotdbs.pl/ref/sources_release_date/"
},
"sources_update_date": {
"@id": "https://www.variotdbs.pl/ref/sources_update_date/"
},
"threat_type": {
"@id": "https://www.variotdbs.pl/ref/threat_type/"
},
"title": {
"@id": "https://www.variotdbs.pl/ref/title/"
},
"type": {
"@id": "https://www.variotdbs.pl/ref/type/"
}
},
"@id": "https://www.variotdbs.pl/vuln/VAR-200908-0248",
"affected_products": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/affected_products#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
},
"@id": "https://www.variotdbs.pl/ref/sources"
}
},
"data": [
{
"model": "firewall services module",
"scope": "eq",
"trust": 1.9,
"vendor": "cisco",
"version": "2.3"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 1.9,
"vendor": "cisco",
"version": "3.1"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 1.6,
"vendor": "cisco",
"version": "2.3\\(1\\)"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 1.6,
"vendor": "cisco",
"version": "2.1_\\(0.208\\)"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 1.6,
"vendor": "cisco",
"version": "3.2"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 1.6,
"vendor": "cisco",
"version": "3.2\\(3\\)"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 1.6,
"vendor": "cisco",
"version": "3.2\\(2\\)"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 1.6,
"vendor": "cisco",
"version": "3.1\\(5\\)"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 1.6,
"vendor": "cisco",
"version": "3.2\\(1\\)"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 1.6,
"vendor": "cisco",
"version": "3.1\\(6\\)"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 1.0,
"vendor": "cisco",
"version": "4.0\\(4\\)"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 1.0,
"vendor": "cisco",
"version": "2.2"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 1.0,
"vendor": "cisco",
"version": "4.0"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 1.0,
"vendor": "cisco",
"version": "2.2\\(1\\)"
},
{
"model": "7600 series",
"scope": null,
"trust": 0.8,
"vendor": "cisco",
"version": null
},
{
"model": "catalyst 6500 series",
"scope": null,
"trust": 0.8,
"vendor": "cisco",
"version": null
},
{
"model": "firewall services module",
"scope": "lt",
"trust": 0.8,
"vendor": "cisco",
"version": "3.1(16)"
},
{
"model": "firewall services module",
"scope": "lt",
"trust": 0.8,
"vendor": "cisco",
"version": "3.2(13)"
},
{
"model": "firewall services module",
"scope": "lt",
"trust": 0.8,
"vendor": "cisco",
"version": "4.0(6)"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "3.1(6)"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "3.1(3.2)"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "2.3(4)"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "3.2(2)"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "3.1(3.1)"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "2.3(4.12)"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "2.3(5)"
},
{
"model": "firewall services module",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": "3.1(16)"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "2.3(4.7)"
},
{
"model": "firewall services module",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": "3.2(13)"
},
{
"model": "firewall services module",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": "4.0(6)"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "3.1(1.9)"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "3.1(4)"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "3.1(3.24)"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "3.1(3.18)"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "3.1(3.3)"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "3.1(1.7)"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "3.1(3.11)"
}
],
"sources": [
{
"db": "BID",
"id": "36085"
},
{
"db": "JVNDB",
"id": "JVNDB-2009-002659"
},
{
"db": "CNNVD",
"id": "CNNVD-200908-296"
},
{
"db": "NVD",
"id": "CVE-2009-0638"
}
]
},
"configurations": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/configurations#",
"children": {
"@container": "@list"
},
"cpe_match": {
"@container": "@list"
},
"data": {
"@container": "@list"
},
"nodes": {
"@container": "@list"
}
},
"data": [
{
"CVE_data_version": "4.0",
"nodes": [
{
"cpe_match": [
{
"cpe22Uri": "cpe:/h:cisco:7600_router",
"vulnerable": true
},
{
"cpe22Uri": "cpe:/h:cisco:catalyst_6500",
"vulnerable": true
},
{
"cpe22Uri": "cpe:/h:cisco:firewall_services_module",
"vulnerable": true
}
],
"operator": "OR"
}
]
}
],
"sources": [
{
"db": "JVNDB",
"id": "JVNDB-2009-002659"
}
]
},
"credits": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/credits#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "Cisco Security bulletin",
"sources": [
{
"db": "CNNVD",
"id": "CNNVD-200908-296"
}
],
"trust": 0.6
},
"cve": "CVE-2009-0638",
"cvss": {
"@context": {
"cvssV2": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/cvss/cvssV2#"
},
"@id": "https://www.variotdbs.pl/ref/cvss/cvssV2"
},
"cvssV3": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/cvss/cvssV3#"
},
"@id": "https://www.variotdbs.pl/ref/cvss/cvssV3/"
},
"severity": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/cvss/severity#"
},
"@id": "https://www.variotdbs.pl/ref/cvss/severity"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
},
"@id": "https://www.variotdbs.pl/ref/sources"
}
},
"data": [
{
"cvssV2": [
{
"accessComplexity": "LOW",
"accessVector": "NETWORK",
"authentication": "NONE",
"author": "nvd@nist.gov",
"availabilityImpact": "COMPLETE",
"baseScore": 7.8,
"confidentialityImpact": "NONE",
"exploitabilityScore": 10.0,
"id": "CVE-2009-0638",
"impactScore": 6.9,
"integrityImpact": "NONE",
"severity": "HIGH",
"trust": 1.8,
"vectorString": "AV:N/AC:L/Au:N/C:N/I:N/A:C",
"version": "2.0"
},
{
"accessComplexity": "LOW",
"accessVector": "NETWORK",
"authentication": "NONE",
"author": "VULHUB",
"availabilityImpact": "COMPLETE",
"baseScore": 7.8,
"confidentialityImpact": "NONE",
"exploitabilityScore": 10.0,
"id": "VHN-38084",
"impactScore": 6.9,
"integrityImpact": "NONE",
"severity": "HIGH",
"trust": 0.1,
"vectorString": "AV:N/AC:L/AU:N/C:N/I:N/A:C",
"version": "2.0"
}
],
"cvssV3": [],
"severity": [
{
"author": "nvd@nist.gov",
"id": "CVE-2009-0638",
"trust": 1.0,
"value": "HIGH"
},
{
"author": "NVD",
"id": "CVE-2009-0638",
"trust": 0.8,
"value": "High"
},
{
"author": "CNNVD",
"id": "CNNVD-200908-296",
"trust": 0.6,
"value": "HIGH"
},
{
"author": "VULHUB",
"id": "VHN-38084",
"trust": 0.1,
"value": "HIGH"
}
]
}
],
"sources": [
{
"db": "VULHUB",
"id": "VHN-38084"
},
{
"db": "JVNDB",
"id": "JVNDB-2009-002659"
},
{
"db": "CNNVD",
"id": "CNNVD-200908-296"
},
{
"db": "NVD",
"id": "CVE-2009-0638"
}
]
},
"description": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/description#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "The Cisco Firewall Services Module (FWSM) 2.x, 3.1 before 3.1(16), 3.2 before 3.2(13), and 4.0 before 4.0(6) for Cisco Catalyst 6500 switches and Cisco 7600 routers allows remote attackers to cause a denial of service (traffic-handling outage) via a series of malformed ICMP messages. \nAttackers can exploit this issue to cause the vulnerable module to fail to respond to further traffic, resulting in a denial-of-service condition. \nThis issue is tracked by Cisco Bug ID CSCsz97207. ----------------------------------------------------------------------\n\nDo you have VARM strategy implemented?\n\n(Vulnerability Assessment Remediation Management) \n\nIf not, then implement it through the most reliable vulnerability\nintelligence source on the market. \n\nImplement it through Secunia. \n\nSOLUTION:\nUpdate to version 3.1(16), 3.2(13), or 4.0(6). \n\nUsers of version 2.x should migrate to either 3.x or 4.x. \n\nPROVIDED AND/OR DISCOVERED BY:\nReported by the vendor. \n\nSubscribe:\nhttp://secunia.com/advisories/secunia_security_advisories/\n\nDefinitions: (Criticality, Where etc.)\nhttp://secunia.com/advisories/about_secunia_advisories/\n\n\nPlease Note:\nSecunia recommends that you verify all advisories you receive by\nclicking the link. \nSecunia NEVER sends attached files with advisories. \nSecunia does not advise people to install third party patches, only\nuse those supplied by the vendor. The\nvulnerability may cause the FWSM to stop forwarding traffic and may be\ntriggered while processing multiple, crafted ICMP messages. \n\nThere are no known instances of intentional exploitation of this\nvulnerability. However, Cisco has observed data streams that appear to\ntrigger this vulnerability unintentionally. \n\nCisco has released free software updates that address this\nvulnerability. \n\nThis advisory is posted at\nhttp://www.cisco.com/warp/public/707/cisco-sa-20090819-fwsm.shtml. \n\nAffected Products\n=================\n\nVulnerable Products\n- -------------------\n\nAll non-fixed 2.x, 3.x and 4.x versions of the FWSM software are\naffected by this vulnerability. \n\nTo determine the version of the FWSM software that is running, issue\nthe \"show module\" command-line interface (CLI) command from Cisco IOS\nSoftware or Cisco Catalyst Operating System Software to identify what\nmodules and sub-modules are installed in the system. \n\nThe following example shows a system with an FWSM (WS-SVC-FWM-1)\ninstalled in slot 4. \n\nswitch#show module\n Mod Ports Card Type Model Serial\nNo. \n --- ----- -------------------------------------- -----------------\n-----------\n 1 48 SFM-capable 48 port 10/100/1000mb RJ45 WS-X6548-GE-TX\n SAxxxxxxxxx\n 4 6 Firewall Module WS-SVC-FWM-1\n SAxxxxxxxxx\n 5 2 Supervisor Engine 720 (Active) WS-SUP720-BASE\n SAxxxxxxxxx\n 6 2 Supervisor Engine 720 (Hot) WS-SUP720-BASE\n SAxxxxxxxxx\n\nAfter locating the correct slot, issue the \"show module \u003cslot number\u003e\"\ncommand to identify the software version that is running. \n\nswitch#show module 4\n Mod Ports Card Type Model Serial\nNo. \n --- ----- -------------------------------------- -----------------\n-----------\n 4 6 Firewall Module WS-SVC-FWM-1\n SAxxxxxxxxx\n\n Mod MAC addresses Hw Fw Sw\nStatus\n --- --------------------------------- ------ ------------ ------------\n-------\n 4 0003.e4xx.xxxx to 0003.e4xx.xxxx 3.0 7.2(1) 3.2(3) Ok\n\nThe preceding example shows that the FWSM is running software version\n3.2(3) as indicated by the column under \"Sw\". \n\nNote: Recent versions of Cisco IOS Software will show the software\nversion of each module in the output from the \"show module\" command;\ntherefore, executing the \"show module \u003cslot number\u003e\" command is not\nnecessary. \n\nIf a Virtual Switching System (VSS) is used to allow two physical Cisco\nCatalyst 6500 Series Switches to operate as a single logical virtual\nswitch, the \"show module switch all\" command can display the software\nversion of all FWSMs that belong to switch 1 and switch 2. The output\nfrom this command will be similar to the output from the \"show module\n\u003cslot number\u003e\" but will include module information for the modules in\neach switch in the VSS. \n\nAlternatively, version information can be obtained directly from the\nFWSM through the \"show version\" command, as shown in the following\nexample. \n\n FWSM#show version\n FWSM Firewall Version 3.2(3)\n\nCustomers who use the Cisco Adaptive Security Device Manager (ASDM) to\nmanage their devices can find the version of the software displayed in\nthe table in the login window or in the upper left corner of the ASDM\nwindow. The version notation is similar to the following example. \n\n FWSM Version: 3.2(3)\n\nProducts Confirmed Not Vulnerable\n- ---------------------------------\n\nOther Cisco products that offer firewall services, including Cisco IOS\nSoftware, Cisco ASA 5500 Series Adaptive Security Appliances, and Cisco\nPIX Security Appliances, are not affected by this vulnerability. \n\nNo other Cisco products are currently known to be affected by this\nvulnerability. The FWSM offers\nfirewall services with stateful packet filtering and deep packet\ninspection. \n\nA vulnerability exists in the Cisco FWSM Software that may cause\nthe FWSM to stop forwarding traffic between interfaces, or stop\nprocessing traffic that is directed at the FWSM (management traffic)\nafter multiple, crafted ICMP messages are processed by the FWSM. Any\ntraffic that transits or is directed towards the FWSM is affected,\nregardless of whether ICMP inspection (\"inspect icmp\" command under\nClass configuration mode) is enabled. \n\nThe FWSM stops processing traffic because one of the Network Processors\n(NPs) that is used by the FWSM to handle traffic may use all available\nexecution threads while handling a specific type of crafted ICMP\nmessages. This behavior limits the execution threads that are available\nto handle additional traffic. \n\nAdministrators may be able to determine if the FWSM has been affected\nby this vulnerability by issuing the \"show np 2 stats\" command. If this\ncommand produces output showing various counters and their values, as\nshown in the example CLI output that follows, the FWSM has not been\naffected by the vulnerability. If the command returns a single line that\nreads \"ERROR: np_logger_query request for FP Stats failed\", the FWSM may\nhave been affected by the vulnerability. \n\nFWSM#show np 2 stats\n-\n-------------------------------------------------------------------------------\nFast Path 64 bit Global Statistics Counters (NP-2)\n\n-\n-------------------------------------------------------------------------------\nPKT_MNG: total packets (dot1q) rcvd : 10565937\nPKT_MNG: total packets (dot1q) sent : 4969517\nPKT_MNG: total packets (dot1q) dropped : 65502\nPKT_MNG: TCP packets received : 0\nPKT_MNG: UDP packets received : 4963509\nPKT_MNG: ICMP packets received : 0\nPKT_MNG: ARP packets received : 2\nPKT_MNG: other protocol pkts received : 0\nPKT_MNG: default (no IP/ARP) dropped : 0\nSESS_MNG: sessions created : 18\nSESS_MNG: sessions embryonic to active : 0\n[...]\n\nAn FWSM that stops processing traffic as a result of this vulnerability\nwill need to be reloaded. Note that unless the FWSM software is updated to a\nnon-vulnerable version, or crafted ICMP messages are blocked (see the\nWorkarounds section for details), the FWSM can still be subject to\nexploitation (intentional or otherwise) after a reload. \n\nIf an FWSM that is configured for failover operation encounters this\nissue, the active FWSM may not properly fail over to the standby FWSM. \n\nIPv6 (in particular ICMPv6) cannot trigger this vulnerability. \n\nVulnerability Scoring Details\n+----------------------------\n\nCisco has provided scores for the vulnerability in this advisory based\non the Common Vulnerability Scoring System (CVSS). The CVSS scoring in\nthis Security Advisory is done in accordance with CVSS version 2.0. \n\nCVSS is a standards-based scoring method that conveys vulnerability\nseverity and helps determine urgency and priority of response. \n\nCisco has provided a base and temporal score. Customers can then\ncompute environmental scores to assist in determining the impact of the\nvulnerability in individual networks. \n\nCisco has provided a FAQ to answer additional questions regarding CVSS\nat:\n\nhttp://www.cisco.com/web/about/security/intelligence/cvss-qandas.html\n\nCisco has also provided a CVSS calculator to help compute the\nenvironmental impact for individual networks at:\n\nhttp://intellishield.cisco.com/security/alertmanager/cvss\n\n\n* NP 2 threads lock due to processing crafted ICMP message (CSCsz97207)\n\nCVSS Base Score - 7.8\n Access Vector - Network\n Access Complexity - Low\n Authentication - None\n Confidentiality Impact - None\n Integrity Impact - None\n Availability Impact - Complete\n\nCVSS Temporal Score - 6.4\n Exploitability - Functional\n Remediation Level - Official-Fix\n Report Confidence - Confirmed\n\n\nImpact\n======\n\nSuccessful exploitation of the vulnerability may cause the FWSM to\nstop forwarding traffic between interfaces (transit traffic), and stop\nprocessing traffic directed at the FWSM (management traffic). If the\nFWSM is configured for failover operation, the active FWSM may not fail\nover to the standby FWSM. \n\nSoftware Versions and Fixes\n===========================\n\nWhen considering software upgrades, also consult\nhttp://www.cisco.com/go/psirt and any subsequent advisories to determine\nexposure and a complete upgrade solution. \n\nIn all cases, customers should exercise caution to be certain the\ndevices to be upgraded contain sufficient memory and that current\nhardware and software configurations will continue to be supported\nproperly by the new release. If the information is not clear, contact\nthe Cisco Technical Assistance Center (TAC) or your contracted\nmaintenance provider for assistance. \n\nEach row of the FWSM software table below describes a major FWSM\nsoftware train and the earliest possible release within that train that\ncontains the fix (the \"First Fixed Release\") and the anticipated date of\navailability (if not currently available) in the \"First Fixed Release\"\ncolumn. A device running a release that is earlier than the release in\na specific column (less than the First Fixed Release) is known to be\nvulnerable. The release should be upgraded at least to the indicated\nrelease or a later version (greater than or equal to the First Fixed\nRelease label). \n\n+---------------------------------------+\n| Major | First Fixed Release |\n| Release | |\n|------------+--------------------------|\n| 2.x | Vulnerable; migrate to |\n| | 3.x or 4.x |\n|------------+--------------------------|\n| 3.1 | 3.1(16) |\n|------------+--------------------------|\n| 3.2 | 3.2(13) |\n|------------+--------------------------|\n| 4.0 | 4.0(6) |\n+---------------------------------------+\n\nFixed FWSM software can be downloaded from the Software Center on\ncisco.com by visiting http://www.cisco.com/public/sw-center/index.shtml\nand navigating to \"Security\" \u003e \"Cisco Catalyst 6500 Series Firewall\nServices Module\" \u003e \"Firewall Services Module (FWSM) Software\". \n\nWorkarounds\n===========\n\nThere are no workarounds for this vulnerability. Access control lists\n(ACLs) that are deployed on the FWSM itself to block through-the-device\nor to-the-device ICMP messages are not effective to prevent this\nvulnerability. However, blocking unnecessary ICMP messages on screening\ndevices or on devices in the path to the FWSM will prevent the FWSM\nfrom triggering the vulnerability. For example, the following ACL,\nwhen deployed on a Cisco IOS device in front of the FWSM, will prevent\ncrafted ICMP messages from reaching the FWSM, and thus protect the FWSM\nfrom triggering the vulnerability:\n\n access-list 101 permit icmp any any echo\n access-list 101 permit icmp any any echo-reply\n access-list 101 permit icmp any any traceroute\n access-list 101 permit icmp any any packet-too-big\n access-list 101 permit icmp any any time-exceeded\n access-list 101 permit icmp any any host-unreachable\n access-list 101 permit icmp any any unreachable\n access-list 101 deny icmp any any\n access-list 101 permit ip any any\n\nThis sample ACL is allowing certain ICMP messages that are vital for\nnetwork troubleshooting and for proper operation of the network. It is\nsafe to allow any other ICMP messages for which the Cisco IOS Software\n\"access-list\" command has named ICMP type keywords. ACLs like the one\nin the preceding example may also be deployed on non-Cisco IOS devices,\nsuch as the Cisco PIX and ASA security appliances, although the ACL\nsyntax on non-Cisco IOS devices may not support all the named ICMP type\nkeywords that the Cisco IOS ACL syntax supports. However, on non-Cisco\nIOS devices, it is safe to permit all ICMP messages for which there are\nnamed ICMP type keywords in the ACL syntax. \n\nAs mentioned in the Details section, if the FWSM has stopped processing\ntraffic due to this vulnerability, the FWSM will require a reload. \n\nAdditional mitigations that can be deployed on Cisco devices within the\nnetwork are available in the Cisco Applied Mitigation Bulletin companion\ndocument for this advisory, which is available at the following link:\n\nhttp://www.cisco.com/warp/public/707/cisco-amb-20090819-fwsm.shtml. \n\nObtaining Fixed Software\n========================\n\nCisco has released free software updates that address this\nvulnerability. Prior to deploying software, customers should consult\ntheir maintenance provider or check the software for feature set\ncompatibility and known issues specific to their environment. \n\nCustomers may only install and expect support for the feature\nsets they have purchased. By installing, downloading, accessing\nor otherwise using such software upgrades, customers agree to be\nbound by the terms of Cisco\u0027s software license terms found at\nhttp://www.cisco.com/en/US/docs/general/warranty/English/EU1KEN_.html,\nor as otherwise set forth at Cisco.com Downloads at\nhttp://www.cisco.com/public/sw-center/sw-usingswc.shtml. \n\nDo not contact psirt@cisco.com or security-alert@cisco.com for software\nupgrades. \n\nCustomers with Service Contracts\n- --------------------------------\n\nCustomers with contracts should obtain upgraded software through their\nregular update channels. For most customers, this means that upgrades\nshould be obtained through the Software Center on Cisco\u0027s worldwide\nwebsite at http://www.cisco.com. \n\nCustomers using Third Party Support Organizations\n- -------------------------------------------------\n\nCustomers whose Cisco products are provided or maintained through prior\nor existing agreements with third-party support organizations, such\nas Cisco Partners, authorized resellers, or service providers should\ncontact that support organization for guidance and assistance with the\nappropriate course of action in regards to this advisory. \n\nThe effectiveness of any workaround or fix is dependent on specific\ncustomer situations, such as product mix, network topology, traffic\nbehavior, and organizational mission. Due to the variety of affected\nproducts and releases, customers should consult with their service\nprovider or support organization to ensure any applied workaround or fix\nis the most appropriate for use in the intended network before it is\ndeployed. \n\nCustomers without Service Contracts\n- -----------------------------------\n\nCustomers who purchase direct from Cisco but do not hold a Cisco service\ncontract, and customers who purchase through third-party vendors but are\nunsuccessful in obtaining fixed software through their point of sale\nshould acquire upgrades by contacting the Cisco Technical Assistance\nCenter (TAC). TAC contacts are as follows. \n\n * +1 800 553 2447 (toll free from within North America)\n * +1 408 526 7209 (toll call from anywhere in the world)\n * e-mail: tac@cisco.com\n\nCustomers should have their product serial number available and be\nprepared to give the URL of this notice as evidence of entitlement to a\nfree upgrade. Free upgrades for non-contract customers must be requested\nthrough the TAC. \n\nRefer to\nhttp://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html\nfor additional TAC contact information, including localized telephone\nnumbers, and instructions and e-mail addresses for use in various\nlanguages. \n\nExploitation and Public Announcements\n=====================================\n\nThe Cisco PSIRT is not aware of any public announcements or malicious\nuse of the vulnerability described in this advisory, but Cisco is aware\nof customers that have encountered this vulnerability during normal\nnetwork operation. \n\nThis vulnerability was discovered during the handling of customer\nsupport cases. \n\nStatus of this Notice: FINAL\n============================\n\nTHIS DOCUMENT IS PROVIDED ON AN \"AS IS\" BASIS AND DOES NOT IMPLY\nANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTIES OF\nMERCHANTABILITY OR FITNESS FOR A PARTICULAR USE. YOUR USE OF THE\nINFORMATION ON THE DOCUMENT OR MATERIALS LINKED FROM THE DOCUMENT IS\nAT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS\nDOCUMENT AT ANY TIME. \n\nA stand-alone copy or Paraphrase of the text of this document that omits\nthe distribution URL in the following section is an uncontrolled copy,\nand may lack important information or contain factual errors. \n\nDistribution\n============\n\nThis advisory is posted on Cisco\u0027s worldwide website at:\n\nhttp://www.cisco.com/warp/public/707/cisco-sa-20090819-fwsm.shtml\n\nIn addition to worldwide web posting, a text version of this notice is\nclear-signed with the Cisco PSIRT PGP key and is posted to the following\ne-mail and Usenet news recipients. \n\n * cust-security-announce@cisco.com\n * first-bulletins@lists.first.org\n * bugtraq@securityfocus.com\n * vulnwatch@vulnwatch.org\n * cisco@spot.colorado.edu\n * cisco-nsp@puck.nether.net\n * full-disclosure@lists.grok.org.uk\n * comp.dcom.sys.cisco@newsgate.cisco.com\n\nFuture updates of this advisory, if any, will be placed on Cisco\u0027s\nworldwide website, but may or may not be actively announced on mailing\nlists or newsgroups. Users concerned about this problem are encouraged\nto check the above URL for any updates. \n\nRevision History\n================\n\n+------------------------------------------------------------+\n| Revision 1.0 | 2009-August-19 | Initial public release |\n+------------------------------------------------------------+\n\nCisco Security Procedures\n=========================\n\nComplete information on reporting security vulnerabilities\nin Cisco products, obtaining assistance with security\nincidents, and registering to receive security information\nfrom Cisco, is available on Cisco\u0027s worldwide website at\nhttp://www.cisco.com/en/US/products/products_security_vulnerability_policy.html\n. \nThis includes instructions for press inquiries regarding\nCisco security notices. All Cisco security advisories are available at\nhttp://www.cisco.com/go/psirt. \n\n+--------------------------------------------------------------------\nCopyright 2008-2009 Cisco Systems, Inc. All rights reserved. \n+--------------------------------------------------------------------\n\nUpdated: Aug 19, 2009 Document ID: 110460\n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v1.4.9 (GNU/Linux)\n\niEYEARECAAYFAkqMMFYACgkQ86n/Gc8U/uA2jACeLVA38jWbQv4AGpSCvOPVJjgR\nNqUAniMoiEUkV/JIDlo1xA0ztaO6jCFR\n=2Tm1\n-----END PGP SIGNATURE-----\n",
"sources": [
{
"db": "NVD",
"id": "CVE-2009-0638"
},
{
"db": "JVNDB",
"id": "JVNDB-2009-002659"
},
{
"db": "BID",
"id": "36085"
},
{
"db": "VULHUB",
"id": "VHN-38084"
},
{
"db": "PACKETSTORM",
"id": "80812"
},
{
"db": "PACKETSTORM",
"id": "80521"
}
],
"trust": 2.16
},
"exploit_availability": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/exploit_availability#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"reference": "https://www.scap.org.cn/vuln/vhn-38084",
"trust": 0.1,
"type": "unknown"
}
],
"sources": [
{
"db": "VULHUB",
"id": "VHN-38084"
}
]
},
"external_ids": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/external_ids#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"db": "NVD",
"id": "CVE-2009-0638",
"trust": 2.9
},
{
"db": "BID",
"id": "36085",
"trust": 2.8
},
{
"db": "SECUNIA",
"id": "36373",
"trust": 2.6
},
{
"db": "SECTRACK",
"id": "1022747",
"trust": 2.5
},
{
"db": "VUPEN",
"id": "ADV-2009-2329",
"trust": 1.7
},
{
"db": "XF",
"id": "52591",
"trust": 1.4
},
{
"db": "JVNDB",
"id": "JVNDB-2009-002659",
"trust": 0.8
},
{
"db": "CISCO",
"id": "20090819 FIREWALL SERVICES MODULE CRAFTED ICMP MESSAGE VULNERABILITY",
"trust": 0.6
},
{
"db": "CNNVD",
"id": "CNNVD-200908-296",
"trust": 0.6
},
{
"db": "PACKETSTORM",
"id": "80521",
"trust": 0.2
},
{
"db": "VULHUB",
"id": "VHN-38084",
"trust": 0.1
},
{
"db": "PACKETSTORM",
"id": "80812",
"trust": 0.1
}
],
"sources": [
{
"db": "VULHUB",
"id": "VHN-38084"
},
{
"db": "BID",
"id": "36085"
},
{
"db": "JVNDB",
"id": "JVNDB-2009-002659"
},
{
"db": "PACKETSTORM",
"id": "80812"
},
{
"db": "PACKETSTORM",
"id": "80521"
},
{
"db": "CNNVD",
"id": "CNNVD-200908-296"
},
{
"db": "NVD",
"id": "CVE-2009-0638"
}
]
},
"id": "VAR-200908-0248",
"iot": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/iot#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": true,
"sources": [
{
"db": "VULHUB",
"id": "VHN-38084"
}
],
"trust": 0.01
},
"last_update_date": "2024-11-23T19:30:59.017000Z",
"patch": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/patch#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"title": "cisco-sa-20090819-fwsm",
"trust": 0.8,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20090819-fwsm.shtml"
}
],
"sources": [
{
"db": "JVNDB",
"id": "JVNDB-2009-002659"
}
]
},
"problemtype_data": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/problemtype_data#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"problemtype": "NVD-CWE-Other",
"trust": 1.0
},
{
"problemtype": "CWE-Other",
"trust": 0.8
}
],
"sources": [
{
"db": "JVNDB",
"id": "JVNDB-2009-002659"
},
{
"db": "NVD",
"id": "CVE-2009-0638"
}
]
},
"references": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/references#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"trust": 2.5,
"url": "http://www.securityfocus.com/bid/36085"
},
{
"trust": 2.5,
"url": "http://securitytracker.com/id?1022747"
},
{
"trust": 2.5,
"url": "http://secunia.com/advisories/36373"
},
{
"trust": 2.1,
"url": "http://www.cisco.com/en/us/products/products_security_advisory09186a0080af0d1d.shtml"
},
{
"trust": 1.7,
"url": "http://www.vupen.com/english/advisories/2009/2329"
},
{
"trust": 1.4,
"url": "http://xforce.iss.net/xforce/xfdb/52591"
},
{
"trust": 1.1,
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/52591"
},
{
"trust": 0.8,
"url": "http://cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2009-0638"
},
{
"trust": 0.8,
"url": "http://web.nvd.nist.gov/view/vuln/detail?vulnid=cve-2009-0638"
},
{
"trust": 0.4,
"url": "http://www.cisco.com/en/us/products/products_applied_mitigation_bulletin09186a0080af151c.html"
},
{
"trust": 0.3,
"url": "http://www.cisco.com/en/us/products/hw/modules/ps2706/ps4452/"
},
{
"trust": 0.3,
"url": "/archive/1/505926"
},
{
"trust": 0.1,
"url": "http://secunia.com/advisories/36373/"
},
{
"trust": 0.1,
"url": "http://secunia.com/advisories/secunia_security_advisories/"
},
{
"trust": 0.1,
"url": "http://secunia.com/advisories/business_solutions/"
},
{
"trust": 0.1,
"url": "http://secunia.com/sec_adv_unsubscribe/?email=packet%40packetstormsecurity.org"
},
{
"trust": 0.1,
"url": "http://secunia.com/advisories/about_secunia_advisories/"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/go/psirt"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20090819-fwsm.shtml"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/en/us/support/tsd_cisco_worldwide_contacts.html"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/en/us/products/products_security_vulnerability_policy.html"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/public/sw-center/index.shtml"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/web/about/security/intelligence/cvss-qandas.html"
},
{
"trust": 0.1,
"url": "https://nvd.nist.gov/vuln/detail/cve-2009-0638"
},
{
"trust": 0.1,
"url": "http://www.cisco.com."
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20090819-fwsm.shtml."
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/public/707/cisco-amb-20090819-fwsm.shtml."
},
{
"trust": 0.1,
"url": "http://www.cisco.com/go/psirt."
},
{
"trust": 0.1,
"url": "http://www.cisco.com/en/us/docs/general/warranty/english/eu1ken_.html,"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/public/sw-center/sw-usingswc.shtml."
},
{
"trust": 0.1,
"url": "http://intellishield.cisco.com/security/alertmanager/cvss"
}
],
"sources": [
{
"db": "VULHUB",
"id": "VHN-38084"
},
{
"db": "BID",
"id": "36085"
},
{
"db": "JVNDB",
"id": "JVNDB-2009-002659"
},
{
"db": "PACKETSTORM",
"id": "80812"
},
{
"db": "PACKETSTORM",
"id": "80521"
},
{
"db": "CNNVD",
"id": "CNNVD-200908-296"
},
{
"db": "NVD",
"id": "CVE-2009-0638"
}
]
},
"sources": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#",
"data": {
"@container": "@list"
}
},
"data": [
{
"db": "VULHUB",
"id": "VHN-38084"
},
{
"db": "BID",
"id": "36085"
},
{
"db": "JVNDB",
"id": "JVNDB-2009-002659"
},
{
"db": "PACKETSTORM",
"id": "80812"
},
{
"db": "PACKETSTORM",
"id": "80521"
},
{
"db": "CNNVD",
"id": "CNNVD-200908-296"
},
{
"db": "NVD",
"id": "CVE-2009-0638"
}
]
},
"sources_release_date": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources_release_date#",
"data": {
"@container": "@list"
}
},
"data": [
{
"date": "2009-08-21T00:00:00",
"db": "VULHUB",
"id": "VHN-38084"
},
{
"date": "2009-08-19T00:00:00",
"db": "BID",
"id": "36085"
},
{
"date": "2011-06-08T00:00:00",
"db": "JVNDB",
"id": "JVNDB-2009-002659"
},
{
"date": "2009-09-01T12:31:24",
"db": "PACKETSTORM",
"id": "80812"
},
{
"date": "2009-08-23T15:52:12",
"db": "PACKETSTORM",
"id": "80521"
},
{
"date": "2009-08-21T00:00:00",
"db": "CNNVD",
"id": "CNNVD-200908-296"
},
{
"date": "2009-08-21T11:02:41.640000",
"db": "NVD",
"id": "CVE-2009-0638"
}
]
},
"sources_update_date": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources_update_date#",
"data": {
"@container": "@list"
}
},
"data": [
{
"date": "2017-08-17T00:00:00",
"db": "VULHUB",
"id": "VHN-38084"
},
{
"date": "2009-08-21T15:54:00",
"db": "BID",
"id": "36085"
},
{
"date": "2011-06-08T00:00:00",
"db": "JVNDB",
"id": "JVNDB-2009-002659"
},
{
"date": "2009-08-26T00:00:00",
"db": "CNNVD",
"id": "CNNVD-200908-296"
},
{
"date": "2024-11-21T01:00:34.850000",
"db": "NVD",
"id": "CVE-2009-0638"
}
]
},
"threat_type": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/threat_type#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "remote",
"sources": [
{
"db": "CNNVD",
"id": "CNNVD-200908-296"
}
],
"trust": 0.6
},
"title": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/title#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "Cisco Firewall Services Module Service disruption in (DoS) Vulnerabilities",
"sources": [
{
"db": "JVNDB",
"id": "JVNDB-2009-002659"
}
],
"trust": 0.8
},
"type": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/type#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "other",
"sources": [
{
"db": "CNNVD",
"id": "CNNVD-200908-296"
}
],
"trust": 0.6
}
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.