CVE-2001-1476: High severity SSH ssh vulnerability

Published Jan 18, 2001
·
Updated

SSH before 2.0, with RC4 encryption and the "disallow NULL passwords" option enabled, makes it easier for remote attackers to guess portions of user passwords by replaying user sessions with certain modifications, which trigger different messages depending on whether the guess is correct or not.

Affected Software

8 affected components
SSH ssh=1.2.24
SSH ssh=1.2.25
SSH ssh=1.2.26
SSH ssh=1.2.27
SSH ssh=1.2.28
SSH ssh=1.2.29
SSH ssh=1.2.30
SSH ssh=1.2.31

Remediation

Event History

Jan 18, 2001
CVE Published
05:00 AM
Apr 21, 2005
CVE Published
via MITRE·08:00 AM
Data Sourced
via MITRE·08:00 AM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2001-1476?

CVE-2001-1476 is considered to have a moderate severity rating due to the potential for password guessing.

2

How do I fix CVE-2001-1476?

To fix CVE-2001-1476, it is recommended to upgrade to a version of SSH that is more secure and does not have this vulnerability.

3

Which versions of SSH are affected by CVE-2001-1476?

CVE-2001-1476 affects SSH versions 1.2.24 through 1.2.31.

4

What happens if I leave CVE-2001-1476 unaddressed?

Leaving CVE-2001-1476 unaddressed may allow attackers to replay user sessions and guess passwords.

5

Is it safe to use SSH with RC4 encryption after CVE-2001-1476?

Using SSH with RC4 encryption is risky after CVE-2001-1476, as it may expose your passwords to vulnerabilities.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203