Описание
ELSA-2022-2031: libssh security, bug fix, and enhancement update (LOW)
[0.9.6-3]
- Remove STI tests
[0.9.6-2]
- Remove bad patch causing errors
- Adding BuildRequires for openssh (SSHD support)
[0.9.6-1]
- Fix CVE-2021-3634: Fix possible heap-buffer overflow when rekeying with different key exchange mechanism
- Rebase to version 0.9.6
- Rename SSHD_EXECUTABLE to SSH_EXECUTABLE in tests/torture.c
- Resolves: rhbz#1896651, rhbz#1994600
[0.9.4-4]
- Revert previous commit as it is incorrect.
[0.9.6-1]
- Fix CVE-2021-3634: Fix possible heap-buffer overflow when rekeying with different key exchange mechanism (#1978810)
Обновленные пакеты
Oracle Linux 8
Oracle Linux aarch64
libssh
0.9.6-3.el8
libssh-config
0.9.6-3.el8
libssh-devel
0.9.6-3.el8
Oracle Linux x86_64
libssh
0.9.6-3.el8
libssh-config
0.9.6-3.el8
libssh-devel
0.9.6-3.el8
Связанные CVE
Связанные уязвимости
A flaw has been found in libssh in versions prior to 0.9.6. The SSH protocol keeps track of two shared secrets during the lifetime of the session. One of them is called secret_hash 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 zeroed or when it is used again during second key re-exchange.
A flaw has been found in libssh in versions prior to 0.9.6. The SSH protocol keeps track of two shared secrets during the lifetime of the session. One of them is called secret_hash 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 zeroed or when it is used again during second key re-exchange.
A flaw has been found in libssh in versions prior to 0.9.6. The SSH protocol keeps track of two shared secrets during the lifetime of the session. One of them is called secret_hash 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 zeroed or when it is used again during second key re-exchange.
A flaw has been found in libssh in versions prior to 0.9.6. The SSH pr ...
