Processing sftp server read may cause null dereference
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions |
|---|---|---|---|
| n/a | libssh | affected | — |
| Red Hat | Red Hat Enterprise Linux 7 | unaffected | — |
| Red Hat | Red Hat Enterprise Linux 8 | unaffected | — |
| Red Hat | Red Hat Enterprise Linux 9 | unaffected | — |
| Fedora | Extra Packages for Enterprise Linux 7 | unaffected | — |
| Fedora | Fedora | unaffected | — |
No data.
No data available yet.
Vendor Workaround
The SFTP server implementation is based on callbacks so you can rewrite the sftp_channel_default_data_callback() to provide additional checks. [1] https://gitlab.com/libssh/libssh-mirror/-/blob/master/examples/sample_sftpserver.c#L330
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2023-44252 | A missing allocation check in sftp server processing read requests may cause a NULL dereference on low-memory conditions. The malicious client can request up to 4GB SFTP reads, causing allocation of up to 4GB buffers, which was not being checked for failure. This will likely crash the authenticated user's sftp server connection (if implemented as forking as recommended). For thread-based servers, this might also cause DoS for legitimate users. Given this code is not in any released versions, no security releases have been issued. |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.903% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|