Security readout for executives and security teams
Plain-English summary
This is an old but serious weakness in SSH version 1.5 implementations. In certain configurations, a remote attacker could decrypt or alter SSH traffic using a Bleichenbacher-style PKCS#1 v1.5 attack. Modern environments are usually unaffected unless they still permit legacy SSHv1-era services or old products.
Executive priority
Treat as high priority only if legacy SSHv1/1.5 exists, especially on externally reachable systems. For modern, supported SSH deployments, urgency is lower, but validation is important because the impact includes confidentiality and integrity of administrative traffic.
Technical view
CVE-2001-0361 affects SSH 1.5 implementations, including OpenSSH up to 2.3.0, AppGate, and ssh-1 up to 1.2.31, in certain configurations. The issue involves PKCS#1 v1.5 handling that may permit session key recovery or traffic modification. No CVSS, CWE, or detailed affected CPE data is provided in the source bundle.
Likely exposure
Exposure is most likely on legacy systems that still run or permit SSH protocol 1/1.5, old OpenSSH builds, AppGate deployments, or ssh-1 up to 1.2.31. Internet-facing administrative services increase business risk.
Exploitation context
The sources describe remote attack potential against certain SSH 1.5 configurations. The CVE is not listed as KEV in the provided bundle, and no cited source confirms active exploitation. Evidence is limited to public vulnerability records.
Researcher notes
The public record is sparse: no CVSS, CWE, CPE list, or patch detail is included. The key research task is determining whether SSHv1/1.5 or the named legacy implementations remain in use. Avoid assuming exploitation without additional evidence.
Mitigation direction
- Inventory systems for SSH protocol 1/1.5 and affected legacy SSH products.
- Check vendor guidance for supported versions and configuration changes.
- Prioritize replacement or upgrade of unsupported SSH implementations.
- Restrict network access to any legacy SSH service pending remediation.
- Document compensating controls where immediate replacement is not possible.
Validation and detection
- Review asset inventory for OpenSSH up to 2.3.0, AppGate, or ssh-1 up to 1.2.31.
- Confirm whether any SSH service permits protocol 1 or 1.5.
- Check exposure of legacy SSH services to untrusted networks.
- Verify vendor-supported SSH versions are deployed after remediation.
- Record exceptions with owner, business purpose, and retirement date.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2001-0361 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- ssh-session-key-recovery(6082)CVE reference · vdb-entry, x_refsource_XF
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.