Linux Kernel 5.0.21 ext4 Image fs/ext4/xattr.c ext4_xattr_set_entry out-of-bounds write

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $5k-$25k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Linux Kernel 5.0.21. Affected by this issue is the function ext4_xattr_set_entry of the file fs/ext4/xattr.c of the component ext4 Image Handler. The manipulation leads to out-of-bounds write.
This vulnerability is uniquely identified as CVE-2019-19319. Local access is required to approach this attack. No exploit exists.
Details
A vulnerability, which was classified as critical, has been found in Linux Kernel 5.0.21 (Operating System). This issue affects the function ext4_xattr_set_entry of the file fs/ext4/xattr.c of the component ext4 Image Handler. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. Using CWE to declare the problem leads to CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
In the Linux kernel 5.0.21, a setxattr operation, after a mount of a crafted ext4 image, can cause a slab-out-of-bounds write access because of an ext4_xattr_set_entry use-after-free in fs/ext4/xattr.c when a large old_size value is used in a memset call.
The weakness was disclosed 11/27/2019. The identification of this vulnerability is CVE-2019-19319 since 11/26/2019. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 02/28/2024).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-146476 and VDB-146473 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.5
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
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-bounds writeCWE: CWE-787 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Patch: git.kernel.org
Timeline
11/26/2019 🔍11/27/2019 🔍
11/28/2019 🔍
02/28/2024 🔍
Sources
Vendor: kernel.orgAdvisory: USN-4391-1
Status: Not defined
CVE: CVE-2019-19319 (🔍)
GCVE (CVE): GCVE-0-2019-19319
GCVE (VulDB): GCVE-100-146477
See also: 🔍
Entry
Created: 11/28/2019 08:17Updated: 02/28/2024 20:38
Changes: 11/28/2019 08:17 (39), 11/28/2019 08:22 (18), 02/28/2024 20:38 (5)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.