Ssh-2.0-cisco-1.25 Vulnerability |verified|

…then it’s likely vulnerable.

Practical, prioritized actions

Disclosing this banner is a poor security practice. It gives an attacker a complete "cheat sheet." It eliminates the need for them to probe or guess, instantly revealing the technology stack and signaling that the device likely has not been updated or hardened recently.

The Cisco-1.25 engine variant often relies on legacy default cryptographic configurations. It defaults to vulnerable Cipher Block Chaining (CBC) modes or older algorithms like Triple DES (3DES) and Blowfish. These algorithms are highly susceptible to modern traffic decryption techniques, sniffing, and Man-in-the-Middle (MitM) injection attacks.

Because the Cisco-1.25 software variant handles legacy cryptographic configurations on older hardware, scanners frequently alert on man-in-the-middle (MitM) vulnerabilities like the (CVE-2023-48795).

Immediately apply these commands to mitigate risks: ssh-2.0-cisco-1.25 vulnerability

The SSH-2.0-Cisco-1.25 string is a classic example of how seemingly innocuous information can be a powerful tool for attackers and a vital clue for defenders.

This version is known to be susceptible to several critical cryptographic weaknesses, including insecure key exchange algorithms, outdated encryption ciphers, and specific Cisco-branded vulnerabilities. If left unpatched, these vulnerabilities can allow attackers to intercept communications (Man-in-the-Middle), decrypt traffic, or gain unauthorized administrative access.

| Risk Factor | Rating | Justification | | :--- | :--- | :--- | | | High | Weak encryption allows traffic decryption via MitM attacks. | | Integrity | High | Weak key exchange algorithms allow data manipulation. | | Availability | Medium | Potential for DoS via handshake exploitation. | | Attack Complexity | Medium | Requires access to the network path (MitM) or valid credentials (downgrade attacks). |

This flaw targets the stability of the core network infrastructure.

: A logical flaw in the subsystem's processing of RSA-based public key validation. …then it’s likely vulnerable

Many legacy Cisco-1.25 banners indicate the device relies on cryptographic handshakes vulnerable to .

The vulnerability affects Cisco devices running SSH-2.0-Cisco-1.25, which is a specific implementation of the SSH protocol on Cisco IOS and IOS XE devices.

:

The identifier is a software version string returned by the SSH banner on many Cisco IOS-based devices. While not a specific vulnerability name itself, this version string is frequently associated with several critical security flaws that affect the SSH implementation in Cisco IOS and IOS XE software. Notable Vulnerabilities Associated with Cisco SSH

The string is not a single specific vulnerability, but rather a standard software banner string emitted by Cisco enterprise devices (running Cisco IOS or IOS XE) when an external system initiates a connection over Secure Shell (SSH) on Port 22. The Cisco-1

Robust network-level filtering is essential. Administrators should implement strict ACLs on all network infrastructure devices to restrict SSH access exclusively to dedicated management subnets, jump hosts, and bastion servers. It is crucial to verify that the ACL implementation supports filtering for the specific features in use. A recent vulnerability (CVE-2025-20159) demonstrated that some ACL implementations were bypassed for SSH and other management features, so validation is key.

: The Shodan CVE database provides detailed summaries of known vulnerabilities, including their CVSS scores and affected products, allowing for rapid correlation with discovered banners.

Cisco has released an advisory to address this vulnerability, which can be found at: https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20191106-ssh-1

In April 2025, a critical vulnerability was disclosed affecting the Erlang/OTP SSH server, which is embedded in various Cisco products and telecommunications systems.

Notifications and fully customizable quality profiles.

ssh-2.0-cisco-1.25 vulnerability ssh-2.0-cisco-1.25 vulnerability
ssh-2.0-cisco-1.25 vulnerability ssh-2.0-cisco-1.25 vulnerability ssh-2.0-cisco-1.25 vulnerability

Multiple Movie views.

ssh-2.0-cisco-1.25 vulnerability

Follow your favorite collections, actors, directors

ssh-2.0-cisco-1.25 vulnerability ssh-2.0-cisco-1.25 vulnerability

Frequent updates. See what's new without leaving the comfort of the app.

Features

ssh-2.0-cisco-1.25 vulnerability

Calendar

