Linux Kernel up to 5.3.11 rtl8xxxu_core.c rtl8xxxu_submit_int_urb resource consumption

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Linux Kernel up to 5.3.11. It has been classified as problematic. This vulnerability affects the function rtl8xxxu_submit_int_urb of the file drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c. This manipulation causes resource consumption.
This vulnerability is registered as CVE-2019-19068. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability has been found in Linux Kernel up to 5.3.11 (Operating System) and classified as problematic. Affected by this vulnerability is the function rtl8xxxu_submit_int_urb of the file drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c. The manipulation with an unknown input leads to a resource consumption vulnerability. The CWE definition for the vulnerability is CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. As an impact it is known to affect availability. The summary by CVE is:
A memory leak in the rtl8xxxu_submit_int_urb() function in drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering usb_submit_urb() failures, aka CID-a2cdd07488e6.
The weakness was published 11/18/2019. This vulnerability is known as CVE-2019-19068 since 11/18/2019. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/23/2024). MITRE ATT&CK project uses the attack technique T1499 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Similar entries are available at VDB-145889, VDB-145888, VDB-145887 and VDB-145886. 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.4VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
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
Class: Resource consumptionCWE: CWE-400 / CWE-404
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
11/18/2019 🔍11/18/2019 🔍
11/18/2019 🔍
02/23/2024 🔍
Sources
Vendor: kernel.orgAdvisory: a2cdd07488e666aa93a49a3fc9c9b1299e27ef3c
Status: Not defined
CVE: CVE-2019-19068 (🔍)
GCVE (CVE): GCVE-0-2019-19068
GCVE (VulDB): GCVE-100-145885
See also: 🔍
Entry
Created: 11/18/2019 17:43Updated: 02/23/2024 10:39
Changes: 11/18/2019 17:43 (38), 11/18/2019 17:48 (18), 02/23/2024 10:33 (5), 02/23/2024 10:39 (1)
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.