var-201007-0200
Vulnerability from variot
IOS 12.2(52)SE and 12.2(52)SE1 on Cisco Industrial Ethernet (IE) 3000 series switches has (1) a community name of public for RO access and (2) a community name of private for RW access, which makes it easier for remote attackers to modify the configuration or obtain potentially sensitive information via SNMP requests, aka Bug ID CSCtf25589. An remote attacker could take full control of a vulnerable device. Cisco Provided by Cisco Industrial Ethernet 3000 Set to series SNMP Community String May be used by remote third parties. Cisco IOS Software release 12.2(52)SE Or 12.2(52)SE1 Using Cisco Industrial Ethernet 3000 The series SNMP Community String Is hard-coded. In addition, when the product is restarted, the hard-coded value is set again. In addition, SNMP The service is disabled by default.SNMP Community String Without changing Cisco Industrial Ethernet 3000 When operating the series, the setting of the corresponding product may be changed by a remote third party. This issue is tracked by Cisco Bug ID CSCtf25589. ----------------------------------------------------------------------
Passionate about writing secure code?
http://secunia.com/company/jobs/open_positions/talented_programmer
Read this if your favourite tool is a disassembler
http://secunia.com/company/jobs/open_positions/reverse_engineer
TITLE: Cisco Industrial Ethernet 3000 Hardcoded SNMP Community Names
SECUNIA ADVISORY ID: SA40407
VERIFY ADVISORY: Secunia.com http://secunia.com/advisories/40407/ Customer Area (Credentials Required) https://ca.secunia.com/?page=viewadvisory&vuln_id=40407
RELEASE DATE: 2010-07-08
DISCUSS ADVISORY: http://secunia.com/advisories/40407/#comments
AVAILABLE ON SITE AND IN CUSTOMER AREA: * Last Update * Popularity * Comments * Criticality Level * Impact * Where * Solution Status * Operating System / Software * CVE Reference(s)
http://secunia.com/advisories/40407/
ONLY AVAILABLE IN CUSTOMER AREA: * Authentication Level * Report Reliability * Secunia PoC * Secunia Analysis * Systems Affected * Approve Distribution * Remediation Status * Secunia CVSS Score * CVSS
https://ca.secunia.com/?page=viewadvisory&vuln_id=40407
ONLY AVAILABLE WITH SECUNIA CSI AND SECUNIA PSI: * AUTOMATED SCANNING
http://secunia.com/vulnerability_scanning/personal/ http://secunia.com/vulnerability_scanning/corporate/wsus_sccm_3rd_third_party_patching/
DESCRIPTION: A security issue has been reported in Cisco Industrial Ethernet 3000, which can be exploited by malicious people to potentially compromise a vulnerable device. This can be exploited to e.g.
Successful exploitation requires that the SNMP service is enabled (disabled by default).
Further details available in Customer Area: http://secunia.com/products/corporate/EVM/
PROVIDED AND/OR DISCOVERED BY: Reported by the vendor.
ORIGINAL ADVISORY: http://www.cisco.com/warp/public/707/cisco-sa-20100707-snmp.shtml
OTHER REFERENCES: Further details available in Customer Area: http://secunia.com/products/corporate/EVM/
DEEP LINKS: Further details available in Customer Area: http://secunia.com/products/corporate/EVM/
EXTENDED DESCRIPTION: Further details available in Customer Area: http://secunia.com/products/corporate/EVM/
EXTENDED SOLUTION: Further details available in Customer Area: http://secunia.com/products/corporate/EVM/
EXPLOIT: Further details available in Customer Area: http://secunia.com/products/corporate/EVM/
About: This Advisory was delivered by Secunia as a free service to help private users keeping their systems up to date against the latest vulnerabilities.
Subscribe: http://secunia.com/advisories/secunia_security_advisories/
Definitions: (Criticality, Where etc.) http://secunia.com/advisories/about_secunia_advisories/
Please Note: Secunia recommends that you verify all advisories you receive by clicking the link. Secunia NEVER sends attached files with advisories. Secunia does not advise people to install third party patches, only use those supplied by the vendor.
Unsubscribe: Secunia Security Advisories http://secunia.com/sec_adv_unsubscribe/?email=packet%40packetstormsecurity.org
.
Cisco has released free software updates that address this vulnerability.
Workarounds that mitigate this vulnerability are available.
SNMP is used for managing and monitoring the device and community names are the equivalent to a password. Cisco has provided a workaround that ensures the community names are removed when the device reloads. Once the device is reloaded the original configuration is inserted without the access lists or mib views assigned to the community names. Consult the workarounds section of this advisory.
This vulnerability was introduced as part of a new feature integrated into the affected releases called PROFINET. This vulnerability has been assigned Common Vulnerabilities and Exposures (CVE) ID CVE-2010-1574.
Vulnerability Scoring Details
Cisco has provided scores for the vulnerability in this advisory based on the Common Vulnerability Scoring System (CVSS). The CVSS scoring in this Security Advisory is done in accordance with CVSS version 2.0.
CVSS is a standards-based scoring method that conveys vulnerability severity and helps determine urgency and priority of response.
Cisco has provided a base and temporal score. Customers can then compute environmental scores to assist in determining the impact of the vulnerability in individual networks.
Cisco has provided 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
CSCtf25589 - Hard-coded SNMP Community Names in Cisco Industrial Ethernet 3000 Series
CVSS Base Score - 10
Access Vector - Network Access Complexity - Low Authentication - None Confidentiality Impact - Complete Integrity Impact - Complete Availability Impact - Complete
CVSS Temporal Score - 8.3
Exploitability - Functional Remediation Level - Official-Fix Report Confidence - Confirmed
Impact
Successful exploitation of the vulnerability could result in an attacker obtaining full control of the device.
Software Versions and Fixes
When considering software upgrades, 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 ensure 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. If a given release train is vulnerable, then the earliest possible releases that contain the fix (along with the anticipated date of availability for each, if applicable) are listed in the "First Fixed Release" column of the table. 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. Cisco recommends upgrading to a release equal to or later than the release specified in the "First Fixed Release" column of the table.
+-------------------------------------------------------------------+ | Major | Availability of Repaired Releases | | Release | | |--------------+----------------------------------------------------| | Affected | | | 12.0-Based | First Fixed Release | | Releases | | |-------------------------------------------------------------------| | There are no affected 12.0 based releases | |-------------------------------------------------------------------| | Affected | | | 12.1-Based | First Fixed Release | | Releases | | |-------------------------------------------------------------------| | There are no affected 12.1 based releases | |-------------------------------------------------------------------| | Affected | | | 12.2-Based | First Fixed Release | | Releases | | |--------------+----------------------------------------------------| | | Releases prior to 12.2(52)SE are not vulnerable. | | 12.2SE | First fixed in release 12.2(55)SE. Currently | | | scheduled to be available August 2010. | |-------------------------------------------------------------------| | There are no other affected 12.2 based releases | |-------------------------------------------------------------------| | Affected | | | 12.3-Based | First Fixed Release | | Releases | | |-------------------------------------------------------------------| | There are no affected 12.3 based releases | |-------------------------------------------------------------------| | Affected | | | 12.4-Based | First Fixed Release | | Releases | | |-------------------------------------------------------------------| | There are no affected 12.4 based releases | |-------------------------------------------------------------------| | Affected | | | 15.0-Based | First Fixed Release | | Releases | | |-------------------------------------------------------------------| | There are no affected 15.0 based releases | |-------------------------------------------------------------------| | Affected | | | 15.1-Based | First Fixed Release | | Releases | | |-------------------------------------------------------------------| | There are no affected 15.1 based releases | +-------------------------------------------------------------------+
Workarounds
Manually Remove SNMP Community Names +-----------------------------------
Note: The following workaround is only effective until the device is reloaded. Upon each reload of the device this workaround must be re-applied.
Log in to the device, and enter configuration mode. This workaround must be applied each time the device is reloaded.
Automatically Remove SNMP Community Names +----------------------------------------
By creating an Embedded Event Manager (EEM) policy, it is possible to automatically remove the hard-coded SNMP community names each time the device is reloaded. The following example shows an EEM policy that runs each time the device is reloaded and removes the hard-coded SNMP community names.
event manager applet cisco-sa-20100707-snmp
event timer countdown time 30
action 10 cli command "enable"
action 20 cli command "configure terminal"
action 30 cli command "no snmp-server community public RO"
action 40 cli command "no snmp-server community private RW"
action 50 cli command "end"
action 60 cli command "disable"
action 70 syslog msg "Hard-coded SNMP community names as per Cisco Security Advisory cisco-sa-20100707-snmp removed"
For more information on EEM policies consult the Cisco IOS Network Management Configuration Guide - Embedded Event Manager Overview at the following link:
http://www.cisco.com/en/US/docs/ios/netmgmt/configuration/guide/nm_eem_overview_ps6441_TSD_Products_Configuration_Guide_Chapter.html
Infrastructure Access Control Lists +----------------------------------
Although it is often difficult to block traffic that transits a network, it is possible to identify traffic that should never be allowed to target infrastructure devices and block that traffic at the device interface or the border of networks.
If SNMP management is not required on the IE3000, then dropping all SNMP traffic to the device is a sufficient workaround. The iACL below shows an example of an IE3000 with two interfaces configured with layer 3 access, dropping all SNMP queries destined to the IE3000:
!---
!--- Deny SNMP traffic from all other sources destined to
!--- configured IP addresses on the IE3000.
!---
access-list 150 deny udp any host 192.168.0.1 eq snmp
access-list 150 deny udp any host 192.168.1.1 eq snmp
!---
!--- Permit/deny all other Layer 3 and Layer 4 traffic in
!--- accordance with existing security policies and configurations
!--- Permit all other traffic to transit the device.
!---
access-list 150 permit ip any any
!---
!--- Apply access-list to all Layer 3 interfaces
!--- (only two examples shown)
!---
interface Vlan1
ip address 192.168.0.1 255.255.255.0
ip access-group 150 in
interface GigabitEthernet1/1
ip address 192.168.1.1 255.255.255.0
ip access-group 150 in
The white paper "Protecting Your Core: Infrastructure Protection Access Control Lists" presents guidelines and recommended deployment techniques for infrastructure protection access lists. This white paper can be obtained at the following link:
http://www.cisco.com/en/US/tech/tk648/tk361/technologies_white_paper09186a00801a1a55.shtml
Obtaining Fixed Software
Cisco has released free software updates that address this vulnerability. Prior to deploying software, customers should consult their maintenance provider or check the software for feature set compatibility and known issues specific to their environment.
Customers may only install and expect support for the feature sets they have purchased. By installing, downloading, accessing or otherwise using such software upgrades, customers agree to be bound by the terms of Cisco's software license terms found at:
http://www.cisco.com/en/US/docs/general/warranty/English/EU1KEN_.html
or as otherwise set forth at Cisco.com Downloads at:
http://www.cisco.com/public/sw-center/sw-usingswc.shtml
Do not contact psirt@cisco.com or security-alert@cisco.com for software upgrades.
Customers with Service Contracts +-------------------------------
Customers with contracts should obtain upgraded software through their regular update channels. For most customers, this means that upgrades should be obtained through the Software Center on Cisco's worldwide website at http://www.cisco.com.
Customers using Third Party Support Organizations +------------------------------------------------
Customers whose Cisco products are provided or maintained through prior or existing agreements with third-party support organizations, such as Cisco Partners, authorized resellers, or service providers should contact that support organization for guidance and assistance with the appropriate course of action in regards to this advisory.
The effectiveness of any workaround or fix is dependent on specific customer situations, such as product mix, network topology, traffic behavior, and organizational mission. Due to the variety of affected products and releases, customers should consult with their service provider or support organization to ensure any applied workaround or fix is the most appropriate for use in the intended network before it is deployed.
Customers without Service Contracts +----------------------------------
Customers who purchase direct from Cisco but do not hold a Cisco service contract, and customers who purchase through third-party vendors but are unsuccessful in obtaining fixed software through their point of sale should acquire upgrades by contacting the Cisco Technical Assistance Center (TAC). TAC contacts are as follows.
- +1 800 553 2447 (toll free from within North America)
- +1 408 526 7209 (toll call from anywhere in the world)
- e-mail: tac@cisco.com
Customers should have their product serial number available and be prepared to give the URL of this notice as evidence of entitlement to a free upgrade. Free upgrades for non-contract customers must be requested through the TAC.
Refer to:
http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html
for additional TAC contact information, including localized telephone numbers, and instructions and e-mail addresses for use in various languages.
Exploitation and Public Announcements
The Cisco PSIRT is not aware of any public announcements or malicious use of the vulnerability described in this advisory.
This vulnerability was discovered when handling customer support calls.
Status of this Notice: FINAL
THIS DOCUMENT IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR USE. YOUR USE OF THE INFORMATION ON THE DOCUMENT OR MATERIALS LINKED FROM THE DOCUMENT IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS DOCUMENT AT ANY TIME.
A stand-alone copy or Paraphrase of the text of this document that omits the distribution URL in the following section is an uncontrolled copy, and may lack important information or contain factual errors.
Distribution
This advisory is posted on Cisco's worldwide website at:
http://www.cisco.com/warp/public/707/cisco-sa-20100707-snmp.shtml
In addition to worldwide web posting, a text version of this notice is clear-signed with the Cisco PSIRT PGP key and is posted to the following e-mail and Usenet news recipients.
- cust-security-announce@cisco.com
- first-bulletins@lists.first.org
- bugtraq@securityfocus.com
- vulnwatch@vulnwatch.org
- cisco@spot.colorado.edu
- cisco-nsp@puck.nether.net
- full-disclosure@lists.grok.org.uk
- comp.dcom.sys.cisco@newsgate.cisco.com
Future updates of this advisory, if any, will be placed on Cisco's worldwide website, but may or may not be actively announced on mailing lists or newsgroups. Users concerned about this problem are encouraged to check the above URL for any updates.
Revision History
+---------------------------------------+ | Revision | | Initial | | 1.0 | 2010-July-07 | 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 -----BEGIN PGP SIGNATURE-----
iD8DBQFMNJS386n/Gc8U/uARAmN5AJsGyv7GXrtcrfddAeeDa6U8ZeYhyQCcCIkj EnlJFTHJ1iEyqh41bdAq0so= =qocW -----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-201007-0200",
"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.6,
"vendor": "cisco",
"version": "12.2\\(52\\)se1"
},
{
"model": "ios",
"scope": "eq",
"trust": 1.6,
"vendor": "cisco",
"version": "12.2\\(52\\)se"
},
{
"model": "industrial ethernet 3000",
"scope": "eq",
"trust": 1.0,
"vendor": "cisco",
"version": "*"
},
{
"model": "ios 12.2 se",
"scope": null,
"trust": 0.9,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2 se1",
"scope": null,
"trust": 0.9,
"vendor": "cisco",
"version": null
},
{
"model": null,
"scope": null,
"trust": 0.8,
"vendor": "cisco",
"version": null
},
{
"model": "industrial ethernet 3000 series",
"scope": null,
"trust": 0.8,
"vendor": "cisco",
"version": null
},
{
"model": "ios",
"scope": "eq",
"trust": 0.8,
"vendor": "cisco",
"version": "12.2 (52)se"
},
{
"model": "ios",
"scope": "eq",
"trust": 0.8,
"vendor": "cisco",
"version": "12.2 (52)se1"
},
{
"model": "ios",
"scope": "eq",
"trust": 0.8,
"vendor": "cisco",
"version": "12.2 (55)se"
},
{
"model": "industrial ethernet",
"scope": "eq",
"trust": 0.6,
"vendor": "cisco",
"version": "3000"
},
{
"model": "industrial ethernet series switches",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "30000"
},
{
"model": "ios 12.2 se",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "12.2 se",
"scope": null,
"trust": 0.2,
"vendor": "ios",
"version": null
},
{
"model": "12.2 se1",
"scope": null,
"trust": 0.2,
"vendor": "ios",
"version": null
},
{
"model": null,
"scope": "eq",
"trust": 0.2,
"vendor": "industrial ethernet 3000",
"version": "*"
}
],
"sources": [
{
"db": "IVD",
"id": "0c83a6ea-2356-11e6-abef-000c29c66e3d"
},
{
"db": "CERT/CC",
"id": "VU#732671"
},
{
"db": "CNVD",
"id": "CNVD-2010-1291"
},
{
"db": "BID",
"id": "41436"
},
{
"db": "JVNDB",
"id": "JVNDB-2010-001731"
},
{
"db": "CNNVD",
"id": "CNNVD-201007-058"
},
{
"db": "NVD",
"id": "CVE-2010-1574"
}
]
},
"configurations": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/configurations#",
"children": {
"@container": "@list"
},
"cpe_match": {
"@container": "@list"
},
"data": {
"@container": "@list"
},
"nodes": {
"@container": "@list"
}
},
"data": [
{
"CVE_data_version": "4.0",
"nodes": [
{
"cpe_match": [
{
"cpe22Uri": "cpe:/h:cisco:industrial_ethernet_3000",
"vulnerable": true
},
{
"cpe22Uri": "cpe:/o:cisco:ios",
"vulnerable": true
}
],
"operator": "OR"
}
]
}
],
"sources": [
{
"db": "JVNDB",
"id": "JVNDB-2010-001731"
}
]
},
"credits": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/credits#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "Cisco",
"sources": [
{
"db": "BID",
"id": "41436"
},
{
"db": "CNNVD",
"id": "CNNVD-201007-058"
}
],
"trust": 0.9
},
"cve": "CVE-2010-1574",
"cvss": {
"@context": {
"cvssV2": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/cvss/cvssV2#"
},
"@id": "https://www.variotdbs.pl/ref/cvss/cvssV2"
},
"cvssV3": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/cvss/cvssV3#"
},
"@id": "https://www.variotdbs.pl/ref/cvss/cvssV3/"
},
"severity": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/cvss/severity#"
},
"@id": "https://www.variotdbs.pl/ref/cvss/severity"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
},
"@id": "https://www.variotdbs.pl/ref/sources"
}
},
"data": [
{
"cvssV2": [
{
"accessComplexity": "LOW",
"accessVector": "NETWORK",
"authentication": "NONE",
"author": "nvd@nist.gov",
"availabilityImpact": "COMPLETE",
"baseScore": 10.0,
"confidentialityImpact": "COMPLETE",
"exploitabilityScore": 10.0,
"id": "CVE-2010-1574",
"impactScore": 10.0,
"integrityImpact": "COMPLETE",
"severity": "HIGH",
"trust": 1.8,
"vectorString": "AV:N/AC:L/Au:N/C:C/I:C/A:C",
"version": "2.0"
},
{
"accessComplexity": "LOW",
"accessVector": "NETWORK",
"authentication": "NONE",
"author": "IVD",
"availabilityImpact": "COMPLETE",
"baseScore": 10.0,
"confidentialityImpact": "COMPLETE",
"exploitabilityScore": 10.0,
"id": "0c83a6ea-2356-11e6-abef-000c29c66e3d",
"impactScore": 10.0,
"integrityImpact": "COMPLETE",
"severity": "HIGH",
"trust": 0.2,
"vectorString": "AV:N/AC:L/Au:N/C:C/I:C/A:C",
"version": "2.9 [IVD]"
},
{
"accessComplexity": "LOW",
"accessVector": "NETWORK",
"authentication": "NONE",
"author": "VULHUB",
"availabilityImpact": "COMPLETE",
"baseScore": 10.0,
"confidentialityImpact": "COMPLETE",
"exploitabilityScore": 10.0,
"id": "VHN-44179",
"impactScore": 10.0,
"integrityImpact": "COMPLETE",
"severity": "HIGH",
"trust": 0.1,
"vectorString": "AV:N/AC:L/AU:N/C:C/I:C/A:C",
"version": "2.0"
}
],
"cvssV3": [],
"severity": [
{
"author": "nvd@nist.gov",
"id": "CVE-2010-1574",
"trust": 1.0,
"value": "HIGH"
},
{
"author": "CARNEGIE MELLON",
"id": "VU#732671",
"trust": 0.8,
"value": "5.93"
},
{
"author": "NVD",
"id": "CVE-2010-1574",
"trust": 0.8,
"value": "High"
},
{
"author": "CNNVD",
"id": "CNNVD-201007-058",
"trust": 0.6,
"value": "CRITICAL"
},
{
"author": "IVD",
"id": "0c83a6ea-2356-11e6-abef-000c29c66e3d",
"trust": 0.2,
"value": "CRITICAL"
},
{
"author": "VULHUB",
"id": "VHN-44179",
"trust": 0.1,
"value": "HIGH"
}
]
}
],
"sources": [
{
"db": "IVD",
"id": "0c83a6ea-2356-11e6-abef-000c29c66e3d"
},
{
"db": "CERT/CC",
"id": "VU#732671"
},
{
"db": "VULHUB",
"id": "VHN-44179"
},
{
"db": "JVNDB",
"id": "JVNDB-2010-001731"
},
{
"db": "CNNVD",
"id": "CNNVD-201007-058"
},
{
"db": "NVD",
"id": "CVE-2010-1574"
}
]
},
"description": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/description#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "IOS 12.2(52)SE and 12.2(52)SE1 on Cisco Industrial Ethernet (IE) 3000 series switches has (1) a community name of public for RO access and (2) a community name of private for RW access, which makes it easier for remote attackers to modify the configuration or obtain potentially sensitive information via SNMP requests, aka Bug ID CSCtf25589. An remote attacker could take full control of a vulnerable device. Cisco Provided by Cisco Industrial Ethernet 3000 Set to series SNMP Community String May be used by remote third parties. Cisco IOS Software release 12.2(52)SE Or 12.2(52)SE1 Using Cisco Industrial Ethernet 3000 The series SNMP Community String Is hard-coded. In addition, when the product is restarted, the hard-coded value is set again. In addition, SNMP The service is disabled by default.SNMP Community String Without changing Cisco Industrial Ethernet 3000 When operating the series, the setting of the corresponding product may be changed by a remote third party. This issue is tracked by Cisco Bug ID CSCtf25589. ----------------------------------------------------------------------\n\n\nPassionate about writing secure code?\n\nhttp://secunia.com/company/jobs/open_positions/talented_programmer\n\n\nRead this if your favourite tool is a disassembler\n\nhttp://secunia.com/company/jobs/open_positions/reverse_engineer\n\n\n----------------------------------------------------------------------\n\nTITLE:\nCisco Industrial Ethernet 3000 Hardcoded SNMP Community Names\n\nSECUNIA ADVISORY ID:\nSA40407\n\nVERIFY ADVISORY:\nSecunia.com\nhttp://secunia.com/advisories/40407/\nCustomer Area (Credentials Required)\nhttps://ca.secunia.com/?page=viewadvisory\u0026vuln_id=40407\n\nRELEASE DATE:\n2010-07-08\n\nDISCUSS ADVISORY:\nhttp://secunia.com/advisories/40407/#comments\n\nAVAILABLE ON SITE AND IN CUSTOMER AREA:\n * Last Update\n * Popularity\n * Comments\n * Criticality Level\n * Impact\n * Where\n * Solution Status\n * Operating System / Software\n * CVE Reference(s)\n\nhttp://secunia.com/advisories/40407/\n\nONLY AVAILABLE IN CUSTOMER AREA:\n * Authentication Level\n * Report Reliability\n * Secunia PoC\n * Secunia Analysis\n * Systems Affected\n * Approve Distribution\n * Remediation Status\n * Secunia CVSS Score\n * CVSS\n\nhttps://ca.secunia.com/?page=viewadvisory\u0026vuln_id=40407\n\nONLY AVAILABLE WITH SECUNIA CSI AND SECUNIA PSI:\n * AUTOMATED SCANNING\n\nhttp://secunia.com/vulnerability_scanning/personal/\nhttp://secunia.com/vulnerability_scanning/corporate/wsus_sccm_3rd_third_party_patching/\n\nDESCRIPTION:\nA security issue has been reported in Cisco Industrial Ethernet 3000,\nwhich can be exploited by malicious people to potentially compromise a\nvulnerable device. This can be exploited to e.g. \n\nSuccessful exploitation requires that the SNMP service is enabled\n(disabled by default). \n\nFurther details available in Customer Area:\nhttp://secunia.com/products/corporate/EVM/\n\nPROVIDED AND/OR DISCOVERED BY:\nReported by the vendor. \n\nORIGINAL ADVISORY:\nhttp://www.cisco.com/warp/public/707/cisco-sa-20100707-snmp.shtml\n\nOTHER REFERENCES:\nFurther details available in Customer Area:\nhttp://secunia.com/products/corporate/EVM/\n\nDEEP LINKS:\nFurther details available in Customer Area:\nhttp://secunia.com/products/corporate/EVM/\n\nEXTENDED DESCRIPTION:\nFurther details available in Customer Area:\nhttp://secunia.com/products/corporate/EVM/\n\nEXTENDED SOLUTION:\nFurther details available in Customer Area:\nhttp://secunia.com/products/corporate/EVM/\n\nEXPLOIT:\nFurther details available in Customer Area:\nhttp://secunia.com/products/corporate/EVM/\n\n----------------------------------------------------------------------\n\nAbout:\nThis Advisory was delivered by Secunia as a free service to help\nprivate users keeping their systems up to date against the latest\nvulnerabilities. \n\nSubscribe:\nhttp://secunia.com/advisories/secunia_security_advisories/\n\nDefinitions: (Criticality, Where etc.)\nhttp://secunia.com/advisories/about_secunia_advisories/\n\n\nPlease Note:\nSecunia recommends that you verify all advisories you receive by\nclicking the link. \nSecunia NEVER sends attached files with advisories. \nSecunia does not advise people to install third party patches, only\nuse those supplied by the vendor. \n\n----------------------------------------------------------------------\n\nUnsubscribe: Secunia Security Advisories\nhttp://secunia.com/sec_adv_unsubscribe/?email=packet%40packetstormsecurity.org\n\n----------------------------------------------------------------------\n\n\n. \n\nCisco has released free software updates that address this\nvulnerability. \n\nWorkarounds that mitigate this vulnerability are available. \n\nSNMP is used for managing and monitoring the device and community\nnames are the equivalent to a password. Cisco has provided a workaround that ensures the\ncommunity names are removed when the device reloads. \nOnce the device is reloaded the original configuration is inserted\nwithout the access lists or mib views assigned to the community\nnames. Consult the workarounds section of this advisory. \n\nThis vulnerability was introduced as part of a new feature integrated\ninto the affected releases called PROFINET. \nThis vulnerability has been assigned Common Vulnerabilities and\nExposures (CVE) ID CVE-2010-1574. \n\nVulnerability Scoring Details\n=============================\n\nCisco has provided scores for the vulnerability in this advisory\nbased on the Common Vulnerability Scoring System (CVSS). The CVSS\nscoring in this Security Advisory is done in accordance with CVSS\nversion 2.0. \n\nCVSS is a standards-based scoring method that conveys vulnerability\nseverity and helps determine urgency and priority of response. \n\nCisco has provided a base and temporal score. Customers can then\ncompute environmental scores to assist in determining the impact of\nthe vulnerability in individual networks. \n\nCisco has provided an FAQ to answer additional questions regarding\nCVSS at:\n\nhttp://www.cisco.com/web/about/security/intelligence/cvss-qandas.html\n\nCisco has also provided a CVSS calculator to help compute the\nenvironmental impact for individual networks at:\n\nhttp://intellishield.cisco.com/security/alertmanager/cvss\n\nCSCtf25589 - Hard-coded SNMP Community Names in Cisco Industrial Ethernet 3000 Series\n\nCVSS Base Score - 10\n\nAccess Vector - Network\nAccess Complexity - Low\nAuthentication - None\nConfidentiality Impact - Complete\nIntegrity Impact - Complete\nAvailability Impact - Complete\n\nCVSS Temporal Score - 8.3\n\nExploitability - Functional\nRemediation Level - Official-Fix\nReport Confidence - Confirmed\n\nImpact\n======\n\nSuccessful exploitation of the vulnerability could result in an\nattacker obtaining full control of the device. \n\nSoftware Versions and Fixes\n===========================\n\nWhen considering software upgrades, consult\nhttp://www.cisco.com/go/psirt and any subsequent advisories to\ndetermine exposure and a complete upgrade solution. \n\nIn all cases, customers should exercise caution to ensure the devices\nto be upgraded contain sufficient memory and that current hardware\nand software configurations will continue to be supported properly by\nthe new release. If the information is not clear, contact the Cisco\nTechnical Assistance Center (TAC) or your contracted maintenance\nprovider for assistance. If a given release train is vulnerable, then the\nearliest possible releases that contain the fix (along with the\nanticipated date of availability for each, if applicable) are listed\nin the \"First Fixed Release\" column of the table. A device running a\nrelease in the given train that is earlier than the release in a\nspecific column (less than the First Fixed Release) is known to be\nvulnerable. Cisco recommends upgrading to a release equal to or later\nthan the release specified in the \"First Fixed Release\" column of the\ntable. \n\n+-------------------------------------------------------------------+\n| Major | Availability of Repaired Releases |\n| Release | |\n|--------------+----------------------------------------------------|\n| Affected | |\n| 12.0-Based | First Fixed Release |\n| Releases | |\n|-------------------------------------------------------------------|\n| There are no affected 12.0 based releases |\n|-------------------------------------------------------------------|\n| Affected | |\n| 12.1-Based | First Fixed Release |\n| Releases | |\n|-------------------------------------------------------------------|\n| There are no affected 12.1 based releases |\n|-------------------------------------------------------------------|\n| Affected | |\n| 12.2-Based | First Fixed Release |\n| Releases | |\n|--------------+----------------------------------------------------|\n| | Releases prior to 12.2(52)SE are not vulnerable. |\n| 12.2SE | First fixed in release 12.2(55)SE. Currently |\n| | scheduled to be available August 2010. |\n|-------------------------------------------------------------------|\n| There are no other affected 12.2 based releases |\n|-------------------------------------------------------------------|\n| Affected | |\n| 12.3-Based | First Fixed Release |\n| Releases | |\n|-------------------------------------------------------------------|\n| There are no affected 12.3 based releases |\n|-------------------------------------------------------------------|\n| Affected | |\n| 12.4-Based | First Fixed Release |\n| Releases | |\n|-------------------------------------------------------------------|\n| There are no affected 12.4 based releases |\n|-------------------------------------------------------------------|\n| Affected | |\n| 15.0-Based | First Fixed Release |\n| Releases | |\n|-------------------------------------------------------------------|\n| There are no affected 15.0 based releases |\n|-------------------------------------------------------------------|\n| Affected | |\n| 15.1-Based | First Fixed Release |\n| Releases | |\n|-------------------------------------------------------------------|\n| There are no affected 15.1 based releases |\n+-------------------------------------------------------------------+\n\nWorkarounds\n===========\n\nManually Remove SNMP Community Names\n+-----------------------------------\n\nNote: The following workaround is only effective until the device is\nreloaded. Upon each reload of the device this workaround must be\nre-applied. \n\nLog in to the device, and enter configuration mode. This workaround\nmust be applied each time the device is reloaded. \n\nAutomatically Remove SNMP Community Names\n+----------------------------------------\n\nBy creating an Embedded Event Manager (EEM) policy, it is possible to\nautomatically remove the hard-coded SNMP community names each time\nthe device is reloaded. The following example shows an EEM policy\nthat runs each time the device is reloaded and removes the hard-coded\nSNMP community names. \n\n event manager applet cisco-sa-20100707-snmp\n event timer countdown time 30 \n action 10 cli command \"enable\"\n action 20 cli command \"configure terminal\"\n action 30 cli command \"no snmp-server community public RO\"\n action 40 cli command \"no snmp-server community private RW\"\n action 50 cli command \"end\"\n action 60 cli command \"disable\"\n action 70 syslog msg \"Hard-coded SNMP community names as per Cisco Security Advisory cisco-sa-20100707-snmp removed\"\n\nFor more information on EEM policies consult the Cisco IOS Network\nManagement Configuration Guide - Embedded Event Manager Overview at\nthe following link:\n\nhttp://www.cisco.com/en/US/docs/ios/netmgmt/configuration/guide/nm_eem_overview_ps6441_TSD_Products_Configuration_Guide_Chapter.html\n\nInfrastructure Access Control Lists\n+----------------------------------\n\nAlthough it is often difficult to block traffic that transits a\nnetwork, it is possible to identify traffic that should never be\nallowed to target infrastructure devices and block that traffic at\nthe device interface or the border of networks. \n\nIf SNMP management is not required on the IE3000, then dropping all\nSNMP traffic to the device is a sufficient workaround. The iACL below\nshows an example of an IE3000 with two interfaces configured with\nlayer 3 access, dropping all SNMP queries destined to the IE3000:\n\n \n !---\n !--- Deny SNMP traffic from all other sources destined to \n !--- configured IP addresses on the IE3000. \n !---\n \n \n access-list 150 deny udp any host 192.168.0.1 eq snmp\n access-list 150 deny udp any host 192.168.1.1 eq snmp\n \n \n !---\n !--- Permit/deny all other Layer 3 and Layer 4 traffic in \n !--- accordance with existing security policies and configurations\n !--- Permit all other traffic to transit the device. \n !---\n \n \n access-list 150 permit ip any any\n \n \n !---\n !--- Apply access-list to all Layer 3 interfaces \n !--- (only two examples shown)\n !---\n \n \n interface Vlan1\n ip address 192.168.0.1 255.255.255.0\n ip access-group 150 in\n \n interface GigabitEthernet1/1\n ip address 192.168.1.1 255.255.255.0\n ip access-group 150 in\n\nThe white paper \"Protecting Your Core: Infrastructure Protection\nAccess Control Lists\" presents guidelines and recommended deployment\ntechniques for infrastructure protection access lists. This white\npaper can be obtained at the following link:\n\nhttp://www.cisco.com/en/US/tech/tk648/tk361/technologies_white_paper09186a00801a1a55.shtml\n\nObtaining Fixed Software\n========================\n\nCisco has released free software updates that address this\nvulnerability. Prior to deploying software, customers should consult\ntheir maintenance provider or check the software for feature set\ncompatibility and known issues specific to their environment. \n\nCustomers may only install and expect support for the feature sets\nthey have purchased. By installing, downloading, accessing or\notherwise using such software upgrades, customers agree to be bound\nby the terms of Cisco\u0027s software license terms found at:\n\nhttp://www.cisco.com/en/US/docs/general/warranty/English/EU1KEN_.html\n\nor as otherwise set forth at Cisco.com Downloads at:\n\nhttp://www.cisco.com/public/sw-center/sw-usingswc.shtml\n\nDo not contact 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\ntheir regular update channels. For most customers, this means that\nupgrades should be obtained through the Software Center on Cisco\u0027s\nworldwide website at http://www.cisco.com. \n\nCustomers using Third Party Support Organizations\n+------------------------------------------------\n\nCustomers whose Cisco products are provided or maintained through\nprior or existing agreements with third-party support organizations,\nsuch as Cisco Partners, authorized resellers, or service providers\nshould contact that support organization for guidance and assistance\nwith the appropriate course of action in regards to this advisory. \n\nThe effectiveness of any workaround or fix is dependent on specific\ncustomer situations, such as product mix, network topology, traffic\nbehavior, and organizational mission. Due to the variety of affected\nproducts and releases, customers should consult with their service\nprovider or support organization to ensure any applied workaround or\nfix is the most appropriate for use in the intended network before it\nis deployed. \n\nCustomers without Service Contracts\n+----------------------------------\n\nCustomers who purchase direct from Cisco but do not hold a Cisco\nservice contract, and customers who purchase through third-party\nvendors but are unsuccessful in obtaining fixed software through\ntheir point of sale should acquire upgrades by contacting the Cisco\nTechnical Assistance Center (TAC). TAC contacts are as follows. \n\n * +1 800 553 2447 (toll free from within North America)\n * +1 408 526 7209 (toll call from anywhere in the world)\n * e-mail: tac@cisco.com\n\nCustomers should have their product serial number available and be\nprepared to give the URL of this notice as evidence of entitlement to\na free upgrade. Free upgrades for non-contract customers must be\nrequested through the TAC. \n\nRefer to:\n\nhttp://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html\n\nfor additional TAC contact information, including localized telephone\nnumbers, and instructions and e-mail addresses for use in various\nlanguages. \n\nExploitation and Public Announcements\n=====================================\n\nThe Cisco PSIRT is not aware of any public announcements or malicious\nuse of the vulnerability described in this advisory. \n\nThis vulnerability was discovered when handling customer support\ncalls. \n\nStatus of this Notice: FINAL\n============================\n\nTHIS DOCUMENT IS PROVIDED ON AN \"AS IS\" BASIS AND DOES NOT IMPLY ANY\nKIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTIES OF\nMERCHANTABILITY OR FITNESS FOR A PARTICULAR USE. YOUR USE OF THE\nINFORMATION ON THE DOCUMENT OR MATERIALS LINKED FROM THE DOCUMENT IS\nAT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS\nDOCUMENT AT ANY TIME. \n\nA stand-alone copy or Paraphrase of the text of this document that\nomits the distribution URL in the following section is an\nuncontrolled copy, and may lack important information or contain\nfactual errors. \n\nDistribution\n============\n\nThis advisory is posted on Cisco\u0027s worldwide website at:\n\nhttp://www.cisco.com/warp/public/707/cisco-sa-20100707-snmp.shtml\n\nIn addition to worldwide web posting, a text version of this notice\nis clear-signed with the Cisco PSIRT PGP key and is posted to the\nfollowing e-mail and Usenet news recipients. \n\n * cust-security-announce@cisco.com\n * first-bulletins@lists.first.org\n * bugtraq@securityfocus.com\n * vulnwatch@vulnwatch.org\n * cisco@spot.colorado.edu\n * cisco-nsp@puck.nether.net\n * full-disclosure@lists.grok.org.uk\n * comp.dcom.sys.cisco@newsgate.cisco.com\n\nFuture updates of this advisory, if any, will be placed on Cisco\u0027s\nworldwide website, but may or may not be actively announced on\nmailing lists or newsgroups. Users concerned about this problem are\nencouraged to check the above URL for any updates. \n\nRevision History\n================\n\n+---------------------------------------+\n| Revision | | Initial |\n| 1.0 | 2010-July-07 | public |\n| | | release. |\n+---------------------------------------+\n\nCisco Security Procedures\n=========================\n\nComplete information on reporting security vulnerabilities in Cisco\nproducts, obtaining assistance with security incidents, and\nregistering to receive security information from Cisco, is available\non Cisco\u0027s worldwide website at:\n\nhttp://www.cisco.com/en/US/products/products_security_vulnerability_policy.html\n\nThis includes instructions for press inquiries regarding Cisco security\nnotices. All Cisco security advisories are available at:\n\nhttp://www.cisco.com/go/psirt\n-----BEGIN PGP SIGNATURE-----\n\niD8DBQFMNJS386n/Gc8U/uARAmN5AJsGyv7GXrtcrfddAeeDa6U8ZeYhyQCcCIkj\nEnlJFTHJ1iEyqh41bdAq0so=\n=qocW\n-----END PGP SIGNATURE-----\n",
"sources": [
{
"db": "NVD",
"id": "CVE-2010-1574"
},
{
"db": "CERT/CC",
"id": "VU#732671"
},
{
"db": "JVNDB",
"id": "JVNDB-2010-001731"
},
{
"db": "CNVD",
"id": "CNVD-2010-1291"
},
{
"db": "BID",
"id": "41436"
},
{
"db": "IVD",
"id": "0c83a6ea-2356-11e6-abef-000c29c66e3d"
},
{
"db": "VULHUB",
"id": "VHN-44179"
},
{
"db": "PACKETSTORM",
"id": "91623"
},
{
"db": "PACKETSTORM",
"id": "91601"
}
],
"trust": 3.6
},
"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-44179",
"trust": 0.1,
"type": "unknown"
}
],
"sources": [
{
"db": "VULHUB",
"id": "VHN-44179"
}
]
},
"external_ids": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/external_ids#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"db": "NVD",
"id": "CVE-2010-1574",
"trust": 3.7
},
{
"db": "SECUNIA",
"id": "40407",
"trust": 3.4
},
{
"db": "BID",
"id": "41436",
"trust": 2.8
},
{
"db": "CERT/CC",
"id": "VU#732671",
"trust": 2.7
},
{
"db": "SECTRACK",
"id": "1024173",
"trust": 2.5
},
{
"db": "OSVDB",
"id": "66120",
"trust": 1.9
},
{
"db": "VUPEN",
"id": "ADV-2010-1754",
"trust": 1.9
},
{
"db": "XF",
"id": "60145",
"trust": 1.4
},
{
"db": "CNNVD",
"id": "CNNVD-201007-058",
"trust": 0.9
},
{
"db": "CNVD",
"id": "CNVD-2010-1291",
"trust": 0.8
},
{
"db": "JVNDB",
"id": "JVNDB-2010-001731",
"trust": 0.8
},
{
"db": "NSFOCUS",
"id": "15402",
"trust": 0.6
},
{
"db": "CISCO",
"id": "20100707 HARD-CODED SNMP COMMUNITY NAME S IN CISCO INDUSTRIAL ETHERNET 3000 SERIES SWITCHES VULNERABILITY",
"trust": 0.6
},
{
"db": "IVD",
"id": "0C83A6EA-2356-11E6-ABEF-000C29C66E3D",
"trust": 0.2
},
{
"db": "PACKETSTORM",
"id": "91601",
"trust": 0.2
},
{
"db": "VULHUB",
"id": "VHN-44179",
"trust": 0.1
},
{
"db": "PACKETSTORM",
"id": "91623",
"trust": 0.1
}
],
"sources": [
{
"db": "IVD",
"id": "0c83a6ea-2356-11e6-abef-000c29c66e3d"
},
{
"db": "CERT/CC",
"id": "VU#732671"
},
{
"db": "CNVD",
"id": "CNVD-2010-1291"
},
{
"db": "VULHUB",
"id": "VHN-44179"
},
{
"db": "BID",
"id": "41436"
},
{
"db": "JVNDB",
"id": "JVNDB-2010-001731"
},
{
"db": "PACKETSTORM",
"id": "91623"
},
{
"db": "PACKETSTORM",
"id": "91601"
},
{
"db": "CNNVD",
"id": "CNNVD-201007-058"
},
{
"db": "NVD",
"id": "CVE-2010-1574"
}
]
},
"id": "VAR-201007-0200",
"iot": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/iot#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": true,
"sources": [
{
"db": "IVD",
"id": "0c83a6ea-2356-11e6-abef-000c29c66e3d"
},
{
"db": "CNVD",
"id": "CNVD-2010-1291"
},
{
"db": "VULHUB",
"id": "VHN-44179"
}
],
"trust": 1.73333335
},
"iot_taxonomy": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/iot_taxonomy#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"category": [
"ICS",
"Network device"
],
"sub_category": null,
"trust": 0.6
},
{
"category": [
"ICS"
],
"sub_category": null,
"trust": 0.2
}
],
"sources": [
{
"db": "IVD",
"id": "0c83a6ea-2356-11e6-abef-000c29c66e3d"
},
{
"db": "CNVD",
"id": "CNVD-2010-1291"
}
]
},
"last_update_date": "2024-11-23T23:03:03.067000Z",
"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-20100707-snmp",
"trust": 0.8,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20100707-snmp.shtml"
},
{
"title": "20809",
"trust": 0.8,
"url": "http://tools.cisco.com/security/center/viewAlert.x?alertId=20809"
},
{
"title": "OL23061",
"trust": 0.8,
"url": "http://www.cisco.com/en/US/docs/switches/lan/cisco_ie3000/software/release/12.2_55_se/release/notes/OL23061.html"
},
{
"title": "PB 614546",
"trust": 0.8,
"url": "http://www.cisco.com/en/US/prod/collateral/iosswrel/ps8802/ps6969/ps5012/product_bulletin_c25-614546_ps10081_Products_Bulletin.html"
},
{
"title": "cisco-sa-20100707-snmp",
"trust": 0.8,
"url": "http://www.cisco.com/JP/support/public/ht/security/109/1090134/cisco-sa-20100707-snmp-j.shtml"
},
{
"title": "Cisco Industrial Ethernet 3000 Series Switches Hardcoded SNMP Common String Name Security Patch",
"trust": 0.6,
"url": "https://www.cnvd.org.cn/patchInfo/show/592"
}
],
"sources": [
{
"db": "CNVD",
"id": "CNVD-2010-1291"
},
{
"db": "JVNDB",
"id": "JVNDB-2010-001731"
}
]
},
"problemtype_data": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/problemtype_data#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"problemtype": "CWE-264",
"trust": 1.9
}
],
"sources": [
{
"db": "VULHUB",
"id": "VHN-44179"
},
{
"db": "JVNDB",
"id": "JVNDB-2010-001731"
},
{
"db": "NVD",
"id": "CVE-2010-1574"
}
]
},
"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/41436"
},
{
"trust": 2.5,
"url": "http://securitytracker.com/id?1024173"
},
{
"trust": 2.5,
"url": "http://secunia.com/advisories/40407"
},
{
"trust": 2.0,
"url": "http://www.cisco.com/en/us/products/products_security_advisory09186a0080b3891f.shtml"
},
{
"trust": 1.9,
"url": "http://www.kb.cert.org/vuls/id/732671"
},
{
"trust": 1.9,
"url": "http://osvdb.org/66120"
},
{
"trust": 1.9,
"url": "http://www.vupen.com/english/advisories/2010/1754"
},
{
"trust": 1.6,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20100707-snmp.shtml"
},
{
"trust": 1.4,
"url": "http://xforce.iss.net/xforce/xfdb/60145"
},
{
"trust": 1.1,
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/60145"
},
{
"trust": 0.9,
"url": "http://secunia.com/advisories/40407/"
},
{
"trust": 0.8,
"url": "http://cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2010-1574"
},
{
"trust": 0.8,
"url": "http://jvn.jp/cert/jvnvu732671"
},
{
"trust": 0.8,
"url": "http://web.nvd.nist.gov/view/vuln/detail?vulnid=cve-2010-1574"
},
{
"trust": 0.6,
"url": "http://www.nsfocus.net/vulndb/15402"
},
{
"trust": 0.1,
"url": "http://secunia.com/products/corporate/evm/"
},
{
"trust": 0.1,
"url": "http://secunia.com/advisories/secunia_security_advisories/"
},
{
"trust": 0.1,
"url": "http://secunia.com/vulnerability_scanning/corporate/wsus_sccm_3rd_third_party_patching/"
},
{
"trust": 0.1,
"url": "http://secunia.com/company/jobs/open_positions/talented_programmer"
},
{
"trust": 0.1,
"url": "http://secunia.com/vulnerability_scanning/personal/"
},
{
"trust": 0.1,
"url": "http://secunia.com/sec_adv_unsubscribe/?email=packet%40packetstormsecurity.org"
},
{
"trust": 0.1,
"url": "http://secunia.com/company/jobs/open_positions/reverse_engineer"
},
{
"trust": 0.1,
"url": "https://ca.secunia.com/?page=viewadvisory\u0026vuln_id=40407"
},
{
"trust": 0.1,
"url": "http://secunia.com/advisories/40407/#comments"
},
{
"trust": 0.1,
"url": "http://secunia.com/advisories/about_secunia_advisories/"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/go/psirt"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/en/us/support/tsd_cisco_worldwide_contacts.html"
},
{
"trust": 0.1,
"url": "https://nvd.nist.gov/vuln/detail/cve-2010-1574"
},
{
"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/docs/general/warranty/english/eu1ken_.html"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/web/about/security/intelligence/cvss-qandas.html"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/en/us/docs/ios/netmgmt/configuration/guide/nm_eem_overview_ps6441_tsd_products_configuration_guide_chapter.html"
},
{
"trust": 0.1,
"url": "http://www.cisco.com."
},
{
"trust": 0.1,
"url": "http://www.cisco.com/en/us/tech/tk648/tk361/technologies_white_paper09186a00801a1a55.shtml"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/public/sw-center/sw-usingswc.shtml"
},
{
"trust": 0.1,
"url": "http://intellishield.cisco.com/security/alertmanager/cvss"
}
],
"sources": [
{
"db": "CERT/CC",
"id": "VU#732671"
},
{
"db": "CNVD",
"id": "CNVD-2010-1291"
},
{
"db": "VULHUB",
"id": "VHN-44179"
},
{
"db": "BID",
"id": "41436"
},
{
"db": "JVNDB",
"id": "JVNDB-2010-001731"
},
{
"db": "PACKETSTORM",
"id": "91623"
},
{
"db": "PACKETSTORM",
"id": "91601"
},
{
"db": "CNNVD",
"id": "CNNVD-201007-058"
},
{
"db": "NVD",
"id": "CVE-2010-1574"
}
]
},
"sources": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#",
"data": {
"@container": "@list"
}
},
"data": [
{
"db": "IVD",
"id": "0c83a6ea-2356-11e6-abef-000c29c66e3d"
},
{
"db": "CERT/CC",
"id": "VU#732671"
},
{
"db": "CNVD",
"id": "CNVD-2010-1291"
},
{
"db": "VULHUB",
"id": "VHN-44179"
},
{
"db": "BID",
"id": "41436"
},
{
"db": "JVNDB",
"id": "JVNDB-2010-001731"
},
{
"db": "PACKETSTORM",
"id": "91623"
},
{
"db": "PACKETSTORM",
"id": "91601"
},
{
"db": "CNNVD",
"id": "CNNVD-201007-058"
},
{
"db": "NVD",
"id": "CVE-2010-1574"
}
]
},
"sources_release_date": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources_release_date#",
"data": {
"@container": "@list"
}
},
"data": [
{
"date": "2010-07-09T00:00:00",
"db": "IVD",
"id": "0c83a6ea-2356-11e6-abef-000c29c66e3d"
},
{
"date": "2010-07-12T00:00:00",
"db": "CERT/CC",
"id": "VU#732671"
},
{
"date": "2010-07-09T00:00:00",
"db": "CNVD",
"id": "CNVD-2010-1291"
},
{
"date": "2010-07-08T00:00:00",
"db": "VULHUB",
"id": "VHN-44179"
},
{
"date": "2010-07-07T00:00:00",
"db": "BID",
"id": "41436"
},
{
"date": "2010-07-27T00:00:00",
"db": "JVNDB",
"id": "JVNDB-2010-001731"
},
{
"date": "2010-07-08T14:38:07",
"db": "PACKETSTORM",
"id": "91623"
},
{
"date": "2010-07-08T04:31:48",
"db": "PACKETSTORM",
"id": "91601"
},
{
"date": "2010-07-12T00:00:00",
"db": "CNNVD",
"id": "CNNVD-201007-058"
},
{
"date": "2010-07-08T18:30:00.827000",
"db": "NVD",
"id": "CVE-2010-1574"
}
]
},
"sources_update_date": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources_update_date#",
"data": {
"@container": "@list"
}
},
"data": [
{
"date": "2010-07-12T00:00:00",
"db": "CERT/CC",
"id": "VU#732671"
},
{
"date": "2010-07-09T00:00:00",
"db": "CNVD",
"id": "CNVD-2010-1291"
},
{
"date": "2017-08-17T00:00:00",
"db": "VULHUB",
"id": "VHN-44179"
},
{
"date": "2010-07-07T00:00:00",
"db": "BID",
"id": "41436"
},
{
"date": "2010-09-29T00:00:00",
"db": "JVNDB",
"id": "JVNDB-2010-001731"
},
{
"date": "2010-07-12T00:00:00",
"db": "CNNVD",
"id": "CNNVD-201007-058"
},
{
"date": "2024-11-21T01:14:43.150000",
"db": "NVD",
"id": "CVE-2010-1574"
}
]
},
"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-201007-058"
}
],
"trust": 0.6
},
"title": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/title#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "Cisco Industrial Ethernet 3000 Series switches have hardcoded SNMP community strings",
"sources": [
{
"db": "CERT/CC",
"id": "VU#732671"
}
],
"trust": 0.8
},
"type": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/type#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "permissions and access control",
"sources": [
{
"db": "CNNVD",
"id": "CNNVD-201007-058"
}
],
"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.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- 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.