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.
Link | Tags |
---|---|
http://securitytracker.com/id?1017060 | vdb entry third party advisory patch |
http://secunia.com/advisories/22350 | third party advisory patch |
http://www.vupen.com/english/advisories/2006/4032 | vdb entry permissions required |
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?1017061 | vdb entry third party advisory patch |