Because of the pervasiveness of the Cisco Catalyst 2960X/2960XR switches on the grey market, it is imperative users enable the latest software release in order to validate the authenticity, security, and performance of their switch, Cisco said in an advisory.
The latest software can be downloaded from the Cisco Software Download website.
Cisco said if users purchase products from anyone other than an authorized dealer, you face the following risks:
- Counterfeit Products
- Licensing
- Warranties
- Support Plans
- Third-Party Components
The Cisco Brand Protection team partners closely with law enforcement and customs officials around the world to stop counterfeit products at borders, identify counterfeiting operations, and pursue legal actions against infringers of Cisco’s intellectual property rights, which includes trademarks.
Cisco’s goal is to actively support our partners and customers in protecting their investment in Cisco solutions.
In order to detect and mitigate device counterfeiting and malicious attacks on hardware and software, Cisco uses Hardware Trust Anchor, Secure Unique Device Identifier, digitally signed software images, secure boot, and other multilayered security approaches to verify the authenticity and integrity of our solutions. These technologies run automated checks of hardware and software integrity and can shut down the boot process if a compromise is detected.
Counterfeit devices run the risk of disrupting normal system operation and can show any abnormal behavior.
Some of the common error logs include:
- AUTHENTICATION_FAIL
- DEVICE_AUTHENTICATION_FAIL
Users can apply the following process to validate the SUDI on a Cisco Catalyst 2960X/2960XR device:
Step 1. Gather Device Data
Data needed from the device for this validation includes:
- Basic information listed in the output of the show version CLI command.
- Details for SUDI verification with the output of the show platform sudi certificate sign nonce [nonce] CLI command. This CLI command is only available in Cisco IOS Release 15.2.7E4 and later.
In order to confirm the output is not tampered in any way, include the ‘sign’ option with a ‘nonce’ in the command. The value of the nonce shall be a random number decided when you enter the command. Do not use a static value for all validations on a particular device.
Step 2. Verify the X.509v3 Certificates
The result of SUDI verification contains three X.509v3 certificates – Certficate 1, Certificate 2, and Certificate 3 in the previous sample output.
Certificate 1 is the Cisco Root Certificate Authority (CA) certificate and Certificate 2 is the signing SUDI CA certificate. In order to verify the certificates, download the official X.509v3 certificates – Cisco Root CA 2048 (crca2048) – PEM and ACT2 SUDI CA – PEM from the Cisco PKI website and compare them with the ones listed in the SUDI verification (show platform sudi certificate sign nonce [nonce command) output:
- Certificate 1 from the device output should match with Cisco Root CA 2048 (crca2048) – PEM downloaded from the website.
- Certificate 2 from the device output should match with ACT2 SUDI CA – PEM downloaded from the website.
Step 3. Verify the Device Identity
The third X.509v3 certificate (Certificate 3 in the sample output) in the result of SUDI verification is the SUDI certificate. It is important to confirm the device identity specified in this certificate which should match the device information.
The openssl command can be used to extract the device ID (Product ID (PID) and Serial Number (SN)) from the Subject line in the SUDI certificate.
All releases earlier than Cisco IOS Release 15.2.7E4 suffer from the issue.
The affected release was 15.12 and the affected numbers were:
15.2(2)E, 15.2(2)E1, 15.2(2)E10, 15.2(2)E2, 15.2(2)E3, 15.2(2)E4, 15.2(2)E5, 15.2(2)E5a, 15.2(2)E6, 15.2(2)E7, 15.2(2)E8, 15.2(2)E9, 15.2(3)E, 15.2(3)E1, 15.2(3)E2, 15.2(3)E3, 15.2(4)E, 15.2(4)E1, 15.2(4)E10, 15.2(4)E2, 15.2(4)E3, 15.2(4)E4, 15.2(4)E5, 15.2(4)E6, 15.2(4)E7, 15.2(4)E8, 15.2(4)E9, 15.2(5)E, 15.2(5)E1, 15.2(5)E2, 15.2(6)E, 15.2(6)E1, 15.2(6)E2a, 15.2(7)E1, 15.2(7)E2, 15.2(7)E3
Click here for more information on the advisory.

