Vulnerabilities · 2006 · Ssh
CVE-2006-5484
Ssh Tectia Client vulnerability
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 products
Tectia Client, Tectia Connector, Tectia Manager, Tectia Server. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Ssh Tectia Client runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- www.ssh.com/company/news/2006/english/security/article/786/ · Patch
- secunia.com/advisories/22350 · Patch
- securitytracker.com/id?1017060 · Patch
- securitytracker.com/id?1017061 · Patch
- www.kb.cert.org/vuls/id/845620 · Third Party Advisory
- www.vupen.com/english/advisories/2006/4032
- nvd.nist.gov/vuln/detail/CVE-2006-5484
- cve.org/CVERecord?id=CVE-2006-5484
More vulnerabilities in Ssh products
CVE-2024-30170CVE-2021-27893CVE-2021-27892CVE-2021-27891CVE-2012-5975CVE-2011-0766CVE-2008-5161CVE-2007-5616All 46
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.