Skip to content
Noroxi
CVE-2008-5161· NVD / CVE Program· CNA mitre

Error handling in the SSH protocol in (1) SSH Tectia Client and Server and Connector 4.0 through 4.4.11, 5.0 through 5.2.4, and 5.3 through

Error handling in the SSH protocol in (1) SSH Tectia Client and Server and Connector 4.0 through 4.4.11, 5.0 through 5.2.4, and 5.3 through 5.3.8; Client and Server and ConnectSecure 6.0 through 6.0.4; Server for Linux on IBM System z 6.0.4; Server for IBM z/OS 5.5.1 and earlier, 6.0.0, and 6.0.1; and Client 4.0-J through 4.3.3-J and 4.0-K through 4.3.10-K; and (2) OpenSSH 4.7p1 and possibly other versions, when using a block cipher algorithm in Cipher Block Chaining (CBC) mode, makes it easier for remote attackers to recover certain plaintext data from an arbitrary block of ciphertext in an SSH session via unknown vectors.

LowCVSS 3.7 · v3.1—Weaponized Fix available
Published
Nov 19, 2008
Updated
Jun 16, 2026
EPSS
18.6% · 97th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

20

Monitor

Low priority for now.

CVSS
14 / 40 · 3.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
6 / 30 · 18.6%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Affected systems

VendorProduct
sshtectia client
sshtectia connector
sshtectia connectsecure
sshtectia server
openbsdopenssh

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • openbsd openssh4.7p1
  • ssh tectia client4.0
  • ssh tectia client4.0.1
  • ssh tectia client4.0.3
  • ssh tectia client4.0.4
  • ssh tectia client4.0.5
  • ssh tectia client4.2
  • ssh tectia client4.2.1
  • ssh tectia client4.3
  • ssh tectia client4.3.1
  • ssh tectia client4.3.1j
  • ssh tectia client4.3.2
  • ssh tectia client4.3.2j
  • ssh tectia client4.3.3
  • ssh tectia client4.3.4
  • ssh tectia client4.3.5
  • ssh tectia client4.3.6
  • ssh tectia client4.3.7
  • ssh tectia client4.3.8k
  • ssh tectia client4.3.9k

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12opensshbefore 1:5.1p1-51:5.1p1-5
Red Hat:enterprise_linux:5::clientopensshbefore 0:4.3p2-36.el50:4.3p2-36.el5
Red Hat:enterprise_linux:5::clientopenssh-askpassbefore 0:4.3p2-36.el50:4.3p2-36.el5
Red Hat:enterprise_linux:5::clientopenssh-clientsbefore 0:4.3p2-36.el50:4.3p2-36.el5
Red Hat:enterprise_linux:5::clientopenssh-debuginfobefore 0:4.3p2-36.el50:4.3p2-36.el5
Red Hat:enterprise_linux:5::clientopenssh-serverbefore 0:4.3p2-36.el50:4.3p2-36.el5

Same product

ssh: all records

Other highest-scoring records for the same primary product.

  • CVE-2021-27891SSH Tectia Client and Server before 6.4.19 on Windows have weak key generation.
    35Monitor
  • CVE-2021-27892SSH Tectia Client and Server before 6.4.19 on Windows allow local privilege escalation.
    31Monitor
  • CVE-2021-27893SSH Tectia Client and Server before 6.4.19 on Windows allow local privilege escalation in nonstandard conditions.
    28Monitor
  • CVE-2007-5616ssh-signer in SSH Tectia Client and Server 5.x before 5.2.4, and 5.3.x before 5.3.6, on Unix and Linux allows local users to gain privileges
    28Monitor
  • CVE-2006-4315Unquoted Windows search path vulnerability in multiple SSH Tectia products, including Client/Server/Connector 5.0.0 and 5.0.1 and Client/Ser
    28Monitor
  • CVE-2006-5484SSH 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,
    20Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:openssh1:5.1p1-5 · Debian:12Package registry (OSV)
red hat:openssh0:4.3p2-36.el5 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)
red hat:openssh-askpass0:4.3p2-36.el5 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)
red hat:openssh-clients0:4.3p2-36.el5 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)
red hat:openssh-debuginfo0:4.3p2-36.el5 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)
red hat:openssh-server0:4.3p2-36.el5 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)

Exploit status

Weaponized

A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.

Evidence

  • Metasploit module ×1
  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Metasploit moduleauxiliary/scanner/ssh/ssh_versionSSH Version Scannerauxiliary—
Proof-of-concept repository on GitHubstars:02025-10-08

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+6166 d
  3. TodaySep 30, 2026+6524 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
low · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

nvd-secondary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records