Tectia Connector
Approved changes feed: RSS · Atom
cpe:2.3:a:ssh:tectia_connector:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Ssh (244e7ab1-7432-5147-94cd-c233f4ecfdee) |
|---|---|
| Product | Tectia Connector (ad104541-e452-5ab2-a4d8-574ef19a455b) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2006-5484 |
vulnerable | 2026-06-08 04:49:20.636941 |
Details available
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.
Published: 2006-10-24T22:00:00.000Z
Updated: 2024-08-07T19:55:52.735Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.