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.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Tectia_client | Ssh | * | 5.1.0 (including) |
| Tectia_connector | Ssh | * | 5.1.0 (including) |
| Tectia_manager | Ssh | * | 2.2.0 (including) |
| Tectia_server | Ssh | * | 5.1.0 (including) |
References
- http://secunia.com/advisories/22350
- http://securitytracker.com/id?1017060
- http://securitytracker.com/id?1017061
- http://www.kb.cert.org/vuls/id/845620
- http://www.ssh.com/company/news/2006/english/security/article/786/
- http://www.vupen.com/english/advisories/2006/4032
- http://secunia.com/advisories/22350
- http://securitytracker.com/id?1017060
- http://securitytracker.com/id?1017061
- http://www.kb.cert.org/vuls/id/845620
- http://www.ssh.com/company/news/2006/english/security/article/786/
- http://www.vupen.com/english/advisories/2006/4032