Yubico libu2f-host up to 1.1.7 devs.c Memory memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Yubico libu2f-host up to 1.1.7. This impacts an unknown function of the file devs.c. This manipulation causes memory corruption (Memory). This vulnerability is handled as CVE-2019-9578. The attack can be initiated remotely. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability was found in Yubico libu2f-host up to 1.1.7. It has been declared as problematic. Affected by this vulnerability is some unknown functionality of the file devs.c. The manipulation with an unknown input leads to a memory corruption vulnerability (Memory). The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality. The summary by CVE is:
In devs.c in Yubico libu2f-host before 1.1.8, the response to init is misparsed, leaking uninitialized stack memory back to the device.
The bug was discovered 02/22/2019. The weakness was released 03/05/2019 (Website). It is possible to read the advisory at lists.fedoraproject.org. This vulnerability is known as CVE-2019-9578 since 03/05/2019. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit.
The vulnerability was handled as a non-public zero-day exploit for at least 11 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 1.1.8 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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
Name: MemoryClass: Memory corruption / Memory
CWE: 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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: libu2f-host 1.1.8
Patch: github.com
Timeline
02/22/2019 🔍03/05/2019 🔍
03/05/2019 🔍
03/06/2019 🔍
07/26/2023 🔍
Sources
Product: github.comAdvisory: e4bb58cc8b6202a421e65f8230217d8ae6e16eb5
Status: Not defined
CVE: CVE-2019-9578 (🔍)
GCVE (CVE): GCVE-0-2019-9578
GCVE (VulDB): GCVE-100-131371
Entry
Created: 03/06/2019 08:56Updated: 07/26/2023 18:05
Changes: 03/06/2019 08:56 (58), 05/14/2020 09:17 (2), 07/26/2023 17:58 (5), 07/26/2023 18:05 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.