| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in dpdk up to 18.11.9/19.11.4. It has been rated as problematic. This vulnerability affects the function move_desc. Performing a manipulation results in integer overflow.
This vulnerability is cataloged as CVE-2020-14378. There is no exploit available.
Upgrading the affected component is advised.
Details
A vulnerability classified as problematic has been found in dpdk up to 18.11.9/19.11.4. This affects the function move_desc. The manipulation with an unknown input leads to a integer overflow vulnerability. CWE is classifying the issue as CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. This is going to have an impact on availability. The summary by CVE is:
An integer underflow in dpdk versions before 18.11.10 and before 19.11.5 in the `move_desc` function can lead to large amounts of CPU cycles being eaten up in a long running loop. An attacker could cause `move_desc` to get stuck in a 4,294,967,295-count iteration loop. Depending on how `vhost_crypto` is being used this could prevent other VMs or network tasks from being serviced by the busy DPDK lcore for an extended period.
The weakness was shared 09/30/2020 as Bug 1879473 as not defined bug report (Bugzilla). It is possible to read the advisory at bugzilla.redhat.com. This vulnerability is uniquely identified as CVE-2020-14378 since 06/17/2020. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 18.11.10 or 19.11.5 eliminates this vulnerability.
The entries VDB-162098, VDB-162097, VDB-162096 and VDB-162095 are related to this item. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
- 18.11.0
- 18.11.1
- 18.11.2
- 18.11.3
- 18.11.4
- 18.11.5
- 18.11.6
- 18.11.7
- 18.11.8
- 18.11.9
- 19.11.0
- 19.11.1
- 19.11.2
- 19.11.3
- 19.11.4
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.3
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.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: Integer overflowCWE: CWE-190 / CWE-189
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: 🔍
0-Day Time: 🔍
Upgrade: dpdk 18.11.10/19.11.5
Timeline
06/17/2020 🔍09/30/2020 🔍
10/01/2020 🔍
11/15/2020 🔍
Sources
Advisory: Bug 1879473Status: Not defined
CVE: CVE-2020-14378 (🔍)
GCVE (CVE): GCVE-0-2020-14378
GCVE (VulDB): GCVE-100-162099
See also: 🔍
Entry
Created: 10/01/2020 09:33Updated: 11/15/2020 06:54
Changes: 10/01/2020 09:33 (40), 10/01/2020 09:38 (3), 11/14/2020 09:32 (5), 11/15/2020 06:54 (14)
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.