CVE-2020-10724 [Medium] | Out-of-bounds Read in Data Plane Development Kit

CVE-2020-10724 is rated Low Risk (30.1/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.35%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.09%	0.35%	+0.27%
2	2025-03-30	0.20%	0.09%	-0.11%
3	2025-03-29	—	0.20%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.09%

0.35%

+0.27%

2025-03-30

0.20%

0.09%

-0.11%

2025-03-29

—

0.20%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.1	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:H) They need powerful rights—admin, root, or similar—before this pays off. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	0.8	4.2	[email protected]
4.4	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:H) They need powerful rights—admin, root, or similar—before this pays off. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:N) Service keeps running; no real outage angle.	0.8	3.6	[email protected]
2.1	2.0	LOW	`AV:L/AC:L/Au:N/C:P/I:N/A:N` Click to expand Access vector (AV:L) Requires local access to the target system. Access complexity (AC:L) Exploitation conditions are straightforward and predictable. Authentication (AU:N) No authentication is required. Confidentiality impact (C:P) Partial confidentiality impact. Integrity impact (I:N) No integrity impact. Availability impact (A:N) No availability impact.	3.9	2.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.1

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H): They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

0.8

4.2

[email protected]

4.4

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H): They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:N): Service keeps running; no real outage angle.

0.8

3.6

[email protected]

2.1

2.0

LOW

AV:L/AC:L/Au:N/C:P/I:N/A:N Click to expand

Access vector (AV:L): Requires local access to the target system.
Access complexity (AC:L): Exploitation conditions are straightforward and predictable.
Authentication (AU:N): No authentication is required.
Confidentiality impact (C:P): Partial confidentiality impact.
Integrity impact (I:N): No integrity impact.
Availability impact (A:N): No availability impact.

3.9

2.9

[email protected]

OS Trackers for CVE-2020-10724

vendor	priority	summary	link
`alpine`	medium	CVE-2020-10724: 1 source package rows (openvswitch); 7 state rows across 7 repos (3.17-community, 3.18-community, 3.19-community, 3.20-community, 3.21-community, 3.22-community, edge-community); fixed 7, open 0.	https://security.alpinelinux.org/vuln/CVE-2020-10724
`debian`	not yet assigned	CVE-2020-10724 not yet assigned priority: Debian including 1 source packages (dpdk), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2020-10724
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2020-10724
`suse`	medium	CVE-2020-10724 severity moderate: SUSE including 83 source package names (dpdk, dpdk-18.11.3-3.19.2, …), 178 product×package rows across 43 product lines (SUSE Enterprise Storage 7.1, SUSE Linux Enterprise High Performance Computing 12 SP4, … (43 product lines)): Fixed 110, Known Not Affected 68.	https://www.suse.com/security/cve/CVE-2020-10724/
`ubuntu`	medium	CVE-2020-10724 medium priority: Ubuntu including 1 source packages (dpdk), 6 status rows across 6 suites (bionic, eoan, focal, trusty, upstream, xenial): released 3, not-affected 2, DNE 1.	https://ubuntu.com/security/CVE-2020-10724

Affected software / configurations for CVE-2020-10724

Vendor	Product	Version	Raw CPE
dpdk	data_plane_development_kit	<= 18.11	cpe:2.3:a:dpdk:data_plane_development_kit::::::::
canonical	ubuntu_linux	18.04	cpe:2.3:o:canonical:ubuntu_linux:18.04::::lts:::
canonical	ubuntu_linux	19.10	cpe:2.3:o:canonical:ubuntu_linux:19.10:::::::*
canonical	ubuntu_linux	20.04	cpe:2.3:o:canonical:ubuntu_linux:20.04::::lts:::
fedoraproject	fedora	32	cpe:2.3:o:fedoraproject:fedora:32:::::::*

References for CVE-2020-10724

URL	Tags
http://lists.opensuse.org/opensuse-security-announce/2020-05/msg00045.html	Broken Link Third Party Advisory
https://bugs.dpdk.org/show_bug.cgi?id=269	Issue Tracking Patch Vendor Advisory
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-10724	Issue Tracking Third Party Advisory
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HRHKFVV4MRWNNJOYQOVP64L4UVWYPEO4/
https://usn.ubuntu.com/4362-1/	Third Party Advisory
https://www.openwall.com/lists/oss-security/2020/05/18/2	Mailing List Third Party Advisory
https://www.oracle.com/security-alerts/cpujan2021.html	Third Party Advisory
https://www.oracle.com/security-alerts/cpuoct2020.html	Third Party Advisory

URL

CVE-2020-10724

Exploit prediction scoring system (EPSS) score for CVE-2020-10724

Common vulnerability scoring system (CVSS) metrics for CVE-2020-10724

Weakness enumeration for CVE-2020-10724

OS Trackers for CVE-2020-10724

Affected software / configurations for CVE-2020-10724

References for CVE-2020-10724