First published: Tue Oct 24 2006(Updated: )
SSH Tectia Client/Server/Connector 5.1.0 and earlier, Manager 2.2.0 and earlier, and other products, when using an RSA key with exponent 3, removes PKCS-1 padding before generating a hash, which allows remote attackers to forge a PKCS #1 v1.5 signature that is signed by that RSA key and prevents Tectia from correctly verifying X.509 and other certificates that use PKCS #1, a similar issue to CVE-2006-4339.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
SSH Tectia Client | <=5.1.0 | |
SSH Tectia Connector | <=5.1.0 | |
SSH Tectia Manager | <=2.2.0 | |
SSH Tectia Server | <=5.1.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2006-5484 has a moderate severity level due to its potential for allowing signature forgery.
To fix CVE-2006-5484, upgrade to a version of SSH Tectia Client/Server/Connector or Manager that is later than 5.1.0 or 2.2.0 respectively.
CVE-2006-5484 affects SSH Tectia Client, Server, Connector, and Manager versions 5.1.0 and earlier for the Client, Server, and Connector, and 2.2.0 and earlier for the Manager.
Yes, CVE-2006-5484 can be exploited remotely by attackers to forge signatures.
CVE-2006-5484 involves RSA keys with an exponent of 3 and the improper handling of PKCS #1 v1.5 padding during hash generation.