CVE-2023-2283: GHSL-2023-085: Authentication bypass in libssh - CVE-2023-2283

Published Apr 26, 2023
·
Updated

A vulnerability was found in libssh, where the authentication check of the connecting client can be bypassed in thepkiverifydatasignature function in memory allocation problems. This issue may happen if there is insufficient memory or the memory usage is limited. The problem is caused by the return value rc, which is initialized to SSHERROR and later rewritten to save the return value of the function call pkikeycheckhashcompatible. The value of the variable is not changed between this point and the cryptographic verification. Therefore any error between them calls goto error returning SSHOK.

Other sources

libssh could allow a remote attacker to bypass security restrictions, caused by a memory allocation flaw in thepkiverifydatasignature function. By sending a specially crafted request, an attacker could exploit this vulnerability to bypass the authentication check of the connecting client.

IBM

The authentication check of the connecting client can be bypassed in the function pkiverifydatasignature in circumstances of memory allocation problems. This may happen f.e. if not enough memory or the memory usage is limited.

The problem is caused by the return value rc, which is initialized to SSHERROR and later rewritten to save the return value of the function call pkikeycheckhashcompatible. The value of the variable is not changed between this point and the cryptographic verification, therefore any error between them calls goto error returning SSHOK.

Red Hat

The public key signature checking code in pkiverifydatasignature has a logic bug, which, under certain conditions, could enable an attacker to bypass the check.

GitHub Security Lab

Affected Software

9 affected componentsFixes available
redhat/libssh<0:0.9.6-10.el8_8
0:0.9.6-10.el8_8
libssh libssh>=0.9.1<=0.9.6
libssh libssh>=0.10.0<=0.10.4
Fedoraproject Fedora=37
redhat Enterprise Linux=8.0
redhat Enterprise Linux=9.0
IBM R10.0<=10.1.3.0 10.0.245.0
IBM R9.4<=89.42.18.0 89.41.25.0 89.40.83.0
IBM R9.3<=89.33.52.0 89.33.45.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/libssh to a version that resolves this vulnerability.

    Fixed in 0:0.9.6-10.el8_8

Event History

Apr 26, 2023
Data Sourced
via Red Hat·04:06 AM
DescriptionSeverityAffected Software
May 5, 2023
CVE Published
12:00 AM
May 9, 2023
Advisory Published
via GitHub Security Lab·12:00 AM
Data Sourced
via GitHub Security Lab·12:00 AM
DescriptionAffected Software
May 26, 2023
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionWeakness
Data Sourced
06:15 PM
Description
Data Sourced
via NVD·06:15 PM
DescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2023-2283?

CVE-2023-2283 is a vulnerability found in libssh that allows the authentication check of the connecting client to be bypassed.

2

What is the severity of CVE-2023-2283?

The severity of CVE-2023-2283 is medium with a CVSS score of 6.5.

3

How does CVE-2023-2283 affect Libssh?

CVE-2023-2283 affects Libssh versions 0.9.1 to 0.9.6 and versions 0.10.0 to 0.10.4.

4

How can I fix CVE-2023-2283?

To fix CVE-2023-2283, update to libssh version 0.9.6-10.el8_8 or apply the necessary patches from the official sources.

5

Where can I find more information about CVE-2023-2283?

You can find more information about CVE-2023-2283 on the official Red Hat and libssh websites.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203