CVE-2006-5484

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://secunia.com/advisories/22350 Patch Third Party Advisory
http://securitytracker.com/id?1017060 Patch Third Party Advisory VDB Entry
http://securitytracker.com/id?1017061 Patch Third Party Advisory VDB Entry
http://www.kb.cert.org/vuls/id/845620 Third Party Advisory US Government Resource
http://www.ssh.com/company/news/2006/english/security/article/786/ Patch Vendor Advisory
http://www.vupen.com/english/advisories/2006/4032 Permissions Required
Configurations

Configuration 1 (hide)

OR cpe:2.3:a:ssh:tectia_client:*:*:*:*:*:*:*:*
cpe:2.3:a:ssh:tectia_connector:*:*:*:*:*:*:*:*
cpe:2.3:a:ssh:tectia_manager:*:*:*:*:*:*:*:*
cpe:2.3:a:ssh:tectia_server:*:*:*:*:*:*:*:*

History

No history.

Information

Published : 2006-10-24 22:07

Updated : 2024-02-28 11:01


NVD link : CVE-2006-5484

Mitre link : CVE-2006-5484

CVE.ORG link : CVE-2006-5484


JSON object : View

Products Affected

ssh

  • tectia_connector
  • tectia_server
  • tectia_client
  • tectia_manager