See all your upcoming movies in one convenient location.

ssh-2.0-cisco-1.25 vulnerability

Manual Search

Find all the releases, choose the one you want and send it right to your download client.

ssh-2.0-cisco-1.25 vulnerability

Automatic Failed Download Handling

Radarr makes failed downloads a thing of the past. Password protected releases, missing repair blocks or virtually any other reason? no worries. Radarr will automatically blacklist the release and tries another one until it finds one that works.

ssh-2.0-cisco-1.25 vulnerability

Custom Formats

Ensure you get the right release every time! Custom Formats allows fine control over release prioritization and selection. As simple as a single preferred word or as complex as you want with multiple criteria and regex.

Download

…then it’s likely vulnerable.

Practical, prioritized actions

Disclosing this banner is a poor security practice. It gives an attacker a complete "cheat sheet." It eliminates the need for them to probe or guess, instantly revealing the technology stack and signaling that the device likely has not been updated or hardened recently.

The Cisco-1.25 engine variant often relies on legacy default cryptographic configurations. It defaults to vulnerable Cipher Block Chaining (CBC) modes or older algorithms like Triple DES (3DES) and Blowfish. These algorithms are highly susceptible to modern traffic decryption techniques, sniffing, and Man-in-the-Middle (MitM) injection attacks.

Because the Cisco-1.25 software variant handles legacy cryptographic configurations on older hardware, scanners frequently alert on man-in-the-middle (MitM) vulnerabilities like the (CVE-2023-48795).

Immediately apply these commands to mitigate risks:

The SSH-2.0-Cisco-1.25 string is a classic example of how seemingly innocuous information can be a powerful tool for attackers and a vital clue for defenders.

This version is known to be susceptible to several critical cryptographic weaknesses, including insecure key exchange algorithms, outdated encryption ciphers, and specific Cisco-branded vulnerabilities. If left unpatched, these vulnerabilities can allow attackers to intercept communications (Man-in-the-Middle), decrypt traffic, or gain unauthorized administrative access.

| Risk Factor | Rating | Justification | | :--- | :--- | :--- | | | High | Weak encryption allows traffic decryption via MitM attacks. | | Integrity | High | Weak key exchange algorithms allow data manipulation. | | Availability | Medium | Potential for DoS via handshake exploitation. | | Attack Complexity | Medium | Requires access to the network path (MitM) or valid credentials (downgrade attacks). |

This flaw targets the stability of the core network infrastructure.

: A logical flaw in the subsystem's processing of RSA-based public key validation.

Many legacy Cisco-1.25 banners indicate the device relies on cryptographic handshakes vulnerable to .

The vulnerability affects Cisco devices running SSH-2.0-Cisco-1.25, which is a specific implementation of the SSH protocol on Cisco IOS and IOS XE devices.

:

The identifier is a software version string returned by the SSH banner on many Cisco IOS-based devices. While not a specific vulnerability name itself, this version string is frequently associated with several critical security flaws that affect the SSH implementation in Cisco IOS and IOS XE software. Notable Vulnerabilities Associated with Cisco SSH

The string is not a single specific vulnerability, but rather a standard software banner string emitted by Cisco enterprise devices (running Cisco IOS or IOS XE) when an external system initiates a connection over Secure Shell (SSH) on Port 22.

Robust network-level filtering is essential. Administrators should implement strict ACLs on all network infrastructure devices to restrict SSH access exclusively to dedicated management subnets, jump hosts, and bastion servers. It is crucial to verify that the ACL implementation supports filtering for the specific features in use. A recent vulnerability (CVE-2025-20159) demonstrated that some ACL implementations were bypassed for SSH and other management features, so validation is key.

: The Shodan CVE database provides detailed summaries of known vulnerabilities, including their CVSS scores and affected products, allowing for rapid correlation with discovered banners.

Cisco has released an advisory to address this vulnerability, which can be found at: https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20191106-ssh-1

In April 2025, a critical vulnerability was disclosed affecting the Erlang/OTP SSH server, which is embedded in various Cisco products and telecommunications systems.

Support

Wiki

Check out the FAQ, API documentation and other guides

Discord

Join our Discord server for a chat.

GitHub Issues

Track bugs and features for the things that matter to you.