var-200705-0570
Vulnerability from variot
The RSA Crypto-C before 6.3.1 and Cert-C before 2.8 libraries, as used by RSA BSAFE, multiple Cisco products, and other products, allows remote attackers to cause a denial of service via malformed ASN.1 objects. The RSA BSAFE Crypto-C and Cert-C libraries contain a denial-of-service vulnerability. RSA Security provides RSA BSAFE Cert-C and Crypto-C For implementing digital certificate processing and cryptographic algorithms respectively C/C++ A library for languages. RSA BSAFE Cert-C and Crypto-C Crafted by ASN.1 There is a problem with object processing, and there is a problem that the library falls into an infinite loop.Service operation disrupted by a remote third party (DoS) There is a possibility of being attacked. Exploiting this vulnerability allows attackers to crash applications that use the affected library. The specific impact of this vulnerability depends on the nature of the applications. Local and remote attacks may be possible. Depending on the nature of vulnerable applications, attackers may be able to exploit this issue without authentication. These versions are vulnerable: RSA BSAFE Crypto-C prior to 6.3.1 Cert-C prior to 2.8 The vendor tracks this issue by RSA Bug ID 46337. Cisco tracks this issue as Bug IDs: Cisco IOS: CSCsd85587 Cisco IOS XR: CSCsg41084 Cisco PIX and ASA Security Appliances: CSCse91999 Cisco Firewall Services Module (FWSM): CSCsi97695 Cisco Unified CallManager: CSCsg44348. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Cisco Security Advisory: Vulnerability In Crypto Library
Advisory ID: cisco-sa-20070522-crypto.shtml
http://www.cisco.com/warp/public/707/cisco-sa-20070522-crypto.shtml
Revision 1.0
For Public Release 2007 May 22 1300 UTC (GMT)
Summary
A vulnerability has been discovered in a third party cryptographic library which is used by a number of Cisco products. This vulnerability may be triggered when a malformed Abstract Syntax Notation One (ASN.1) object is parsed. Due to the nature of the vulnerability it may be possible, in some cases, to trigger this vulnerability without a valid certificate or valid application-layer credentials (such as a valid username or password).
Successful repeated exploitation of any of these vulnerabilities may lead to a sustained Denial-of-Service (DoS); however, vulnerabilities are not known to compromise either the confidentiality or integrity of the data or the device. These vulnerabilities are not believed to allow an attacker will not be able to decrypt any previusly encrypted information. It is externally coordinated and is tracked by the following external coordinators:
- JPCERT/CC - tracked as JVNVU#754281
- CPNI - tracked as NISCC-362917
- CERT/CC - tracked as VU#754281
Cisco has made free software available to address this vulnerability for affected customers. There are no workarounds available to mitigate the effects of the vulnerability.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070522-crypto.shtml.
Note: Another related advisory is posted together with this Advisory. It also describes vulnerabilities related to cryptography that affect Cisco IOS. A combined software table for Cisco IOS only is available at http://www.cisco.com /warp/public/707/cisco-sa-20070522-cry-bundle.shtml and can be used to choose a software release which fixes all security vulnerabilities published as of May 22, 2007. It is sufficient that only one protocol or feature is enabled in order for a devices to be vulnerable. In order to be not vulnerable, all of the listed application protocols or features must be disabled.
Affected protocols in Cisco IOS +------------------------------
To determine the software running on a Cisco IOS product, log in to the device and issue the "show version" command to display the system banner. Cisco IOS software will identify itself as "Internetwork Operating System Software" or simply "IOS." On the next line of output, the image name will be displayed between parentheses, followed by "Version" and the Cisco IOS release name. Other Cisco devices will not have the "show version" command, or will give different output.
Only Cisco IOS images that contain the Crypto Feature Set are vulnerable. Customers who are not running an IOS image with crypto support are not exposed to this vulnerability.
Cisco IOS feature set naming indicates that IOS images with crypto support have 'K8' or 'K9' in the feature designator field.
The following example shows output from a device running an IOS image with crypto support:
Router>show version
Cisco IOS Software, 7200 Software (C7200-IK9S-M), Version 12.3(14)T1, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2005 by Cisco Systems, Inc.
Compiled Thu 31-Mar-05 08:04 by yiyan
Since the feature set designator (IK9S) contains 'K9', it can be determine that this feature set contains crypto support.
Additional information about Cisco IOS release naming is available at the following link: http://www.cisco.com/en/US/products/sw/iosswrel/ps1828/products_white_paper09186a008018305e.shtml.
You are affected by this vulnerability if you are running one of the vulnerable IOS software releases and have, at least one, of the following protocols or features enabled:
- Internet Security Association and Key Management Protocol (ISAKMP)
- In some IOS releases the Secure Socket Layer (SSL) may also be affected
- Threat Information Distribution Protocol (TIDP)
- Cisco IOS SIP Gateway Signaling Support Over TLS (SIP-TLS)
- Extensible Authentication Protocol-Transport Layer Security (EAP-TLS)
As some other protocols may use affected crypto library the most accurate way to determine if your IOS release is vulnerable is to consult fixed IOS releases table.
Internet Security Association and Key Management Protocol (ISAKMP) +-----------------------------------------------------------------
To determine if your device has ISAKMP enabled, enter the command "show crypto isakmp policy". Below is an example of a device that has ISAKMP enabled.
Router#show crypto isakmp policy
Global IKE policy
Protection suite of priority 1
<more output>
If your output is like in the following example then you do not have IKE enabled on your device.
Router#show crypto isakmp policy
ISAKMP is turned off
In Cisco IOS two features rely on ISAKMP - IPSec and Group Domain of Interpretation (GDOI). Presence of either of these features is detected by the previous example.
Prior to IOS version 12.3(8)T, IKE was enabled by default, with no crypto configuration needed for the IOS device to process IKE messages.
12.2SXD versions of Cisco IOS have IKE enabled by default. To ensure that IKE processing is disabled, enter the global configuration command "no crypto isakmp enable".
As of IOS version 12.3(2)T (which includes all 12.4-based versions), crypto configuration is required to enable IKE message processing.
In order for an IOS device to be vulnerable crypto map must be explicilty configured and applied to an interface.
Secure Socket Layer (SSL) +------------------------
In some Cisco IOS software releases the vulnerable library is used to process elements of SSL functionalities. SSL is used to protect several application layer protocols like Hyper Text Transfer Protocol over SSL (HTTPS).
HTTPS is not the only protocol that may use SSL but it is the most commonly known. In order to determine if your device has HTTPS configured enter the command "show running | include secure". Below is an example of a device that has HTTPS enabled.
router#show running | include secure-server
ip http secure-server
Threat Information Distribution Protocol (TIDP) +----------------------------------------------
To determine if your device has TDIP enabled, enter the command "show running-config | include parameter-map". Below is an example of a device that has TDIP enabled.
router#show running | include parameter-map
parameter-map type tms TMS_PAR
Cisco IOS SIP Gateway Signaling Support Over TLS (SIP-TLS) +---------------------------------------------------------
To determine if your device has SIP-TLS enabled, enter the command "show running-config | include crypto signaling". Below is an example of a device that has SIP-TLS enabled.
router#show running | include crypto signaling
crypto signaling default trustpoint user1
Extensible Authentication Protocol-Transport Layer Security (EAP-TLS) +--------------------------------------------------------------------
To determine if your device has EAP-TLS enabled, enter the command "show running-config | include method". Below is an example of a device that has EAP-TLS enabled.
Router#show running | include method
method tls
Affected protocols in Cisco IOS XR +---------------------------------
You are affected by this vulnerability if you are running one of the vulnerable Cisco IOS XR software releases and have, at least one, of the following protocols or features enabled:
- Internet Security Association and Key Management Protocol (ISAKMP)
- In some IOS XR releases the Secure Socket Layer (SSL) may also be affected
- Secure Shell (SSH)
Internet Security Association and Key Management Protocol (ISAKMP) +-----------------------------------------------------------------
To determine if your device has ISAKMP enabled, enter the command "show running-config | include isakmp". Below is an example of a device that has IKE enabled.
Router#show running-config | include isakmp
crypto isakmp
crypto isakmp policy 1
crypto isakmp profile profile-a
Secure Socket Layer (SSL) +------------------------
SSL is used to provide secure communications to the application layer protocols like Hyper Text Transfer Protocol over SSL (HTTPS) and Object Request Brokers (ORB). To determine if your device has any service enabled that uses SSL, enter one of the following commands "show running-config | include http server ssl" or "show running-config | include xml agent corba ssl". Below is an example of a device that has both of the services enabled.
Router#show running-config | include http server ssl
http server ssl
Router#show running-config | include xml agent corba ssl
xml agent corba ssl
Secure Shell (SSH) +-----------------
SSH is an application and a protocol that provides secure replacement for the suite of Berkeley r-tools such as rsh, rlogin and rcp. It is highly prefered over Telnet for interactive sessions. To determine if your device has SSH enabled enter the command "show running-config | include ssh server". Below is an example of a device that has SSH enabled.
Router#show running-config | include ssh server
ssh server
ssh server rate-limit 100
Affected protocols in Cisco PIX and ASA Security Appliances +----------------------------------------------------------
You are affected by this vulnerability if you are running one of the vulnerable Cisco PIX and ASA software releases and have, at least one, of the following protocols or features enabled:
- Secure Shell (SSH)
- Internet Security Association and Key Management Protocol (ISAKMP)
- Secure Socket Layer (SSL)
Secure Shell (SSH) +-----------------
To determine if a device has SSH enabled, enter the command "show running" and observe the output. If it contains the line as in the following example then SSH is enabled.
PIX#show running
....
ssh <host_IP_address> <host_netmask> <interface>
....
Internet Security Association and Key Management Protocol (ISAKMP) +-----------------------------------------------------------------
To determine if a device has ISAKMP enabled, enter the command "show running" and observe the output. If it contains the lines as in the following example then ISAKMP is enabled.
PIX#show running
....
crypto isakmp policy 2
authentication rsa-sig
....
Secure Socket Layer (SSL) +------------------------
SSL is used to protect several application layer protocols like Hyper Text Transfer Protocol over SSL (HTTPS) and Cisco Adaptive Security Device Manager (ASDM) session.
To determine if a device has SSL enabled, enter the command "show running" and observe the output. If it contains the line as in the following example then SSL is enabled.
PIX#show running
....
http server enable
....
Affected protocols in Cisco Unified CallManager +----------------------------------------------
You are affected by this vulnerability if you are running one of the vulnerable Cisco Unified CallManager software releases and have, at least one, of the following protocols or features enabled:
- Certificate Authority Proxy Function (CAPF)
- Cisco TAPI Service Provider (Cisco Unified CallManager TSP)
Certificate Authority Proxy Function (CAPF) +------------------------------------------
CAPF is automatically installed with Cisco CallManager but is disabled by default. In order to verify if CAPF is enabled on your Unified CallManager do the following steps.
- Step 1 - In Cisco CallManager Administration, choose Service > Service Parameter.
- Step 2 - If you are running 4.x software then do the following: from the Server drop-down list box, choose the publisher database server. If you are running 5.x software then do the following: From the Server drop-down list box, choose the first node.
- Step 3 - From the Service drop-down list box, choose the Cisco Certificate Authority Proxy Function service.
If you are given CAPF parameters then CAPF is running on your system.
Cisco TAPI Service Provider (Cisco Unified CallManager TSP) +----------------------------------------------------------
In order to determine if Cisco Unified CallManager TSP is installed open Windows Control Panel (Start > Control Panel) and click on Add/Remove Programs. If 'Cisco Unity-CM TSP' is listed then you have it installed on your system.
Products Confirmed Not Vulnerable +--------------------------------
No other Cisco products are currently known to be affected by this vulnerability. Specifically, the following product's features or products are known not to be affected:
- Cisco IOS
- Secure Shell (SSH)
- Secure Copy (SCP)
- Cisco Unified Call Manager
- Hyper Text Transfer Protocol over SSL (HTTPS)
- Cisco Unified CallManager is configured for Secure Survivable Remote Site Telephony (SRST)
- MeetingPlace Express and MeetingPlace for Telepresence
- Cisco IP Communicator
- All Cisco Unified IP Phones 7900 Series
- CIP TN3270 Server
- Cisco GSS 4400 Series Global Site Selector Appliances
- Cisco CatOS
The list is not exhaustive.
Details
ASN.1 is defined by ITU-T (International Telecommunication Union - Telecommunication Standardization Sector) standards and it describes, among other things, data structures for encoding values. The vulnerability addressed by this advisory is related to the implementation of parsing certain data structures and is not a vulnerability in the standard itself.
Protocols that use ASN.1 (e.g., voice over IP, Simple Network Management Protocol and others), but do not rely on the vulnerable crypto library, are not affected. This advisory only addresses an implementation issue in a particular crypto library from a single vendor.
Cisco will provide a base and temporal score. Customers can then compute environmental scores to assist in determining the impact of the vulnerability in individual networks.
Cisco PSIRT will set the bias in all cases to normal. Customers are encouraged to apply the bias parameter when determining the environmental impact of a particular vulnerability.
CVSS is a standards based scoring method that conveys vulnerability severity and helps determine urgency and priority of response.
Cisco has provided an 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.
Cisco Bug IDs:
CSCsd85587 - Router crashes when processing ISAKMP message
CVSS Base Score: 3.3 Access Vector: Remote Access Complexity: Low Authentication: Not Required Confidentiality Impact: None Integrity Impact: None Availability Impact: Complete Impact Bias: Normal
CVSS Temporal Score: 2.7 Exploitability: Functional Remediation Level: Official Fix Report Confidence: Confirmed
CSCsg41084 - IOS XR crashes when processing ISAKMP message
CVSS Base Score: 3.3 Access Vector: Remote Access Complexity: Low Authentication: Not Required Confidentiality Impact: None Integrity Impact: None Availability Impact: Complete Impact Bias: Normal
CVSS Temporal Score: 2.7 Exploitability: Functional Remediation Level: Official Fix Report Confidence: Confirmed
CSCse91999 - PIX/ASA crashes when processing ISAKMP message
CVSS Base Score: 3.3 Access Vector: Remote Access Complexity: Low Authentication: Not Required Confidentiality Impact: None Integrity Impact: None Availability Impact: Complete Impact Bias: Normal
CVSS Temporal Score: 2.7 Exploitability: Functional Remediation Level: Official Fix Report Confidence: Confirmed
CSCsg44348 - Unified CallManager crashes when processing crypto message
CVSS Base Score: 3.3 Access Vector: Remote Access Complexity: Low Authentication: Not Required Confidentiality Impact: None Integrity Impact: None Availability Impact: Complete Impact Bias: Normal
CVSS Temporal Score: 2.7 Exploitability: Functional Remediation Level: Official Fix Report Confidence: Confirmed
Impact
Successful exploitation of the vulnerability listed in this advisory may result in the crash of a vulnerable device. Repeated exploitation can result in a sustained DoS attack.
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 Cisco IOS software table (below) describes a release train. If a given release train is vulnerable, then the earliest possible releases that contain the fix (the "First Fixed Release") and the anticipated date of availability for each are listed in the "Rebuild" and "Maintenance" columns. A device running a release in the given train 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).
For more information on the terms "Rebuild" and "Maintenance," consult the following URL: http://www.cisco.com/en/US/products/sw/iosswrel/ps1828/products_white_paper09186a008018305e.shtml
Cisco IOS +--------
Fixed Cisco IOS software releases are listed in the table below.
+-----------------------------------------------------------------------------+ | Major Release | Availability of Repaired Releases | |------------------------------+----------------------------------------------| | Affected 12.2-Based Release | Rebuild | Maintenance | |------------------------------+----------------------------------------------| | 12.2B | Vulnerable; migrate to 12.4(10) or later | |------------------------------+----------------------------------------------| | 12.2BC | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.2BZ | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.2CX | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.2CZ | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.2EW | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.2EWA | 12.2(25)EWA9 | | |------------------------------+----------------------------------------------| | 12.2EX | Vulnerable; migrate to 12.2(25)SEE3 or later | |------------------------------+----------------------------------------------| | 12.2EY | Vulnerable; migrate to 12.2(25)SEE3 or later | |------------------------------+----------------------------------------------| | 12.2EZ | Vulnerable; migrate to 12.2(25)SEE3 or later | |------------------------------+----------------------------------------------| | 12.2FX | Vulnerable; migrate to 12.2(25)SEE3 or later | |------------------------------+----------------------------------------------| | 12.2FY | Vulnerable; migrate to 12.2(35)SE2 or later | |------------------------------+----------------------------------------------| | 12.2FZ | Vulnerable; migrate to 12.2(35)SE2 or later | |------------------------------+----------------------------------------------| | 12.2IXA | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.2IXB | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.2IXC | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.2JA | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.2JK | Vulnerable; migrate to 12.4(6)T7 or later | |------------------------------+----------------------------------------------| | 12.2SB | 12.2(31)SB3 | | |------------------------------+---------------------+------------------------| | 12.2SE | 12.2(35)SE2 | | |------------------------------+----------------------------------------------| | 12.2SEA | Vulnerable; migrate to 12.2(25)SEE3 or later | |------------------------------+----------------------------------------------| | 12.2SEB | Vulnerable; migrate to 12.2(25)SEE3 or later | |------------------------------+----------------------------------------------| | 12.2SEC | Vulnerable; migrate to 12.2(25)SEE3 or later | |------------------------------+----------------------------------------------| | 12.2SED | Vulnerable; migrate to 12.2(25)SEE3 or later | |------------------------------+----------------------------------------------| | 12.2SEE | 12.2(25)SEE3 | | |------------------------------+----------------------------------------------| | 12.2SEF | Vulnerable; migrate to 12.2(35)SE2 or later | |------------------------------+----------------------------------------------| | 12.2SEG | Vulnerable; migrate to 12.2(35)SE2 or later | |------------------------------+----------------------------------------------| | 12.2SG | | 12.2(37)SG | |------------------------------+---------------------+------------------------| | 12.2SGA | 12.2(31)SGA1 | | |------------------------------+---------------------+------------------------| | 12.2SRA | 12.2(33)SRA3 | | |------------------------------+---------------------+------------------------| | 12.2SRB | | 12.2(33)SRB | |------------------------------+----------------------------------------------| | 12.2SXD | Vulnerable; migrate to 12.2(18)SXF8 or later | |------------------------------+----------------------------------------------| | 12.2SXE | Vulnerable; migrate to 12.2(18)SXF8 or later | |------------------------------+----------------------------------------------| | 12.2SXF | 12.2(18)SXF8 | | |------------------------------+----------------------------------------------| | 12.2T | Vulnerable; migrate to 12.3(22) or later | |------------------------------+----------------------------------------------| | 12.2XR | Vulnerable; migrate to 12.3(22) or later | |------------------------------+----------------------------------------------| | 12.2YU | Vulnerable; migrate to 12.4(10) or later | |------------------------------+----------------------------------------------| | 12.2YV | Vulnerable; migrate to 12.4(10) or later | |------------------------------+----------------------------------------------| | 12.2ZD | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.2ZE | Vulnerable; migrate to 12.3(22) or later | |------------------------------+----------------------------------------------| | 12.2ZF | Vulnerable; migrate to 12.4(10) or later | |------------------------------+----------------------------------------------| | 12.2ZG | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.2ZH | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.2ZJ | Vulnerable; migrate to 12.4(10) or later | |------------------------------+----------------------------------------------| | 12.2ZL | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.2ZU | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.2ZW | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | Affected 12.3-Based Release | Rebuild | Maintenance | |------------------------------+---------------------+------------------------| | 12.3 | | 12.3(22) | |------------------------------+----------------------------------------------| | 12.3B | Vulnerable; migrate to 12.4(10) or later | |------------------------------+----------------------------------------------| | 12.3BC | 12.3(17b)BC6 | | |------------------------------+----------------------------------------------| | 12.3JA | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.3JEA | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.3JK | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.3JL | 12.3(2)JL1 | | |------------------------------+----------------------------------------------| | 12.3JX | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.3T | Vulnerable; migrate to 12.4(10) or later | |------------------------------+----------------------------------------------| | 12.3TPC | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.3XA | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.3XB | Vulnerable; migrate to 12.4(10) or later | |------------------------------+----------------------------------------------| | 12.3XC | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.3XD | Vulnerable; migrate to 12.4(10) or later | |------------------------------+----------------------------------------------| | 12.3XE | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.3XF | Vulnerable; migrate to 12.4(10) or later | |------------------------------+----------------------------------------------| | 12.3XG | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.3XH | Vulnerable; migrate to 12.4(10) or later | |------------------------------+----------------------------------------------| | 12.3XI | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.3XJ | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.3XK | Vulnerable; migrate to 12.4(10) or later | |------------------------------+----------------------------------------------| | 12.3XQ | Vulnerable; migrate to 12.4(10) or later | |------------------------------+----------------------------------------------| | 12.3XR | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.3XS | Vulnerable; migrate to 12.4(10) or later | |------------------------------+----------------------------------------------| | 12.3XU | Vulnerable; migrate to 12.4(6)T7 or later | |------------------------------+----------------------------------------------| | 12.3XW | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.3XX | Vulnerable; migrate to 12.4(10) or later | |------------------------------+----------------------------------------------| | 12.3YA | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.3YD | Vulnerable; migrate to 12.4(6)T7 or later | |------------------------------+----------------------------------------------| | 12.3YF | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.3YG | Vulnerable; migrate to 12.4(6)T7 or later | |------------------------------+----------------------------------------------| | 12.3YH | Vulnerable; migrate to 12.4(6)T7 or later | |------------------------------+----------------------------------------------| | 12.3YI | Vulnerable; migrate to 12.4(6)T7 or later | |------------------------------+----------------------------------------------| | 12.3YK | Vulnerable; migrate to 12.4(6)T7 or later | |------------------------------+----------------------------------------------| | 12.3YQ | Vulnerable; migrate to 12.4(6)T7 or later | |------------------------------+----------------------------------------------| | 12.3YS | Vulnerable; migrate to 12.4(6)T7 or later | |------------------------------+----------------------------------------------| | 12.3YT | Vulnerable; migrate to 12.4(6)T7 or later | |------------------------------+----------------------------------------------| | 12.3YU | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.3YX | 12.3(14)YX7 | | |------------------------------+----------------------------------------------| | 12.3YZ | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | Affected 12.4-Based Release | Rebuild | Maintenance | |------------------------------+---------------------+------------------------| | 12.4 | 12.4(7d) | 12.4(10) | |------------------------------+---------------------+------------------------| | 12.4SW | 12.4(11)SW1 | | |------------------------------+---------------------+------------------------| | | 12.4(6)T7 | | | |---------------------+------------------------| | 12.4T | 12.4(9)T3 | | | |---------------------+------------------------| | | 12.4(11)T1 | | |------------------------------+----------------------------------------------| | 12.4XA | Vulnerable; migrate to 12.4(6)T7 or later | |------------------------------+----------------------------------------------| | 12.4XB | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.4XC | 12.4(4)XC6 | | |------------------------------+---------------------+------------------------| | 12.4XD | 12.4(4)XD6 | | |------------------------------+----------------------------------------------| | 12.4XE | Vulnerable; contact TAC | |------------------------------+----------------------------------------------| | 12.4XJ | 12.4(11)XJ2 | | |------------------------------+----------------------------------------------| | 12.4XP | Vulnerable; contact TAC | +-----------------------------------------------------------------------------+
Cisco IOS XR +-----------
The following table lists fixed Cisco IOS XR software.
+---------------------------------------------------------------------+ | Cisco IOS XR | SMU ID | SMU Name | | Version | | | |---------------------+-----------------+-----------------------------| | 3.2.3 | AA01802 | hfr-k9sec-3.2.3.CSCsg41084 | |---------------------+-----------------+-----------------------------| | 3.2.4 | AA01801 | hfr-k9sec-3.2.4.CSCsg41084 | |---------------------+-----------------+-----------------------------| | 3.2.6 | AA01800 | hfr-k9sec-3.2.6.CSCsg41084 | |---------------------+-----------------+-----------------------------| | 3.3.0 | AA01799, | hfr-k9sec-3.3.0.CSCsg41084 | | | AA01780 | | |---------------------+-----------------+-----------------------------| | 3.3.0 | AA01780 | c12k-k9sec-3.3.0.CSCsg41084 | |---------------------+-----------------+-----------------------------| | 3.3.1 | AA01781 | c12k-k9sec-3.3.1.CSCsg41084 | |---------------------+-----------------+-----------------------------| | 3.3.1 | AA01798 | hfr-k9sec-3.3.1.CSCsg41084 | |---------------------+-----------------+-----------------------------| | 3.3.2 | AA01797 | hfr-k9sec-3.3.2.CSCsg41084 | |---------------------+-----------------+-----------------------------| | 3.3.3 | AA01796 | hfr-k9sec-3.3.3.CSCsg41084 | |---------------------+-----------------+-----------------------------| | 3.3.3 | AA01785 | c12k-k9sec-3.3.3.CSCsg41084 | |---------------------+-----------------+-----------------------------| | 3.4.0 | AA01782 | c12k-k9sec-3.4.0.CSCsg41084 | |---------------------+-----------------+-----------------------------| | 3.4.0 | AA01795 | hfr-k9sec-3.4.0.CSCsg41084 | |---------------------+-----------------+-----------------------------| | 3.4.1 | AA01783 | c12k-k9sec-3.4.1.CSCsg41084 | |---------------------+-----------------+-----------------------------| | 3.4.1 | AA01794 | hfr-k9sec-3.4.1.CSCsg41084 | +---------------------------------------------------------------------+
IOS XR Package Installation Envelopes (PIE) can be downloaded from File Exchange at: https://upload.cisco.com/cgi-bin/swc/fileexg/main.cgi?CONTYPES=IOS-XR Installation instructions are included in the accompanying .txt files.
Cisco PIX and ASA Security Appliance +-----------------------------------
This vulnerability is fixed in the following 7.x software releases: 7.0(6.7), 7.1(2.27), 7.2(1.22), 7.2(2). All 8.x software releases do contain the fixed library and are not affected. No 6.x software releases are affected by this vulnerability.
Cisco Firewall Service Module (FWSM) +-----------------------------------
This vulnerability is fixed in the following software releases:
- 2.3(5) maintenance release, expected in 2007-June
- 3.1(6) maintenance release, expected in 2007-June
Cisco Unified CallManager +------------------------
This vulnerability is fixed in the following software releases.
- 4.0(x) releases are vulnerable but no fix will be provided. Customers are advised to upgrade to the fixed 4.1 or 4.2 software.
- 4.1(3)sr.5 expected in 2007-May-24
- 4.2(3)sr.2 expected in 2007-May
- 4.3(1)sr.1 expected 2007-Jun
- 5.0(4) - no fixed software planned, users should upgrade to 5.1(2)
- 5.1(1) - no fixed software planned, users should upgrade to 5.1(2)
- 5.1(2)
Workarounds
The only way to prevent a device being susceptible to the listed vulnerabilities is to disable the affected service(s). However, if regular maintenance and operation of the device relies on these services then there is no workaround.
It is possible to mitigate these vulnerabilities by preventing unauthorized hosts to access the affected devices. Additional mitigations that can be deployed on Cisco devices within the network are available in the Cisco Applied Intelligence companion document for this advisory:
http://www.cisco.com/warp/ public/707/cisco-air-20070522-crypto.shtml
Control Plane Policing (CoPP) +----------------------------
Control Plane Policing: IOS software versions that support Control Plane Policing (CoPP) can be configured to help protect the device from attacks that target the management and control planes. CoPP is available in Cisco IOS release trains 12.0S, 12.2SX, 12.2S, 12.3T, 12.4, and 12.4T.
In the CoPP example below, the ACL entries that match the exploit packets with the permit action will be discarded by the policy-map drop function, while packets that match a deny action (not shown) are not affected by the policy-map drop function.
!-- Include deny statements up front for any protocols/ports/IP addresses that
!-- should not be impacted by CoPP
!-- Include permit statements for the protocols/ports that will be governed by CoPP
!-- port 443 - HTTPS
access-list 100 permit tcp any any eq 443
!-- port 500 - IKE
access-list 100 permit udp any any eq 500
!-- port 848 - GDOI
access-list 100 permit tcp any any eq 848
!-- port 5060 - SIP-TLS
access-list 100 permit tcp any any eq 5060
!-- port 5354 - TIDP
access-list 100 permit tcp any any eq 5354
!-- Permit (Police or Drop)/Deny (Allow) all other Layer3 and Layer4
!-- traffic in accordance with existing security policies and
!-- configurations for traffic that is authorized to be sent
!-- to infrastructure devices.
!
!-- Create a Class-Map for traffic to be policed by
!-- the CoPP feature.
!
class-map match-all Drop-Known-Undesirable
match access-group 100
!
!-- Create a Policy-Map that will be applied to the
!-- Control-Plane of the device.
!
policy-map CoPP-Input-Policy
class Drop-Known-Undesirable
drop
!-- Apply the Policy-Map to the Control-Plane of the
!-- device.
!
control-plane
service-policy input CoPP-Input-Policy
Please note that in the 12.0S, 12.2S, and 12.2SX Cisco IOS trains, the policy-map syntax is different:
policy-map CoPP-Input-Policy
class Drop-Known-Undesirable
police 32000 1500 1500 conform-action drop exceed-action drop
NOTE: In the above CoPP example, the ACL entries with the "permit" action that match the exploit packets result in the discarding of those packets by the policy-map drop function, while packets that match the "deny" action are not affected by the policy-map drop function.
Additional information on the configuration and use of the CoPP feature can be found at http://www.cisco.com/en/US/products/ps6642/products_white_paper0900aecd804fa16a.shtml and http://www.cisco.com/en/US/products/sw/iosswrel/ps1838/products_feature_guide09186a008052446b.html
Access Control List (ACL) +------------------------
Access control lists can be used to help mitigate attacks that may try to exploit these vulnerabilities. This is done in a way that only packets from the legitimate sources are allowed to reach the device and all others are dropped.
access-list 101 permit tcp host <legitimate_host_IP_address> host <router_IP_address> eq 443
access-list 101 permit udp host <legitimate_host_IP_address> host <router_IP_address> eq 500
access-list 101 permit tcp host <legitimate_host_IP_address> host <router_IP_address> eq 506
access-list 101 permit tcp host <legitimate_host_IP_address> host <router_IP_address> eq 4848
access-list 101 permit tcp host <legitimate_host_IP_address> host <router_IP_address> eq 5060
access-list 101 permit tcp host <legitimate_host_IP_address> host <router_IP_address> eq 5354
access-list 101 deny tcp any any eq 443
access-list 101 deny udp any any eq 500
access-list 101 deny tcp any any eq 506
access-list 101 deny udp any any eq 4848
access-list 101 deny tcp any any eq 5060
access-list 101 deny tcp any any eq 5354
Obtaining Fixed Software
Cisco has made free software available to address this vulnerability for affected customers. 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/public/sw-license-agreement.html, or as otherwise set forth at Cisco.com Downloads at http://www.cisco.com/public/sw-center/sw-usingswc.shtml.
Do not contact either "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 agreement 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 who do not hold a Cisco service contract and customers who purchase through third-party vendors but are unsuccessful at obtaining fixed software through their point of sale should get their 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
Have your product serial number available and give the URL of this notice as evidence of your entitlement to a free upgrade. Free upgrades for non-contract customers must be requested through the TAC.
Refer to http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml for additional TAC contact information, including special 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.
This vulnerability was discovered by Cisco during internal testing.
Status of This Notice: Interim
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. CISCO EXPECTS TO UPDATE THIS DOCUMENT AS NEW INFORMATION BECOMES AVAILABLE.
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-20070522-crypto.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-teams@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 | 2007-May-22 | 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.
All contents are Copyright 2006-2007 Cisco Systems, Inc. All rights reserved.
Updated: May 22, 2007 Document ID: 91890
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux)
iD8DBQFGUv7c8NUAbBmDaxQRAse8AJ9YwxPEprfhiJNzLVTLMXsTnTuWSwCghmmF qlrKeNA331DvYso6f2C5mRk= =dfTU -----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-200705-0570",
"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": "ios",
"scope": "eq",
"trust": 1.1,
"vendor": "cisco",
"version": "12.3"
},
{
"model": "pix/asa",
"scope": "eq",
"trust": 1.1,
"vendor": "cisco",
"version": "7.0"
},
{
"model": "ios",
"scope": "eq",
"trust": 1.1,
"vendor": "cisco",
"version": "12.4"
},
{
"model": "ios xr",
"scope": null,
"trust": 1.1,
"vendor": "cisco",
"version": null
},
{
"model": "bsafe crypto-c",
"scope": "lte",
"trust": 1.0,
"vendor": "dell",
"version": "6.3"
},
{
"model": "bsafe cert-c",
"scope": "lte",
"trust": 1.0,
"vendor": "dell",
"version": "2.7"
},
{
"model": null,
"scope": null,
"trust": 0.8,
"vendor": "cisco",
"version": null
},
{
"model": null,
"scope": null,
"trust": 0.8,
"vendor": "emc formerly data general",
"version": null
},
{
"model": null,
"scope": null,
"trust": 0.8,
"vendor": "novell",
"version": null
},
{
"model": null,
"scope": null,
"trust": 0.8,
"vendor": "rsa security",
"version": null
},
{
"model": "psp",
"scope": null,
"trust": 0.8,
"vendor": "sony computer entertainment",
"version": null
},
{
"model": "teamware office",
"scope": "eq",
"trust": 0.8,
"vendor": "fujitsu",
"version": "200x security options v2.0l10"
},
{
"model": "teamware office",
"scope": "eq",
"trust": 0.8,
"vendor": "fujitsu",
"version": "security options v5.3l13"
},
{
"model": "playstation 3",
"scope": null,
"trust": 0.8,
"vendor": "sony computer entertainment",
"version": null
},
{
"model": "teamware office",
"scope": "eq",
"trust": 0.8,
"vendor": "fujitsu",
"version": "200x security options v2.0l30"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 0.8,
"vendor": "cisco",
"version": "3.1(6)"
},
{
"model": "ios",
"scope": "eq",
"trust": 0.8,
"vendor": "cisco",
"version": "12.0"
},
{
"model": "ios",
"scope": "eq",
"trust": 0.8,
"vendor": "cisco",
"version": "12.2"
},
{
"model": "bsafe cert-c",
"scope": "lt",
"trust": 0.8,
"vendor": "rsa security",
"version": "2.8 earlier versions"
},
{
"model": "teamware office",
"scope": "eq",
"trust": 0.8,
"vendor": "fujitsu",
"version": "200x security options v1.0l10"
},
{
"model": "teamware office",
"scope": "eq",
"trust": 0.8,
"vendor": "fujitsu",
"version": "200x security options v2.0l20"
},
{
"model": "pix/asa",
"scope": "eq",
"trust": 0.8,
"vendor": "cisco",
"version": "7.1"
},
{
"model": "ios",
"scope": "eq",
"trust": 0.8,
"vendor": "cisco",
"version": "12.1"
},
{
"model": "pix/asa",
"scope": "eq",
"trust": 0.8,
"vendor": "cisco",
"version": "7.2"
},
{
"model": "unified callmanager",
"scope": null,
"trust": 0.8,
"vendor": "cisco",
"version": null
},
{
"model": "teamware office",
"scope": "eq",
"trust": 0.8,
"vendor": "fujitsu",
"version": "security options v5.3l11"
},
{
"model": "firewall services module",
"scope": "lt",
"trust": 0.8,
"vendor": "cisco",
"version": "version"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 0.8,
"vendor": "cisco",
"version": "2.3(5)"
},
{
"model": "bsafe crypto-c",
"scope": "lt",
"trust": 0.8,
"vendor": "rsa security",
"version": "6.3.1 earlier versions"
},
{
"model": "bsafe cert-c",
"scope": "eq",
"trust": 0.6,
"vendor": "rsa",
"version": "2.7"
},
{
"model": "bsafe crypto-c",
"scope": "eq",
"trust": 0.6,
"vendor": "rsa",
"version": "6.3"
},
{
"model": "ios 12.3xd",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3b",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3yk",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2sea",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3xu",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2ixb",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"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": "unified callmanager",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "4.0"
},
{
"model": "ios 12.2seg",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "bsafe cert-c",
"scope": "ne",
"trust": 0.3,
"vendor": "rsa",
"version": "2.8"
},
{
"model": "ios 12.2yv",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2sb",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "firewall services module",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": "3.1(6)"
},
{
"model": "ios 12.2sxe",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "unified communications manager",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": "5.1(2)"
},
{
"model": "pix/asa",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": "6.0"
},
{
"model": "ios 12.4 t7",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "pix/asa",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": "7.1(2.27)"
},
{
"model": "ios 12.4 xd6",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4 xj2",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4xd",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "unified communications manager 4.2 sr2",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "unified callmanager",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "5.0(2)"
},
{
"model": "ios 12.2 sxf8",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2seb",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": "12.3(22)"
},
{
"model": "ios xr",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": "3.3.1"
},
{
"model": "ios 12.3yh",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "pix/asa",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "7.0(5.2)"
},
{
"model": "firewall services module",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": "2.3(5)"
},
{
"model": "ios 12.2zh",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2sed",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "unified callmanager",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "5.0(4)"
},
{
"model": "ios 12.2t",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3xi",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "unified communications manager 4.3 sr.1",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2 see3",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "3.1(3.3)"
},
{
"model": "unified callmanager",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "4.2"
},
{
"model": "ios 12.3xh",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2fy",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "pix/asa",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "7.0.4"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "3.1(1.7)"
},
{
"model": "pix/asa",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "7.0(5)"
},
{
"model": "ios 12.3xb",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "pix/asa",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": "7.2(2)"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "3.1(3.2)"
},
{
"model": "ios 12.2zj",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "bsafe crypto-c",
"scope": "ne",
"trust": 0.3,
"vendor": "rsa",
"version": "6.3.1"
},
{
"model": "ios 12.2ex",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3yf",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2zl",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2sxf",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2ixc",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "unified callmanager 4.1 sr4",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3yz",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3yg",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "pix/asa",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "7.2(1)"
},
{
"model": "ios 12.4 sw1",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3 jl1",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2ewa",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2zg",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3jl",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "bsafe cert-c",
"scope": "eq",
"trust": 0.3,
"vendor": "rsa",
"version": "0"
},
{
"model": "ios 12.3jea",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3xj",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "unified callmanager",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "4.1"
},
{
"model": "ios 12.3xs",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3t",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "unified callmanager",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "5.0(3)"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "2.3(4.7)"
},
{
"model": "ios 12.2ja",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3xw",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios xr",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": "3.2.3"
},
{
"model": "bsafe crypto-c",
"scope": "eq",
"trust": 0.3,
"vendor": "rsa",
"version": "0"
},
{
"model": "ios 12.2jk",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2xr",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3yd",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4 xc6",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "3.1(3.18)"
},
{
"model": "ios xr",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": "3.3"
},
{
"model": "ios 12.3ja",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "international cryptographic infrastructure",
"scope": "ne",
"trust": 0.3,
"vendor": "novell",
"version": "2.7.2"
},
{
"model": "ios 12.4xj",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3jk",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2ixa",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2bc",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4 t1",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3xr",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2bz",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4xc",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios zw",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "12.2"
},
{
"model": "ios 12.2 sra2",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2 sga1",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "unified callmanager",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "5.0"
},
{
"model": "pix/asa",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "7.0.1.4"
},
{
"model": "ios 12.3yx",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2yu",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "pix/asa",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": "7.0(6.7)"
},
{
"model": "unified communications manager",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "5.1(1)"
},
{
"model": "pix/asa",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "7.1(2)"
},
{
"model": "ios 12.2sra",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2sga",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2sec",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2 sg",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2fz",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2cx",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "2.3"
},
{
"model": "pix/asa",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": "8.0"
},
{
"model": "ios",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": "12.4(10)"
},
{
"model": "ios 12.2cz",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2fx",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2zf",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2sxd",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3xe",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "pix/asa",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": "7.2(1.22)"
},
{
"model": "ios xr",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": "3.2.4"
},
{
"model": "ios 12.4 t3",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2b",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3xf",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "unified callmanager",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "5.0(1)"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "3.1(3.24)"
},
{
"model": "ios 12.2 ewa9",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3 yx7",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3yt",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3tpc",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2see",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios xr",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": "3.4"
},
{
"model": "ios 12.3jx",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios xr",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": "3.3.2"
},
{
"model": "ios 12.3xk",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "unified callmanager 5.0",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "unified callmanager 5.0 su1",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3yq",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "2.3(4)"
},
{
"model": "unified callmanager 4.1 sr5",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3bc",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2zu",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios xr",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": "3.2.6"
},
{
"model": "ios 12.3ya",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2 se2",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2ze",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3 bc6",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2sg",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3yu",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2srb",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "12.3xx"
},
{
"model": "ios 12.3xa",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2zd",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2 sb3",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4xa",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios xr",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": "3.3.3"
},
{
"model": "ios 12.3xg",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2 srb",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4xb",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4xp",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3yi",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3xq",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "3.1(1.9)"
},
{
"model": "ios 12.4xe",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2ey",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "3.1(4)"
},
{
"model": "ios 12.2sef",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2ew",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2ez",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3xc",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4t",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "pix/asa",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "7.0.4.3"
},
{
"model": "ios xr",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": "3.4.1"
},
{
"model": "unified callmanager 4.2 sr1",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4sw",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.3ys",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "3.1"
},
{
"model": "firewall services module",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "3.1(3.11)"
},
{
"model": "ios 12.2se",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "international cryptographic infostructure",
"scope": "eq",
"trust": 0.3,
"vendor": "novell",
"version": "2.6.1"
}
],
"sources": [
{
"db": "CERT/CC",
"id": "VU#754281"
},
{
"db": "BID",
"id": "24104"
},
{
"db": "JVNDB",
"id": "JVNDB-2007-000404"
},
{
"db": "NVD",
"id": "CVE-2006-3894"
},
{
"db": "CNNVD",
"id": "CNNVD-200705-446"
}
]
},
"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": [
{
"children": [],
"cpe_match": [
{
"cpe23Uri": "cpe:2.3:a:dell:bsafe_cert-c:*:*:*:*:*:*:*:*",
"cpe_name": [],
"versionEndIncluding": "2.7",
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:dell:bsafe_crypto-c:*:*:*:*:*:*:*:*",
"cpe_name": [],
"versionEndIncluding": "6.3",
"vulnerable": true
}
],
"operator": "OR"
}
]
}
],
"sources": [
{
"db": "NVD",
"id": "CVE-2006-3894"
}
]
},
"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-200705-446"
}
],
"trust": 0.6
},
"cve": "CVE-2006-3894",
"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": [
{
"acInsufInfo": false,
"accessComplexity": "LOW",
"accessVector": "NETWORK",
"authentication": "NONE",
"author": "NVD",
"availabilityImpact": "PARTIAL",
"baseScore": 5.0,
"confidentialityImpact": "NONE",
"exploitabilityScore": 10.0,
"impactScore": 2.9,
"integrityImpact": "NONE",
"obtainAllPrivilege": false,
"obtainOtherPrivilege": false,
"obtainUserPrivilege": false,
"severity": "MEDIUM",
"trust": 1.0,
"userInteractionRequired": false,
"vectorString": "AV:N/AC:L/Au:N/C:N/I:N/A:P",
"version": "2.0"
},
{
"acInsufInfo": null,
"accessComplexity": "Low",
"accessVector": "Network",
"authentication": "None",
"author": "NVD",
"availabilityImpact": "Partial",
"baseScore": 5.0,
"confidentialityImpact": "None",
"exploitabilityScore": null,
"id": "CVE-2006-3894",
"impactScore": null,
"integrityImpact": "None",
"obtainAllPrivilege": null,
"obtainOtherPrivilege": null,
"obtainUserPrivilege": null,
"severity": "Medium",
"trust": 0.8,
"userInteractionRequired": null,
"vectorString": "AV:N/AC:L/Au:N/C:N/I:N/A:P",
"version": "2.0"
},
{
"accessComplexity": "LOW",
"accessVector": "NETWORK",
"authentication": "NONE",
"author": "VULHUB",
"availabilityImpact": "PARTIAL",
"baseScore": 5.0,
"confidentialityImpact": "NONE",
"exploitabilityScore": 10.0,
"id": "VHN-20002",
"impactScore": 2.9,
"integrityImpact": "NONE",
"severity": "MEDIUM",
"trust": 0.1,
"vectorString": "AV:N/AC:L/AU:N/C:N/I:N/A:P",
"version": "2.0"
}
],
"cvssV3": [],
"severity": [
{
"author": "NVD",
"id": "CVE-2006-3894",
"trust": 1.8,
"value": "MEDIUM"
},
{
"author": "CARNEGIE MELLON",
"id": "VU#754281",
"trust": 0.8,
"value": "0.13"
},
{
"author": "CNNVD",
"id": "CNNVD-200705-446",
"trust": 0.6,
"value": "MEDIUM"
},
{
"author": "VULHUB",
"id": "VHN-20002",
"trust": 0.1,
"value": "MEDIUM"
}
]
}
],
"sources": [
{
"db": "CERT/CC",
"id": "VU#754281"
},
{
"db": "VULHUB",
"id": "VHN-20002"
},
{
"db": "JVNDB",
"id": "JVNDB-2007-000404"
},
{
"db": "NVD",
"id": "CVE-2006-3894"
},
{
"db": "CNNVD",
"id": "CNNVD-200705-446"
}
]
},
"description": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/description#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "The RSA Crypto-C before 6.3.1 and Cert-C before 2.8 libraries, as used by RSA BSAFE, multiple Cisco products, and other products, allows remote attackers to cause a denial of service via malformed ASN.1 objects. The RSA BSAFE Crypto-C and Cert-C libraries contain a denial-of-service vulnerability. RSA Security provides RSA BSAFE Cert-C and Crypto-C For implementing digital certificate processing and cryptographic algorithms respectively C/C++ A library for languages. RSA BSAFE Cert-C and Crypto-C Crafted by ASN.1 There is a problem with object processing, and there is a problem that the library falls into an infinite loop.Service operation disrupted by a remote third party (DoS) There is a possibility of being attacked. \nExploiting this vulnerability allows attackers to crash applications that use the affected library. The specific impact of this vulnerability depends on the nature of the applications. Local and remote attacks may be possible. Depending on the nature of vulnerable applications, attackers may be able to exploit this issue without authentication. \nThese versions are vulnerable:\nRSA BSAFE Crypto-C prior to 6.3.1\nCert-C prior to 2.8\nThe vendor tracks this issue by RSA Bug ID 46337. \nCisco tracks this issue as Bug IDs:\nCisco IOS: CSCsd85587\nCisco IOS XR: CSCsg41084\nCisco PIX and ASA Security Appliances: CSCse91999\nCisco Firewall Services Module (FWSM): CSCsi97695\nCisco Unified CallManager: CSCsg44348. -----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA1\n\n\nCisco Security Advisory: Vulnerability In Crypto Library\n\nAdvisory ID: cisco-sa-20070522-crypto.shtml\n\nhttp://www.cisco.com/warp/public/707/cisco-sa-20070522-crypto.shtml\n\nRevision 1.0\n\nFor Public Release 2007 May 22 1300 UTC (GMT)\n\n- ------------------------------------------------------------------------------\n\nSummary\n=======\n\nA vulnerability has been discovered in a third party cryptographic library\nwhich is used by a number of Cisco products. This vulnerability may be\ntriggered when a malformed Abstract Syntax Notation One (ASN.1) object is\nparsed. Due to the nature of the vulnerability it may be possible, in some\ncases, to trigger this vulnerability without a valid certificate or valid\napplication-layer credentials (such as a valid username or password). \n\nSuccessful repeated exploitation of any of these vulnerabilities may lead to a\nsustained Denial-of-Service (DoS); however, vulnerabilities are not known to\ncompromise either the confidentiality or integrity of the data or the device. \nThese vulnerabilities are not believed to allow an attacker will not be able to\ndecrypt any previusly encrypted information. It is externally\ncoordinated and is tracked by the following external coordinators:\n\n * JPCERT/CC - tracked as JVNVU#754281\n * CPNI - tracked as NISCC-362917\n * CERT/CC - tracked as VU#754281\n\nCisco has made free software available to address this vulnerability for\naffected customers. There are no workarounds available to mitigate the effects\nof the vulnerability. \n\nThis advisory is posted at \nhttp://www.cisco.com/warp/public/707/cisco-sa-20070522-crypto.shtml. \n\nNote: Another related advisory is posted together with this Advisory. \nIt also describes vulnerabilities related to cryptography that affect\nCisco IOS. A combined software table for Cisco IOS only is available at\nhttp://www.cisco.com /warp/public/707/cisco-sa-20070522-cry-bundle.shtml\nand can be used to choose a software release which fixes all\nsecurity vulnerabilities published as of May 22, 2007. It is sufficient that only one\nprotocol or feature is enabled in order for a devices to be vulnerable. In\norder to be not vulnerable, all of the listed application protocols or features\nmust be disabled. \n\nAffected protocols in Cisco IOS\n+------------------------------\n\nTo determine the software running on a Cisco IOS product, log in to the device\nand issue the \"show version\" command to display the system banner. Cisco IOS\nsoftware will identify itself as \"Internetwork Operating System Software\" or\nsimply \"IOS.\" On the next line of output, the image name will be displayed\nbetween parentheses, followed by \"Version\" and the Cisco IOS release name. \nOther Cisco devices will not have the \"show version\" command, or will give\ndifferent output. \n\nOnly Cisco IOS images that contain the Crypto Feature Set are vulnerable. \nCustomers who are not running an IOS image with crypto support are not exposed\nto this vulnerability. \n\nCisco IOS feature set naming indicates that IOS images with crypto support have\n\u0027K8\u0027 or \u0027K9\u0027 in the feature designator field. \n\nThe following example shows output from a device running an IOS image with\ncrypto support:\n\n Router\u003eshow version\n Cisco IOS Software, 7200 Software (C7200-IK9S-M), Version 12.3(14)T1, RELEASE SOFTWARE (fc1)\n Technical Support: http://www.cisco.com/techsupport\n Copyright (c) 1986-2005 by Cisco Systems, Inc. \n Compiled Thu 31-Mar-05 08:04 by yiyan\n\n\nSince the feature set designator (IK9S) contains \u0027K9\u0027, it can be determine that\nthis feature set contains crypto support. \n\nAdditional information about Cisco IOS release naming is available at the\nfollowing link: \nhttp://www.cisco.com/en/US/products/sw/iosswrel/ps1828/products_white_paper09186a008018305e.shtml. \n\nYou are affected by this vulnerability if you are running one of the vulnerable\nIOS software releases and have, at least one, of the following protocols or\nfeatures enabled:\n\n * Internet Security Association and Key Management Protocol (ISAKMP)\n * In some IOS releases the Secure Socket Layer (SSL) may also be affected\n * Threat Information Distribution Protocol (TIDP)\n * Cisco IOS SIP Gateway Signaling Support Over TLS (SIP-TLS)\n * Extensible Authentication Protocol-Transport Layer Security (EAP-TLS)\n\nAs some other protocols may use affected crypto library the most accurate way\nto determine if your IOS release is vulnerable is to consult fixed IOS releases\ntable. \n\nInternet Security Association and Key Management Protocol (ISAKMP)\n+-----------------------------------------------------------------\n\nTo determine if your device has ISAKMP enabled, enter the command \n\"show crypto isakmp policy\". Below is an example of a device that has \nISAKMP enabled. \n\n Router#show crypto isakmp policy\n\n Global IKE policy\n Protection suite of priority 1\n \u003cmore output\u003e\n\n\nIf your output is like in the following example then you do not have IKE\nenabled on your device. \n\n Router#show crypto isakmp policy\n ISAKMP is turned off\n\n\nIn Cisco IOS two features rely on ISAKMP - IPSec and Group Domain of\nInterpretation (GDOI). Presence of either of these features is detected by the\nprevious example. \n\nPrior to IOS version 12.3(8)T, IKE was enabled by default, with no crypto\nconfiguration needed for the IOS device to process IKE messages. \n\n12.2SXD versions of Cisco IOS have IKE enabled by default. To ensure that IKE\nprocessing is disabled, enter the global configuration command \n\"no crypto isakmp enable\". \n\nAs of IOS version 12.3(2)T (which includes all 12.4-based versions), crypto\nconfiguration is required to enable IKE message processing. \n\nIn order for an IOS device to be vulnerable crypto map must be explicilty\nconfigured and applied to an interface. \n\nSecure Socket Layer (SSL)\n+------------------------\n\nIn some Cisco IOS software releases the vulnerable library is used to process\nelements of SSL functionalities. SSL is used to protect several application\nlayer protocols like Hyper Text Transfer Protocol over SSL (HTTPS). \n\nHTTPS is not the only protocol that may use SSL but it is the most commonly\nknown. In order to determine if your device has HTTPS configured enter the\ncommand \"show running | include secure\". Below is an example of a device \nthat has HTTPS enabled. \n\n router#show running | include secure-server\n ip http secure-server\n\n\nThreat Information Distribution Protocol (TIDP)\n+----------------------------------------------\n\nTo determine if your device has TDIP enabled, enter the command \n\"show running-config | include parameter-map\". Below is an example of a \ndevice that has TDIP enabled. \n\n router#show running | include parameter-map\n parameter-map type tms TMS_PAR\n\n\nCisco IOS SIP Gateway Signaling Support Over TLS (SIP-TLS)\n+---------------------------------------------------------\n\nTo determine if your device has SIP-TLS enabled, enter the command \n\"show running-config | include crypto signaling\". Below is an example of \na device that has SIP-TLS enabled. \n\n router#show running | include crypto signaling\n crypto signaling default trustpoint user1\n\n\nExtensible Authentication Protocol-Transport Layer Security (EAP-TLS)\n+--------------------------------------------------------------------\n\nTo determine if your device has EAP-TLS enabled, enter the command \n\"show running-config | include method\". Below is an example of a device \nthat has EAP-TLS enabled. \n\n Router#show running | include method\n method tls\n\n\nAffected protocols in Cisco IOS XR\n+---------------------------------\n\nYou are affected by this vulnerability if you are running one of the vulnerable\nCisco IOS XR software releases and have, at least one, of the following\nprotocols or features enabled:\n\n * Internet Security Association and Key Management Protocol (ISAKMP)\n * In some IOS XR releases the Secure Socket Layer (SSL) may also be affected\n * Secure Shell (SSH)\n\nInternet Security Association and Key Management Protocol (ISAKMP)\n+-----------------------------------------------------------------\n\nTo determine if your device has ISAKMP enabled, enter the command \n\"show running-config | include isakmp\". Below is an example of a device \nthat has IKE enabled. \n\n Router#show running-config | include isakmp\n crypto isakmp\n crypto isakmp policy 1\n crypto isakmp profile profile-a\n\n\nSecure Socket Layer (SSL)\n+------------------------\n\nSSL is used to provide secure communications to the application layer\nprotocols like Hyper Text Transfer Protocol over SSL (HTTPS) and Object\nRequest Brokers (ORB). To determine if your device has any service\nenabled that uses SSL, enter one of the following commands \n\"show running-config | include http server ssl\" or \n\"show running-config | include xml agent corba ssl\". Below is an example \nof a device that has both of the services enabled. \n\n Router#show running-config | include http server ssl\n http server ssl\n\n Router#show running-config | include xml agent corba ssl\n xml agent corba ssl\n\n\nSecure Shell (SSH)\n+-----------------\n\nSSH is an application and a protocol that provides secure replacement for the\nsuite of Berkeley r-tools such as rsh, rlogin and rcp. It is highly prefered\nover Telnet for interactive sessions. To determine if your device has SSH\nenabled enter the command \"show running-config | include ssh server\". Below \nis an example of a device that has SSH enabled. \n\n Router#show running-config | include ssh server\n ssh server\n ssh server rate-limit 100\n\n\nAffected protocols in Cisco PIX and ASA Security Appliances\n+----------------------------------------------------------\n\nYou are affected by this vulnerability if you are running one of the vulnerable\nCisco PIX and ASA software releases and have, at least one, of the following\nprotocols or features enabled:\n\n * Secure Shell (SSH)\n * Internet Security Association and Key Management Protocol (ISAKMP)\n * Secure Socket Layer (SSL)\n\nSecure Shell (SSH)\n+-----------------\n\nTo determine if a device has SSH enabled, enter the command \"show running\" \nand observe the output. If it contains the line as in the following example \nthen SSH is enabled. \n\n PIX#show running\n .... \n ssh \u003chost_IP_address\u003e \u003chost_netmask\u003e \u003cinterface\u003e\n .... \n\n\nInternet Security Association and Key Management Protocol (ISAKMP)\n+-----------------------------------------------------------------\n\nTo determine if a device has ISAKMP enabled, enter the command \"show running\" \nand observe the output. If it contains the lines as in the following \nexample then ISAKMP is enabled. \n\n PIX#show running\n .... \n crypto isakmp policy 2\n authentication rsa-sig\n .... \n\n\nSecure Socket Layer (SSL)\n+------------------------\n\nSSL is used to protect several application layer protocols like Hyper Text\nTransfer Protocol over SSL (HTTPS) and Cisco Adaptive Security Device Manager\n(ASDM) session. \n\nTo determine if a device has SSL enabled, enter the command \"show running\" \nand observe the output. If it contains the line as in the following \nexample then SSL is enabled. \n\n PIX#show running\n .... \n http server enable\n .... \n\n\nAffected protocols in Cisco Unified CallManager\n+----------------------------------------------\n\nYou are affected by this vulnerability if you are running one of the vulnerable\nCisco Unified CallManager software releases and have, at least one, of the\nfollowing protocols or features enabled:\n\n * Certificate Authority Proxy Function (CAPF)\n * Cisco TAPI Service Provider (Cisco Unified CallManager TSP)\n\nCertificate Authority Proxy Function (CAPF)\n+------------------------------------------\n\nCAPF is automatically installed with Cisco CallManager but is disabled by\ndefault. In order to verify if CAPF is enabled on your Unified CallManager do\nthe following steps. \n\n * Step 1 - In Cisco CallManager Administration, choose Service \u003e Service\n Parameter. \n * Step 2 - If you are running 4.x software then do the following: from the\n Server drop-down list box, choose the publisher database server. If you are\n running 5.x software then do the following: From the Server drop-down list\n box, choose the first node. \n * Step 3 - From the Service drop-down list box, choose the Cisco Certificate\n Authority Proxy Function service. \n\nIf you are given CAPF parameters then CAPF is running on your system. \n\nCisco TAPI Service Provider (Cisco Unified CallManager TSP)\n+----------------------------------------------------------\n\nIn order to determine if Cisco Unified CallManager TSP is installed open\nWindows Control Panel (Start \u003e Control Panel) and click on Add/Remove Programs. \nIf \u0027Cisco Unity-CM TSP\u0027 is listed then you have it installed on your system. \n\nProducts Confirmed Not Vulnerable\n+--------------------------------\n\nNo other Cisco products are currently known to be affected by this\nvulnerability. Specifically, the following product\u0027s features or products are\nknown not to be affected:\n\n * Cisco IOS\n + Secure Shell (SSH)\n + Secure Copy (SCP)\n * Cisco Unified Call Manager\n + Hyper Text Transfer Protocol over SSL (HTTPS)\n + Cisco Unified CallManager is configured for Secure Survivable Remote\n Site Telephony (SRST)\n * MeetingPlace Express and MeetingPlace for Telepresence\n * Cisco IP Communicator\n * All Cisco Unified IP Phones 7900 Series\n * CIP TN3270 Server\n * Cisco GSS 4400 Series Global Site Selector Appliances\n * Cisco CatOS\n\nThe list is not exhaustive. \n\nDetails\n=======\n\nASN.1 is defined by ITU-T (International Telecommunication Union -\nTelecommunication Standardization Sector) standards and it describes, among\nother things, data structures for encoding values. The vulnerability addressed\nby this advisory is related to the implementation of parsing certain data\nstructures and is not a vulnerability in the standard itself. \n\nProtocols that use ASN.1 (e.g., voice over IP, Simple Network Management\nProtocol and others), but do not rely on the vulnerable crypto library, are not\naffected. This advisory only addresses an implementation issue in a particular\ncrypto library from a single vendor. \n\nCisco will provide a base and temporal score. Customers can then compute\nenvironmental scores to assist in determining the impact of the vulnerability\nin individual networks. \n\nCisco PSIRT will set the bias in all cases to normal. Customers are encouraged\nto apply the bias parameter when determining the environmental impact of a\nparticular vulnerability. \n\nCVSS is a standards based scoring method that conveys vulnerability severity\nand helps determine urgency and priority of response. \n\nCisco has provided an FAQ to answer additional questions regarding CVSS at\nhttp://www.cisco.com/web/about/security/intelligence/cvss-qandas.html. \n\nCisco has also provided a CVSS calculator to help compute\nthe environmental impact for individual networks at\nhttp://intellishield.cisco.com/security/alertmanager/cvss. \n\nCisco Bug IDs:\n\nCSCsd85587 - Router crashes when processing ISAKMP message\n\nCVSS Base Score: 3.3\n Access Vector: Remote\n Access Complexity: Low\n Authentication: Not Required\n Confidentiality Impact: None\n Integrity Impact: None\n Availability Impact: Complete\n Impact Bias: Normal\n\nCVSS Temporal Score: 2.7\n Exploitability: Functional\n Remediation Level: Official Fix\n Report Confidence: Confirmed\n\n\nCSCsg41084 - IOS XR crashes when processing ISAKMP message\n\nCVSS Base Score: 3.3\n Access Vector: Remote\n Access Complexity: Low\n Authentication: Not Required\n Confidentiality Impact: None\n Integrity Impact: None\n Availability Impact: Complete\n Impact Bias: Normal\n\nCVSS Temporal Score: 2.7\n Exploitability: Functional\n Remediation Level: Official Fix\n Report Confidence: Confirmed\n\nCSCse91999 - PIX/ASA crashes when processing ISAKMP message\n\nCVSS Base Score: 3.3\n Access Vector: Remote\n Access Complexity: Low\n Authentication: Not Required\n Confidentiality Impact: None\n Integrity Impact: None\n Availability Impact: Complete\n Impact Bias: Normal\n\nCVSS Temporal Score: 2.7\n Exploitability: Functional\n Remediation Level: Official Fix\n Report Confidence: Confirmed\n\n\nCSCsg44348 - Unified CallManager crashes when processing crypto message\n\nCVSS Base Score: 3.3\n Access Vector: Remote\n Access Complexity: Low\n Authentication: Not Required\n Confidentiality Impact: None\n Integrity Impact: None\n Availability Impact: Complete\n Impact Bias: Normal\n\nCVSS Temporal Score: 2.7\n Exploitability: Functional\n Remediation Level: Official Fix\n Report Confidence: Confirmed\n\n\nImpact\n======\n\nSuccessful exploitation of the vulnerability listed in this advisory may result\nin the crash of a vulnerable device. Repeated exploitation can result in a\nsustained DoS attack. \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 Cisco IOS software table (below) describes a release\ntrain. If a given release train is vulnerable, then the earliest\npossible releases that contain the fix (the \"First Fixed Release\")\nand the anticipated date of availability for each are listed in the\n\"Rebuild\" and \"Maintenance\" columns. A device running a release in the\ngiven train that is earlier than the release in a specific column (less\nthan the First Fixed Release) is known to be vulnerable. The release\nshould be upgraded at least to the indicated release or a later version\n(greater than or equal to the First Fixed Release label). \n\nFor more information on the terms \"Rebuild\" and \"Maintenance,\" consult the \nfollowing URL:\nhttp://www.cisco.com/en/US/products/sw/iosswrel/ps1828/products_white_paper09186a008018305e.shtml\n\nCisco IOS\n+--------\n\nFixed Cisco IOS software releases are listed in the table below. \n\n+-----------------------------------------------------------------------------+\n| Major Release | Availability of Repaired Releases |\n|------------------------------+----------------------------------------------|\n| Affected 12.2-Based Release | Rebuild | Maintenance |\n|------------------------------+----------------------------------------------|\n| 12.2B | Vulnerable; migrate to 12.4(10) or later |\n|------------------------------+----------------------------------------------|\n| 12.2BC | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.2BZ | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.2CX | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.2CZ | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.2EW | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.2EWA | 12.2(25)EWA9 | |\n|------------------------------+----------------------------------------------|\n| 12.2EX | Vulnerable; migrate to 12.2(25)SEE3 or later |\n|------------------------------+----------------------------------------------|\n| 12.2EY | Vulnerable; migrate to 12.2(25)SEE3 or later |\n|------------------------------+----------------------------------------------|\n| 12.2EZ | Vulnerable; migrate to 12.2(25)SEE3 or later |\n|------------------------------+----------------------------------------------|\n| 12.2FX | Vulnerable; migrate to 12.2(25)SEE3 or later |\n|------------------------------+----------------------------------------------|\n| 12.2FY | Vulnerable; migrate to 12.2(35)SE2 or later |\n|------------------------------+----------------------------------------------|\n| 12.2FZ | Vulnerable; migrate to 12.2(35)SE2 or later |\n|------------------------------+----------------------------------------------|\n| 12.2IXA | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.2IXB | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.2IXC | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.2JA | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.2JK | Vulnerable; migrate to 12.4(6)T7 or later |\n|------------------------------+----------------------------------------------|\n| 12.2SB | 12.2(31)SB3 | |\n|------------------------------+---------------------+------------------------|\n| 12.2SE | 12.2(35)SE2 | |\n|------------------------------+----------------------------------------------|\n| 12.2SEA | Vulnerable; migrate to 12.2(25)SEE3 or later |\n|------------------------------+----------------------------------------------|\n| 12.2SEB | Vulnerable; migrate to 12.2(25)SEE3 or later |\n|------------------------------+----------------------------------------------|\n| 12.2SEC | Vulnerable; migrate to 12.2(25)SEE3 or later |\n|------------------------------+----------------------------------------------|\n| 12.2SED | Vulnerable; migrate to 12.2(25)SEE3 or later |\n|------------------------------+----------------------------------------------|\n| 12.2SEE | 12.2(25)SEE3 | |\n|------------------------------+----------------------------------------------|\n| 12.2SEF | Vulnerable; migrate to 12.2(35)SE2 or later |\n|------------------------------+----------------------------------------------|\n| 12.2SEG | Vulnerable; migrate to 12.2(35)SE2 or later |\n|------------------------------+----------------------------------------------|\n| 12.2SG | | 12.2(37)SG |\n|------------------------------+---------------------+------------------------|\n| 12.2SGA | 12.2(31)SGA1 | |\n|------------------------------+---------------------+------------------------|\n| 12.2SRA | 12.2(33)SRA3 | |\n|------------------------------+---------------------+------------------------|\n| 12.2SRB | | 12.2(33)SRB |\n|------------------------------+----------------------------------------------|\n| 12.2SXD | Vulnerable; migrate to 12.2(18)SXF8 or later |\n|------------------------------+----------------------------------------------|\n| 12.2SXE | Vulnerable; migrate to 12.2(18)SXF8 or later |\n|------------------------------+----------------------------------------------|\n| 12.2SXF | 12.2(18)SXF8 | |\n|------------------------------+----------------------------------------------|\n| 12.2T | Vulnerable; migrate to 12.3(22) or later |\n|------------------------------+----------------------------------------------|\n| 12.2XR | Vulnerable; migrate to 12.3(22) or later |\n|------------------------------+----------------------------------------------|\n| 12.2YU | Vulnerable; migrate to 12.4(10) or later |\n|------------------------------+----------------------------------------------|\n| 12.2YV | Vulnerable; migrate to 12.4(10) or later |\n|------------------------------+----------------------------------------------|\n| 12.2ZD | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.2ZE | Vulnerable; migrate to 12.3(22) or later |\n|------------------------------+----------------------------------------------|\n| 12.2ZF | Vulnerable; migrate to 12.4(10) or later |\n|------------------------------+----------------------------------------------|\n| 12.2ZG | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.2ZH | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.2ZJ | Vulnerable; migrate to 12.4(10) or later |\n|------------------------------+----------------------------------------------|\n| 12.2ZL | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.2ZU | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.2ZW | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| Affected 12.3-Based Release | Rebuild | Maintenance |\n|------------------------------+---------------------+------------------------|\n| 12.3 | | 12.3(22) |\n|------------------------------+----------------------------------------------|\n| 12.3B | Vulnerable; migrate to 12.4(10) or later |\n|------------------------------+----------------------------------------------|\n| 12.3BC | 12.3(17b)BC6 | |\n|------------------------------+----------------------------------------------|\n| 12.3JA | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.3JEA | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.3JK | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.3JL | 12.3(2)JL1 | |\n|------------------------------+----------------------------------------------|\n| 12.3JX | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.3T | Vulnerable; migrate to 12.4(10) or later |\n|------------------------------+----------------------------------------------|\n| 12.3TPC | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.3XA | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.3XB | Vulnerable; migrate to 12.4(10) or later |\n|------------------------------+----------------------------------------------|\n| 12.3XC | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.3XD | Vulnerable; migrate to 12.4(10) or later |\n|------------------------------+----------------------------------------------|\n| 12.3XE | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.3XF | Vulnerable; migrate to 12.4(10) or later |\n|------------------------------+----------------------------------------------|\n| 12.3XG | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.3XH | Vulnerable; migrate to 12.4(10) or later |\n|------------------------------+----------------------------------------------|\n| 12.3XI | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.3XJ | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.3XK | Vulnerable; migrate to 12.4(10) or later |\n|------------------------------+----------------------------------------------|\n| 12.3XQ | Vulnerable; migrate to 12.4(10) or later |\n|------------------------------+----------------------------------------------|\n| 12.3XR | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.3XS | Vulnerable; migrate to 12.4(10) or later |\n|------------------------------+----------------------------------------------|\n| 12.3XU | Vulnerable; migrate to 12.4(6)T7 or later |\n|------------------------------+----------------------------------------------|\n| 12.3XW | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.3XX | Vulnerable; migrate to 12.4(10) or later |\n|------------------------------+----------------------------------------------|\n| 12.3YA | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.3YD | Vulnerable; migrate to 12.4(6)T7 or later |\n|------------------------------+----------------------------------------------|\n| 12.3YF | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.3YG | Vulnerable; migrate to 12.4(6)T7 or later |\n|------------------------------+----------------------------------------------|\n| 12.3YH | Vulnerable; migrate to 12.4(6)T7 or later |\n|------------------------------+----------------------------------------------|\n| 12.3YI | Vulnerable; migrate to 12.4(6)T7 or later |\n|------------------------------+----------------------------------------------|\n| 12.3YK | Vulnerable; migrate to 12.4(6)T7 or later |\n|------------------------------+----------------------------------------------|\n| 12.3YQ | Vulnerable; migrate to 12.4(6)T7 or later |\n|------------------------------+----------------------------------------------|\n| 12.3YS | Vulnerable; migrate to 12.4(6)T7 or later |\n|------------------------------+----------------------------------------------|\n| 12.3YT | Vulnerable; migrate to 12.4(6)T7 or later |\n|------------------------------+----------------------------------------------|\n| 12.3YU | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.3YX | 12.3(14)YX7 | |\n|------------------------------+----------------------------------------------|\n| 12.3YZ | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| Affected 12.4-Based Release | Rebuild | Maintenance |\n|------------------------------+---------------------+------------------------|\n| 12.4 | 12.4(7d) | 12.4(10) |\n|------------------------------+---------------------+------------------------|\n| 12.4SW | 12.4(11)SW1 | |\n|------------------------------+---------------------+------------------------|\n| | 12.4(6)T7 | |\n| |---------------------+------------------------|\n| 12.4T | 12.4(9)T3 | |\n| |---------------------+------------------------|\n| | 12.4(11)T1 | |\n|------------------------------+----------------------------------------------|\n| 12.4XA | Vulnerable; migrate to 12.4(6)T7 or later |\n|------------------------------+----------------------------------------------|\n| 12.4XB | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.4XC | 12.4(4)XC6 | |\n|------------------------------+---------------------+------------------------|\n| 12.4XD | 12.4(4)XD6 | |\n|------------------------------+----------------------------------------------|\n| 12.4XE | Vulnerable; contact TAC |\n|------------------------------+----------------------------------------------|\n| 12.4XJ | 12.4(11)XJ2 | |\n|------------------------------+----------------------------------------------|\n| 12.4XP | Vulnerable; contact TAC |\n+-----------------------------------------------------------------------------+\n\nCisco IOS XR\n+-----------\n\nThe following table lists fixed Cisco IOS XR software. \n\n+---------------------------------------------------------------------+\n| Cisco IOS XR | SMU ID | SMU Name |\n| Version | | |\n|---------------------+-----------------+-----------------------------|\n| 3.2.3 | AA01802 | hfr-k9sec-3.2.3.CSCsg41084 |\n|---------------------+-----------------+-----------------------------|\n| 3.2.4 | AA01801 | hfr-k9sec-3.2.4.CSCsg41084 |\n|---------------------+-----------------+-----------------------------|\n| 3.2.6 | AA01800 | hfr-k9sec-3.2.6.CSCsg41084 |\n|---------------------+-----------------+-----------------------------|\n| 3.3.0 | AA01799, | hfr-k9sec-3.3.0.CSCsg41084 |\n| | AA01780 | |\n|---------------------+-----------------+-----------------------------|\n| 3.3.0 | AA01780 | c12k-k9sec-3.3.0.CSCsg41084 |\n|---------------------+-----------------+-----------------------------|\n| 3.3.1 | AA01781 | c12k-k9sec-3.3.1.CSCsg41084 |\n|---------------------+-----------------+-----------------------------|\n| 3.3.1 | AA01798 | hfr-k9sec-3.3.1.CSCsg41084 |\n|---------------------+-----------------+-----------------------------|\n| 3.3.2 | AA01797 | hfr-k9sec-3.3.2.CSCsg41084 |\n|---------------------+-----------------+-----------------------------|\n| 3.3.3 | AA01796 | hfr-k9sec-3.3.3.CSCsg41084 |\n|---------------------+-----------------+-----------------------------|\n| 3.3.3 | AA01785 | c12k-k9sec-3.3.3.CSCsg41084 |\n|---------------------+-----------------+-----------------------------|\n| 3.4.0 | AA01782 | c12k-k9sec-3.4.0.CSCsg41084 |\n|---------------------+-----------------+-----------------------------|\n| 3.4.0 | AA01795 | hfr-k9sec-3.4.0.CSCsg41084 |\n|---------------------+-----------------+-----------------------------|\n| 3.4.1 | AA01783 | c12k-k9sec-3.4.1.CSCsg41084 |\n|---------------------+-----------------+-----------------------------|\n| 3.4.1 | AA01794 | hfr-k9sec-3.4.1.CSCsg41084 |\n+---------------------------------------------------------------------+\n\nIOS XR Package Installation Envelopes (PIE) can be downloaded from File \nExchange at:\nhttps://upload.cisco.com/cgi-bin/swc/fileexg/main.cgi?CONTYPES=IOS-XR \nInstallation instructions are included in the accompanying .txt files. \n\nCisco PIX and ASA Security Appliance\n+-----------------------------------\n\nThis vulnerability is fixed in the following 7.x software releases: 7.0(6.7),\n7.1(2.27), 7.2(1.22), 7.2(2). All 8.x software releases do contain the fixed\nlibrary and are not affected. No 6.x software releases are affected by this\nvulnerability. \n\nCisco Firewall Service Module (FWSM)\n+-----------------------------------\n\nThis vulnerability is fixed in the following software releases:\n\n * 2.3(5) maintenance release, expected in 2007-June\n * 3.1(6) maintenance release, expected in 2007-June\n\nCisco Unified CallManager\n+------------------------\n\nThis vulnerability is fixed in the following software releases. \n\n * 4.0(x) releases are vulnerable but no fix will be provided. Customers are\n advised to upgrade to the fixed 4.1 or 4.2 software. \n * 4.1(3)sr.5 expected in 2007-May-24\n * 4.2(3)sr.2 expected in 2007-May\n * 4.3(1)sr.1 expected 2007-Jun\n * 5.0(4) - no fixed software planned, users should upgrade to 5.1(2)\n * 5.1(1) - no fixed software planned, users should upgrade to 5.1(2)\n * 5.1(2)\n\nWorkarounds\n===========\n\nThe only way to prevent a device being susceptible to the listed\nvulnerabilities is to disable the affected service(s). However, if regular\nmaintenance and operation of the device relies on these services then there is\nno workaround. \n\nIt is possible to mitigate these vulnerabilities by preventing\nunauthorized hosts to access the affected devices. Additional mitigations \nthat can be deployed on Cisco devices within the network are available \nin the Cisco Applied Intelligence companion document for this advisory:\n\nhttp://www.cisco.com/warp/ public/707/cisco-air-20070522-crypto.shtml\n\nControl Plane Policing (CoPP)\n+----------------------------\n\nControl Plane Policing: IOS software versions that support Control Plane\nPolicing (CoPP) can be configured to help protect the device from attacks that\ntarget the management and control planes. CoPP is available in Cisco IOS\nrelease trains 12.0S, 12.2SX, 12.2S, 12.3T, 12.4, and 12.4T. \n\nIn the CoPP example below, the ACL entries that match the exploit packets with\nthe permit action will be discarded by the policy-map drop function, while\npackets that match a deny action (not shown) are not affected by the policy-map\ndrop function. \n\n !-- Include deny statements up front for any protocols/ports/IP addresses that\n !-- should not be impacted by CoPP\n !-- Include permit statements for the protocols/ports that will be governed by CoPP\n !-- port 443 - HTTPS\n access-list 100 permit tcp any any eq 443\n !-- port 500 - IKE\n access-list 100 permit udp any any eq 500\n !-- port 848 - GDOI\n access-list 100 permit tcp any any eq 848\n !-- port 5060 - SIP-TLS\n access-list 100 permit tcp any any eq 5060\n !-- port 5354 - TIDP\n access-list 100 permit tcp any any eq 5354\n\n !-- Permit (Police or Drop)/Deny (Allow) all other Layer3 and Layer4\n !-- traffic in accordance with existing security policies and\n !-- configurations for traffic that is authorized to be sent\n !-- to infrastructure devices. \n !\n !-- Create a Class-Map for traffic to be policed by\n !-- the CoPP feature. \n !\n class-map match-all Drop-Known-Undesirable\n match access-group 100\n\n !\n !-- Create a Policy-Map that will be applied to the\n !-- Control-Plane of the device. \n !\n policy-map CoPP-Input-Policy\n class Drop-Known-Undesirable\n drop\n\n !-- Apply the Policy-Map to the Control-Plane of the\n !-- device. \n !\n control-plane\n service-policy input CoPP-Input-Policy\n\n\nPlease note that in the 12.0S, 12.2S, and 12.2SX Cisco IOS trains, the\npolicy-map syntax is different:\n\n policy-map CoPP-Input-Policy\n class Drop-Known-Undesirable\n police 32000 1500 1500 conform-action drop exceed-action drop\n\n\nNOTE: In the above CoPP example, the ACL entries with the \"permit\" action that\nmatch the exploit packets result in the discarding of those packets by the\npolicy-map drop function, while packets that match the \"deny\" action are not\naffected by the policy-map drop function. \n\nAdditional information on the configuration and use of the CoPP\nfeature can be found at \nhttp://www.cisco.com/en/US/products/ps6642/products_white_paper0900aecd804fa16a.shtml\nand \nhttp://www.cisco.com/en/US/products/sw/iosswrel/ps1838/products_feature_guide09186a008052446b.html\n\n\nAccess Control List (ACL)\n+------------------------\n\nAccess control lists can be used to help mitigate attacks that may try to\nexploit these vulnerabilities. This is done in a way that only packets from the\nlegitimate sources are allowed to reach the device and all others are dropped. \n\n access-list 101 permit tcp host \u003clegitimate_host_IP_address\u003e host \u003crouter_IP_address\u003e eq 443\n access-list 101 permit udp host \u003clegitimate_host_IP_address\u003e host \u003crouter_IP_address\u003e eq 500\n access-list 101 permit tcp host \u003clegitimate_host_IP_address\u003e host \u003crouter_IP_address\u003e eq 506\n access-list 101 permit tcp host \u003clegitimate_host_IP_address\u003e host \u003crouter_IP_address\u003e eq 4848\n access-list 101 permit tcp host \u003clegitimate_host_IP_address\u003e host \u003crouter_IP_address\u003e eq 5060\n access-list 101 permit tcp host \u003clegitimate_host_IP_address\u003e host \u003crouter_IP_address\u003e eq 5354\n access-list 101 deny tcp any any eq 443\n access-list 101 deny udp any any eq 500\n access-list 101 deny tcp any any eq 506\n access-list 101 deny udp any any eq 4848\n access-list 101 deny tcp any any eq 5060\n access-list 101 deny tcp any any eq 5354\n\n\nObtaining Fixed Software\n========================\n\nCisco has made free software available to address this vulnerability for\naffected customers. Prior to deploying software, customers should consult their\nmaintenance provider or check the software for feature set compatibility and\nknown 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/public/sw-license-agreement.html, or as otherwise\nset forth at Cisco.com Downloads at\nhttp://www.cisco.com/public/sw-center/sw-usingswc.shtml. \n\nDo not contact either \"psirt@cisco.com\" or \"security-alert@cisco.com\" for\nsoftware upgrades. \n\nCustomers with Service Contracts\n+-------------------------------\n\nCustomers with contracts should obtain upgraded software through their regular\nupdate channels. For most customers, this means that upgrades should be\nobtained through the Software Center on Cisco\u0027s worldwide website at \nhttp://www.cisco.com. \n\nCustomers using Third-party Support Organizations\n+------------------------------------------------\n\nCustomers whose Cisco products are provided or maintained through prior or\nexisting agreement with third-party support organizations such as Cisco\nPartners, authorized resellers, or service providers should contact that\nsupport organization for guidance and assistance with the appropriate course of\naction in regards to this advisory. \n\nThe effectiveness of any workaround or fix is dependent on specific customer\nsituations such as product mix, network topology, traffic behavior, and\norganizational mission. Due to the variety of affected products and releases,\ncustomers should consult with their service provider or support organization to\nensure any applied workaround or fix is the most appropriate for use in the\nintended network before it is deployed. \n\nCustomers without Service Contracts\n+----------------------------------\n\nCustomers who purchase direct from Cisco but who do not hold a Cisco service\ncontract and customers who purchase through third-party vendors but are\nunsuccessful at obtaining fixed software through their point of sale should get\ntheir upgrades by contacting the Cisco Technical Assistance Center (TAC). TAC\ncontacts 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\nHave your product serial number available and give the URL of this notice as\nevidence of your entitlement to a free upgrade. Free upgrades for non-contract\ncustomers must be requested through the TAC. \n\nRefer to http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml for\nadditional TAC contact information, including special localized telephone\nnumbers and instructions and e-mail addresses for use in various languages. \n\nExploitation and Public Announcements\n=====================================\n\nThe Cisco PSIRT is not aware of any public announcements or malicious use of\nthe vulnerability described in this Advisory. \n\nThis vulnerability was discovered by Cisco during internal testing. \n\nStatus of This Notice: Interim\n==============================\n\nTHIS DOCUMENT IS PROVIDED ON AN \"AS IS\" BASIS AND DOES NOT IMPLY ANY KIND OF\nGUARANTEE OR WARRANTY, INCLUDING THE WARRANTIES OF MERCHANTABILITY OR FITNESS\nFOR A PARTICULAR USE. YOUR USE OF THE INFORMATION ON THE DOCUMENT OR MATERIALS\nLINKED FROM THE DOCUMENT IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO\nCHANGE OR UPDATE THIS DOCUMENT AT ANY TIME. CISCO EXPECTS TO UPDATE THIS\nDOCUMENT AS NEW INFORMATION BECOMES AVAILABLE. \n\nA stand-alone copy or Paraphrase of the text of this document that omits the\ndistribution URL in the following section is an uncontrolled copy, and may lack\nimportant information or contain factual errors. \n\nDistribution\n============\n\nThis advisory is posted on Cisco\u0027s worldwide website at \nhttp://www.cisco.com/warp/public/707/cisco-sa-20070522-crypto.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 e-mail\nand Usenet news recipients. \n\n * cust-security-announce@cisco.com\n * first-teams@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 worldwide\nwebsite, but may or may not be actively announced on mailing lists or\nnewsgroups. Users concerned about this problem are encouraged to check the\nabove URL for any updates. \n\nRevision History\n================\n\n+---------------------------------------------------------------------+\n| Revision 1.0 | 2007-May-22 | Initial public release. |\n+---------------------------------------------------------------------+\n\nCisco Security Procedures\n=========================\n\nComplete information on reporting security vulnerabilities in Cisco products,\nobtaining assistance with security incidents, and registering to receive\nsecurity information from Cisco, is available on Cisco\u0027s worldwide website at\nhttp://www.cisco.com/en/US/products/products_security_vulnerability_policy.html\nThis includes instructions for press inquiries regarding Cisco security\nnotices. All Cisco security advisories are available at \nhttp://www.cisco.com/go/psirt. \n\n- -------------------------------------------------------------------------------\nAll contents are Copyright 2006-2007 Cisco Systems, Inc. All rights reserved. \n- -------------------------------------------------------------------------------\n\nUpdated: May 22, 2007 Document ID: 91890\n\n- -------------------------------------------------------------------------------\n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v1.4.2.2 (GNU/Linux)\n\niD8DBQFGUv7c8NUAbBmDaxQRAse8AJ9YwxPEprfhiJNzLVTLMXsTnTuWSwCghmmF\nqlrKeNA331DvYso6f2C5mRk=\n=dfTU\n-----END PGP SIGNATURE-----\n",
"sources": [
{
"db": "NVD",
"id": "CVE-2006-3894"
},
{
"db": "CERT/CC",
"id": "VU#754281"
},
{
"db": "JVNDB",
"id": "JVNDB-2007-000404"
},
{
"db": "BID",
"id": "24104"
},
{
"db": "VULHUB",
"id": "VHN-20002"
},
{
"db": "PACKETSTORM",
"id": "56911"
}
],
"trust": 2.79
},
"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-20002",
"trust": 0.1,
"type": "unknown"
}
],
"sources": [
{
"db": "VULHUB",
"id": "VHN-20002"
}
]
},
"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": "CERT/CC",
"id": "VU#754281",
"trust": 3.6
},
{
"db": "NVD",
"id": "CVE-2006-3894",
"trust": 2.9
},
{
"db": "BID",
"id": "24104",
"trust": 2.8
},
{
"db": "SECUNIA",
"id": "25364",
"trust": 2.5
},
{
"db": "SECUNIA",
"id": "25343",
"trust": 2.5
},
{
"db": "SECTRACK",
"id": "1018095",
"trust": 1.7
},
{
"db": "SECUNIA",
"id": "25399",
"trust": 1.7
},
{
"db": "OSVDB",
"id": "35338",
"trust": 1.7
},
{
"db": "VUPEN",
"id": "ADV-2007-1909",
"trust": 1.7
},
{
"db": "VUPEN",
"id": "ADV-2007-1908",
"trust": 1.7
},
{
"db": "VUPEN",
"id": "ADV-2007-1945",
"trust": 1.7
},
{
"db": "JVNDB",
"id": "JVNDB-2007-000404",
"trust": 0.8
},
{
"db": "CNNVD",
"id": "CNNVD-200705-446",
"trust": 0.6
},
{
"db": "PACKETSTORM",
"id": "56911",
"trust": 0.2
},
{
"db": "VULHUB",
"id": "VHN-20002",
"trust": 0.1
}
],
"sources": [
{
"db": "CERT/CC",
"id": "VU#754281"
},
{
"db": "VULHUB",
"id": "VHN-20002"
},
{
"db": "BID",
"id": "24104"
},
{
"db": "JVNDB",
"id": "JVNDB-2007-000404"
},
{
"db": "PACKETSTORM",
"id": "56911"
},
{
"db": "NVD",
"id": "CVE-2006-3894"
},
{
"db": "CNNVD",
"id": "CNNVD-200705-446"
}
]
},
"id": "VAR-200705-0570",
"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-20002"
}
],
"trust": 0.578125
},
"last_update_date": "2023-12-18T11:04:50.780000Z",
"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-20070522-crypto",
"trust": 0.8,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20070522-crypto.shtml"
},
{
"title": "\u682a\u5f0f\u4f1a\u793e\u30bd\u30cb\u30fc\u30fb\u30b3\u30f3\u30d4\u30e5\u30fc\u30bf\u30a8\u30f3\u30bf\u30c6\u30a4\u30f3\u30e1\u30f3\u30c8\u304b\u3089\u306e\u60c5\u5831",
"trust": 0.8,
"url": "http://jvn.jp/cert/jvnvu%23754281/281799/index.html"
},
{
"title": "PSP(R) \u30b7\u30b9\u30c6\u30e0\u30bd\u30d5\u30c8\u30a6\u30a7\u30a2\u30a2\u30c3\u30d7\u30c7\u30fc\u30c8",
"trust": 0.8,
"url": "http://www.jp.playstation.com/psp/update/ud_01.html"
},
{
"title": "PLAYSTATION(R) \u30b7\u30b9\u30c6\u30e0\u30bd\u30d5\u30c8\u30a6\u30a7\u30a2\u30a2\u30c3\u30d7\u30c7\u30fc\u30c8",
"trust": 0.8,
"url": "http://www.jp.playstation.com/ps3/update/index.html"
},
{
"title": "RSA BSAFE Cert-C",
"trust": 0.8,
"url": "http://www.rsa.com/japan/products/bsafe/cert-c.html"
},
{
"title": "RSA BSAFE Crypto-C",
"trust": 0.8,
"url": "http://www.rsa.com/japan/products/bsafe/crypto-c.html"
},
{
"title": "\u8a3c\u660e\u66f8\u306e\u64cd\u4f5c\u306b\u95a2\u3059\u308b\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u4e0a\u306e\u8106\u5f31\u6027",
"trust": 0.8,
"url": "http://software.fujitsu.com/jp/security/products-fujitsu/solution/teamware2007_02.html"
},
{
"title": "VU#754281",
"trust": 0.8,
"url": "http://software.fujitsu.com/jp/security/vulnerabilities/vu754281.html"
},
{
"title": "DELL RSA BSAFE Crypto-C Micro Edition Security vulnerabilities",
"trust": 0.6,
"url": "http://www.cnnvd.org.cn/web/xxk/bdxqbyid.tag?id=173772"
}
],
"sources": [
{
"db": "JVNDB",
"id": "JVNDB-2007-000404"
},
{
"db": "CNNVD",
"id": "CNNVD-200705-446"
}
]
},
"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
}
],
"sources": [
{
"db": "NVD",
"id": "CVE-2006-3894"
}
]
},
"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/24104"
},
{
"trust": 2.5,
"url": "http://jvn.jp/cert/jvnvu%23754281/index.html"
},
{
"trust": 2.0,
"url": "http://www.kb.cert.org/vuls/id/754281"
},
{
"trust": 2.0,
"url": "https://secure-support.novell.com/kanisaplatform/publishing/97/3590033_f.sal_public.html"
},
{
"trust": 1.7,
"url": "http://www.cisco.com/en/us/products/products_security_advisory09186a0080847c5d.shtml"
},
{
"trust": 1.7,
"url": "http://osvdb.org/35338"
},
{
"trust": 1.7,
"url": "https://oval.cisecurity.org/repository/search/definition/oval%3aorg.mitre.oval%3adef%3a5778"
},
{
"trust": 1.7,
"url": "http://www.securitytracker.com/id?1018095"
},
{
"trust": 1.7,
"url": "http://secunia.com/advisories/25343"
},
{
"trust": 1.7,
"url": "http://secunia.com/advisories/25364"
},
{
"trust": 1.7,
"url": "http://secunia.com/advisories/25399"
},
{
"trust": 1.7,
"url": "http://www.vupen.com/english/advisories/2007/1908"
},
{
"trust": 1.7,
"url": "http://www.vupen.com/english/advisories/2007/1909"
},
{
"trust": 1.7,
"url": "http://www.vupen.com/english/advisories/2007/1945"
},
{
"trust": 1.7,
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/34430"
},
{
"trust": 1.1,
"url": "http://www.rsa.com/node.aspx?id=1204"
},
{
"trust": 0.8,
"url": "http://secunia.com/advisories/25364/"
},
{
"trust": 0.8,
"url": "http://cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2006-3894"
},
{
"trust": 0.8,
"url": "http://www.cpni.gov.uk/products/advisories/default.aspx?id=al-20070522-137.xml"
},
{
"trust": 0.8,
"url": "http://www.frsirt.com/english/advisories/2007/1908"
},
{
"trust": 0.8,
"url": "http://www.jpcert.or.jp/wr/2007/wr072001.txt"
},
{
"trust": 0.8,
"url": "http://www.jpcert.or.jp/at/2007/at070013.txt"
},
{
"trust": 0.8,
"url": "http://nvd.nist.gov/nvd.cfm?cvename=cve-2006-3894"
},
{
"trust": 0.8,
"url": "http://secunia.com/advisories/25343/"
},
{
"trust": 0.8,
"url": "http://www.kb.cert.org/vuls/id/754281/"
},
{
"trust": 0.4,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20070522-crypto.shtml"
},
{
"trust": 0.3,
"url": "http://www.rsa.com/"
},
{
"trust": 0.3,
"url": "http://tools.cisco.com/security/center/content/ciscosecurityadvisory/cisco-sa-20151130-csr"
},
{
"trust": 0.3,
"url": "http://www116.nortelnetworks.com/pub/repository/clarify/document/2007/21/022317-01.pdf"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/go/psirt"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/en/us/products/sw/iosswrel/ps1838/products_feature_guide09186a008052446b.html"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20070522-ssl.shtml"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/web/about/security/intelligence/cvss-qandas.html."
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/public/sw-license-agreement.html,"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/en/us/products/ps6642/products_white_paper0900aecd804fa16a.shtml"
},
{
"trust": 0.1,
"url": "http://intellishield.cisco.com/security/alertmanager/cvss."
},
{
"trust": 0.1,
"url": "http://www.cisco.com/go/psirt."
},
{
"trust": 0.1,
"url": "https://upload.cisco.com/cgi-bin/swc/fileexg/main.cgi?contypes=ios-xr"
},
{
"trust": 0.1,
"url": "https://nvd.nist.gov/vuln/detail/cve-2006-3894"
},
{
"trust": 0.1,
"url": "http://www.cisco.com."
},
{
"trust": 0.1,
"url": "http://www.cisco.com"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20070522-crypto.shtml."
},
{
"trust": 0.1,
"url": "http://www.cisco.com/public/sw-center/sw-usingswc.shtml."
},
{
"trust": 0.1,
"url": "http://www.cisco.com/en/us/products/products_security_vulnerability_policy.html"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/en/us/products/sw/iosswrel/ps1828/products_white_paper09186a008018305e.shtml"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/en/us/products/sw/iosswrel/ps1828/products_white_paper09186a008018305e.shtml."
},
{
"trust": 0.1,
"url": "http://www.cisco.com/techsupport"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/public/687/directory/dirtac.shtml"
}
],
"sources": [
{
"db": "CERT/CC",
"id": "VU#754281"
},
{
"db": "VULHUB",
"id": "VHN-20002"
},
{
"db": "BID",
"id": "24104"
},
{
"db": "JVNDB",
"id": "JVNDB-2007-000404"
},
{
"db": "PACKETSTORM",
"id": "56911"
},
{
"db": "NVD",
"id": "CVE-2006-3894"
},
{
"db": "CNNVD",
"id": "CNNVD-200705-446"
}
]
},
"sources": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#",
"data": {
"@container": "@list"
}
},
"data": [
{
"db": "CERT/CC",
"id": "VU#754281"
},
{
"db": "VULHUB",
"id": "VHN-20002"
},
{
"db": "BID",
"id": "24104"
},
{
"db": "JVNDB",
"id": "JVNDB-2007-000404"
},
{
"db": "PACKETSTORM",
"id": "56911"
},
{
"db": "NVD",
"id": "CVE-2006-3894"
},
{
"db": "CNNVD",
"id": "CNNVD-200705-446"
}
]
},
"sources_release_date": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources_release_date#",
"data": {
"@container": "@list"
}
},
"data": [
{
"date": "2007-05-22T00:00:00",
"db": "CERT/CC",
"id": "VU#754281"
},
{
"date": "2007-05-22T00:00:00",
"db": "VULHUB",
"id": "VHN-20002"
},
{
"date": "2007-05-22T00:00:00",
"db": "BID",
"id": "24104"
},
{
"date": "2007-06-06T00:00:00",
"db": "JVNDB",
"id": "JVNDB-2007-000404"
},
{
"date": "2007-05-23T05:09:57",
"db": "PACKETSTORM",
"id": "56911"
},
{
"date": "2007-05-22T19:30:00",
"db": "NVD",
"id": "CVE-2006-3894"
},
{
"date": "2007-05-22T00:00:00",
"db": "CNNVD",
"id": "CNNVD-200705-446"
}
]
},
"sources_update_date": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources_update_date#",
"data": {
"@container": "@list"
}
},
"data": [
{
"date": "2007-12-19T00:00:00",
"db": "CERT/CC",
"id": "VU#754281"
},
{
"date": "2021-12-09T00:00:00",
"db": "VULHUB",
"id": "VHN-20002"
},
{
"date": "2007-06-29T18:58:00",
"db": "BID",
"id": "24104"
},
{
"date": "2007-06-20T00:00:00",
"db": "JVNDB",
"id": "JVNDB-2007-000404"
},
{
"date": "2021-12-17T20:00:11.030000",
"db": "NVD",
"id": "CVE-2006-3894"
},
{
"date": "2021-12-10T00:00:00",
"db": "CNNVD",
"id": "CNNVD-200705-446"
}
]
},
"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-200705-446"
}
],
"trust": 0.6
},
"title": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/title#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "RSA BSAFE libraries denial of service vulnerability",
"sources": [
{
"db": "CERT/CC",
"id": "VU#754281"
}
],
"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-200705-446"
}
],
"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.