high
8.8
CWE
190 787
Advisory Published
CVE Published
Updated

CVE-2019-3857: Integer Overflow

First published: Mon Mar 11 2019(Updated: )

A server could send a SSH_MSG_CHANNEL_REQUEST packet with an exit signal message with a length of max unsigned integer value. The length would then have a value of 1 added to it and used to allocate memory causing a possible memory write out of bounds error or zero byte allocation.

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
Libssh2 Libssh2>=1.2.8<=1.8.0
Debian Debian Linux=8.0
Debian Debian Linux=9.0
NetApp ONTAP Select Deploy administration utility
openSUSE Leap=15.0
openSUSE Leap=42.3
Redhat Enterprise Linux=8.0
Redhat Enterprise Linux Desktop=7.0
Redhat Enterprise Linux Server=7.0
Redhat Enterprise Linux Server Aus=7.6
Redhat Enterprise Linux Server Eus=7.6
Redhat Enterprise Linux Server Tus=7.6
Redhat Enterprise Linux Workstation=7.0
Fedoraproject Fedora=28
Oracle PeopleSoft Enterprise PeopleTools=8.56
Oracle PeopleSoft Enterprise PeopleTools=8.57
debian/libssh2
1.8.0-2.1
1.8.0-2.1+deb10u1
1.9.0-2
1.10.0-3
1.11.0-2

Remedy

https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3857

Remedy

https://www.libssh2.org/CVE-2019-3857.html

Remedy

https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is CVE-2019-3857?

    CVE-2019-3857 is an integer overflow vulnerability discovered in libssh2 before 1.8.1.

  • What is the severity of CVE-2019-3857?

    CVE-2019-3857 has a severity level of 8.8 (high).

  • How does CVE-2019-3857 impact the affected software?

    CVE-2019-3857 could lead to an out of bounds write in the way SSH_MSG_CHANNEL_REQUEST packets with an exit signal are parsed, potentially allowing a remote attacker to execute code on the client system.

  • Which versions of libssh2 are affected by CVE-2019-3857?

    Versions of libssh2 before 1.8.1 are affected by CVE-2019-3857.

  • How can I fix CVE-2019-3857?

    To fix CVE-2019-3857, you should update libssh2 to version 1.8.1 or later.

Company

Resources

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.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203