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.
                
            References
                    | Link | Resource | 
|---|---|
| http://www.ssh.com/company/news/2006/english/security/article/786/ | Patch Vendor Advisory | 
| http://www.kb.cert.org/vuls/id/845620 | Third Party Advisory US Government Resource | 
| http://securitytracker.com/id?1017060 | Patch Third Party Advisory VDB Entry | 
| http://securitytracker.com/id?1017061 | Patch Third Party Advisory VDB Entry | 
| http://secunia.com/advisories/22350 | Patch Third Party Advisory | 
| http://www.vupen.com/english/advisories/2006/4032 | Permissions Required | 
Configurations
                    Configuration 1 (hide)
                                
                                
  | 
                        
Information
                Published : 2006-10-24 15:07
Updated : 2019-08-28 07:49
NVD link : CVE-2006-5484
Mitre link : CVE-2006-5484
JSON object : View
CWE
                Products Affected
                ssh
- tectia_manager
 - tectia_server
 - tectia_connector
 - tectia_client
 


