Linux Kernel up to 5.3.9 dwc3-pci.c dwc3_pci_probe resource consumption

CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.4 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Linux Kernel up to 5.3.9 and classified as problematic. This vulnerability affects the function dwc3_pci_probe
of the file drivers/usb/dwc3/dwc3-pci.c. The manipulation leads to resource consumption.
This vulnerability was named CVE-2019-18813. The attack can be initiated remotely. There is no exploit available.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Details
A vulnerability, which was classified as problematic, was found in Linux Kernel up to 5.3.9 (Operating System). This affects the function dwc3_pci_probe
of the file drivers/usb/dwc3/dwc3-pci.c. The manipulation with an unknown input leads to a resource consumption vulnerability. CWE is classifying the issue as 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. This is going to have an impact on availability. The summary by CVE is:
A memory leak in the dwc3_pci_probe() function in drivers/usb/dwc3/dwc3-pci.c in the Linux kernel through 5.3.9 allows attackers to cause a denial of service (memory consumption) by triggering platform_device_add_properties() failures, aka CID-9bbfceea12a8.
The weakness was disclosed 11/07/2019. This vulnerability is uniquely identified as CVE-2019-18813 since 11/07/2019. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/05/2024). The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-145228, VDB-145226, VDB-145225 and VDB-145224 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
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: 🔍
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: git.kernel.org
Timeline
11/07/2019 🔍11/07/2019 🔍
11/08/2019 🔍
02/05/2024 🔍
Sources
Vendor: kernel.orgAdvisory: USN-4225-1
Status: Not defined
CVE: CVE-2019-18813 (🔍)
GCVE (CVE): GCVE-0-2019-18813
GCVE (VulDB): GCVE-100-145227
See also: 🔍
Entry
Created: 11/08/2019 11:22 AMUpdated: 02/05/2024 03:39 PM
Changes: 11/08/2019 11:22 AM (38), 11/08/2019 11:27 AM (18), 02/05/2024 03:39 PM (5)
Complete: 🔍
Cache ID: 18:400:40
No comments yet. Languages: en.
Please log in to comment.