| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.0 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in Libssh2 up to 1.8.0. Impacted is an unknown function. The manipulation as part of Exit Status results in out-of-bounds. This vulnerability is cataloged as CVE-2019-3862. The attack may be launched remotely. There is no exploit available. You should upgrade the affected component.
Details
A vulnerability classified as critical has been found in Libssh2 up to 1.8.0. Affected is some unknown functionality. The manipulation as part of a Exit Status leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
An out of bounds read flaw was discovered in libssh2 before 1.8.1 in the way SSH_MSG_CHANNEL_REQUEST packets with an exit status message and no payload are parsed. A remote attacker who compromises a SSH server may be able to cause a Denial of Service or read data in the client memory.
The bug was discovered 03/18/2019. The weakness was shared 03/21/2019 by Chris Coulson as confirmed bug report (Bugzilla). The advisory is available at bugzilla.redhat.com. This vulnerability is traded as CVE-2019-3862 since 01/03/2019. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. The technical details are unknown and an exploit is not available.
The vulnerability was handled as a non-public zero-day exploit for at least 3 days. During that time the estimated underground price was around $0-$5k. The commercial vulnerability scanner Qualys is able to test this issue with plugin 172157 (SUSE Enterprise Linux Security Update for libssh2_org (SUSE-SU-2019:13982-1)).
Upgrading to version 1.8.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 107485†). The entries VDB-131993, VDB-132104, VDB-132105 and VDB-132210 are related to this item. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.2VulDB Meta Temp Score: 8.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.1
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Out-of-boundsCWE: CWE-125 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Libssh2 1.8.1
Timeline
01/03/2019 🔍03/18/2019 🔍
03/18/2019 🔍
03/21/2019 🔍
03/22/2019 🔍
08/03/2023 🔍
Sources
Advisory: RHSA-2019:1884Researcher: Chris Coulson
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2019-3862 (🔍)
GCVE (CVE): GCVE-0-2019-3862
GCVE (VulDB): GCVE-100-131994
SecurityFocus: 107485 - libssh2 Multiple Security Vulnerabilities
See also: 🔍
Entry
Created: 03/22/2019 08:27Updated: 08/03/2023 23:23
Changes: 03/22/2019 08:27 (63), 05/18/2020 12:35 (5), 08/03/2023 23:23 (4)
Complete: 🔍
Cache ID: 216:AA0:103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.