# CVE-2006-5484: Weak cryptography in n/a

> Remote attackers can forge PKCS #1 v1.5 signatures when RSA keys with exponent 3 are used, bypassing certificate verification in SSH Tectia products.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Oct 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-f6g8-8p5j-hphv

## What is CVE-2006-5484?

CVE-2006-5484 is a medium-severity vulnerability in n/a, published on 24 Oct 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2006-5484?

It affects 4 products.


Products: Ssh Tectia Client, Ssh Tectia Connector, Ssh Tectia Manager, Ssh Tectia Server.

## How do I fix CVE-2006-5484?

No fix has been published for CVE-2006-5484 yet. Limit exposure of the affected software until one is available.

## Is CVE-2006-5484 being exploited?

There is no known exploitation of CVE-2006-5484 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2021-27891](https://insights.sbomify.com/CVE-2021-27891/): SSH Tectia Client and Server before 6.4.19 on Windows have weak key generation. (high 8.8)
- [CVE-2021-27892](https://insights.sbomify.com/CVE-2021-27892/): Privilege escalation in n/a (high 7.8)
- [CVE-2007-5616](https://insights.sbomify.com/CVE-2007-5616/): Privilege escalation in n/a (high 7.2)
- [CVE-2006-4315](https://insights.sbomify.com/CVE-2006-4315/): Privilege escalation in n/a (high 7.2)
- [CVE-2021-27893](https://insights.sbomify.com/CVE-2021-27893/): Privilege escalation in n/a (high 7.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-5484 and fix it if it is affected.

What it is: CVE-2006-5484 is a medium-severity vulnerability in n/a, published on 24 Oct 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-5484 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2006-5484/ (Markdown: https://insights.sbomify.com/CVE-2006-5484/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2006-5484
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2006-5484
- OSV: https://osv.dev/vulnerability/CVE-2006-5484

---
From sbomify Insights: https://insights.sbomify.com/CVE-2006-5484/
Summaries are generated and may contain mistakes; the official description above is the record.