Approved changes feed: RSS · Atom
cpe:2.3:a:sshnet:ssh.net:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Sshnet (e37260d2-cfe1-5391-b140-67cedfe4de04) |
|---|---|
| Product | Ssh.Net (e379ace6-04c8-51c7-b0f5-39078d61b0c7) |
| 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-2026-85756 |
vulnerable | 2026-10-13 12:28:54.111118 |
SSH.NET: ScpClient allows server-side RCE via default SCP path handling
HIGH (7.5)
SSH.NET is a Secure Shell (SSH) library for .NET. Prior to 2026.0.0, ScpClient places caller-supplied remote paths into the command used to run scp on the server, and the default RemotePathTransformation.DoubleQuote transformation cannot safely quote every remote command interpreter. When an application passes an attacker-controlled path to a shell-based server, shell metacharacters not neutralized by the active IRemotePathTransformation can execute commands as the authenticated SSH user. Exploitation requires a shell-based server and a path crafted for that shell's parsing rules; non-shell servers and paths fully neutralized by the selected transformation are not affected. RemotePathTransformation.ShellQuote is available for POSIX shells, while SftpClient avoids a remote shell entirely. This issue is fixed in version 2026.0.0.
Published: 2026-09-16T16:31:24.630Z
Updated: 2026-09-16T18:34:33.535Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-29245 |
vulnerable | 2026-06-08 05:42:47.407682 |
Weak private key generation in SSH.NET
MEDIUM (6.5)
SSH.NET is a Secure Shell (SSH) library for .NET. In versions 2020.0.0 and 2020.0.1, during an `X25519` key exchange, the client’s private key is generated with `System.Random`. `System.Random` is not a cryptographically secure random number generator, it must therefore not be used for cryptographic purposes. When establishing an SSH connection to a remote host, during the X25519 key exchange, the private key is generated with a weak random number generator whose seed can be brute forced. This allows an attacker who is able to eavesdrop on the communications to decrypt them. Version 2020.0.2 contains a patch for this issue. As a workaround, one may disable support for `curve25519-sha256` and `curve25519-sha256@libssh.org` key exchange algorithms.
Published: 2022-05-31T16:35:11.000Z
Updated: 2025-04-22T17:55:45.721Z Reference links
|
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.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.