libyal libfwsi libfwsi_extension_block.c libfwsi_extension_block_copy_from_byte_stream out-of-bounds ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in libyal libfwsi and classified as critical. This affects the function libfwsi_extension_block_copy_from_byte_stream of the file libfwsi_extension_block.c. The manipulation results in out-of-bounds.
This vulnerability is identified as CVE-2019-17263. The attack is only possible with local access. There is not any exploit available.
There are still doubts about whether this vulnerability truly exists.
It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in libyal libfwsi (the affected version is unknown). Affected is the function libfwsi_extension_block_copy_from_byte_stream of the file libfwsi_extension_block.c. The manipulation with an unknown input 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:
In libyal libfwsi before 20191006, libfwsi_extension_block_copy_from_byte_stream in libfwsi_extension_block.c has a heap-based buffer over-read because rejection of an unsupported size only considers values less than 6, even though values of 6 and 7 are also unsupported.
The weakness was released 10/06/2019. This vulnerability is traded as CVE-2019-17263 since 10/06/2019. Local access is required to approach this attack. The exploitation doesn't require any form of authentication. Technical details are known, but there is no available exploit.
The real existence of this vulnerability is still doubted at the moment.
Upgrading eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 3.3
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: Partially
Local: Yes
Remote: No
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: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
10/06/2019 🔍10/06/2019 🔍
10/06/2019 🔍
10/07/2019 🔍
08/05/2024 🔍
Sources
Advisory: 154774Status: Not defined
Disputed: 🔍
CVE: CVE-2019-17263 (🔍)
GCVE (CVE): GCVE-0-2019-17263
GCVE (VulDB): GCVE-100-142986
Entry
Created: 10/07/2019 07:43Updated: 08/05/2024 05:13
Changes: 10/07/2019 07:43 (37), 09/24/2020 16:57 (17), 01/03/2024 17:58 (4), 06/19/2024 00:03 (15), 08/05/2024 05:13 (2)
Complete: 🔍
Cache ID: 216::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.