FreshPorts - VuXML

This page displays vulnerability information about FreeBSD Ports.

The VUXML data was last processed by FreshPorts on 2024-12-18 00:09:58 UTC

List all Vulnerabilities, by package

List all Vulnerabilities, by date

k68

These are the vulnerabilities relating to the commit you have selected:

VuXML ID	Description
3d7dfd63-823b-11ea-b3a8-240a644dd835	Client/server denial of service when handling AES-CTR ciphers The libssh team reports (originally reported by Yasheng Yang from Google): A malicious client or server could crash the counterpart implemented with libssh AES-CTR ciphers are used and don't get fully initialized. It will crash when it tries to cleanup the AES-CTR ciphers when closing the connection. Discovery 2020-01-25 Entry 2020-04-19 libssh >= 0.8.0 lt 0.8.9 >= 0.9.0 lt 0.9.4 https://www.libssh.org/security/advisories/CVE-2020-1730.txt" CVE-2020-1730
57b1ee25-1a7c-11ec-9376-0800272221cc	libssh -- possible heap-buffer overflow vulnerability libssh security advisories: The SSH protocol keeps track of two shared secrets during the lifetime of the session. One of them is called `secret_hash` and and the other `session_id`. Initially, both of them are the same, but after key re-exchange, previous `session_id` is kept and used as an input to new `secret_hash`. Historically, both of these buffers had shared length variable, which worked as long as these buffers were same. But the key re-exchange operation can also change the key exchange method, which can be based on hash of different size, eventually creating `secret_hash` of different size than the `session_id` has. This becomes an issue when the `session_id` memory is zeroized or when it is used again during second key re-exchange. Discovery 2021-08-26 Entry 2021-09-21 libssh >= 0.9.1 le 0.9.5 CVE-2021-3634 https://www.libssh.org/security/advisories/CVE-2021-3634.txt https://www.libssh.org/2021/08/26/libssh-0-9-6-security-release/

VuXML ID

Description

3d7dfd63-823b-11ea-b3a8-240a644dd835

Client/server denial of service when handling AES-CTR ciphers

The libssh team reports (originally reported by Yasheng Yang from Google):

A malicious client or server could crash the counterpart implemented with libssh AES-CTR ciphers are used and don't get fully initialized. It will crash when it tries to cleanup the AES-CTR ciphers when closing the connection.

Discovery 2020-01-25
Entry 2020-04-19
libssh

>= 0.8.0 lt 0.8.9

>= 0.9.0 lt 0.9.4

https://www.libssh.org/security/advisories/CVE-2020-1730.txt"
CVE-2020-1730

57b1ee25-1a7c-11ec-9376-0800272221cc

libssh -- possible heap-buffer overflow vulnerability

libssh security advisories:

The SSH protocol keeps track of two shared secrets during the lifetime of the session. One of them is called `secret_hash` and and the other `session_id`. Initially, both of them are the same, but after key re-exchange, previous `session_id` is kept and used as an input to new `secret_hash`.

Historically, both of these buffers had shared length variable, which worked as long as these buffers were same. But the key re-exchange operation can also change the key exchange method, which can be based on hash of different size, eventually creating `secret_hash` of different size than the `session_id` has.

This becomes an issue when the `session_id` memory is zeroized or when it is used again during second key re-exchange.

Discovery 2021-08-26
Entry 2021-09-21
libssh

>= 0.9.1 le 0.9.5

CVE-2021-3634
https://www.libssh.org/security/advisories/CVE-2021-3634.txt
https://www.libssh.org/2021/08/26/libssh-0-9-6-security-release/