CVE-2006-5484

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

1.4% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2006-10-24 22:07 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 22:31 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.4% in the next 30 days (EPSS).
• Severity: 5.0 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2006-10-24 22:07 UTC

Last modified

2026-06-16 22:31 UTC

Exploit probability

1.4% · EPSS, next 30 days

Record status

Modified

Affected

• Ssh Tectia Client ≤ 5.1.0
• Ssh Tectia Connector ≤ 5.1.0
• Ssh Tectia Manager ≤ 2.2.0
• Ssh Tectia Server ≤ 5.1.0

Attack profile CVSS 2.0 · 5.0

Attack vector

Network

Complexity

Low

Authentication

None

Confidentiality

None

Integrity

Partial

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2006-5484.md and follow it. Check whether this project is affected by CVE-2006-5484. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge