CVE-2019-1010142: scapy 2.4.0 is affected by: Denial of Service

This week

HIGH 7.5REMOTEDOWNGRADEMITIGATE

CVE-2019-1010142 is a high-severity flaw (CVSS 7.5) affecting scapy, fedora. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

scapy 2.4.0 is affected by: Denial of Service. The impact is: infinite loop, resource consumption and program unresponsive. The component is: _RADIUSAttrPacketListField.getfield(self..). The attack vector is: over the network or in a pcap. both work.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.8% (top 14%)
CISA exploited list	No
Weakness	CWE-835
Published	2019-07-19
Last modified	2026-06-17

Publisher (CNA): DWF · Vendor: fedoraproject · scapy

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-07-19 16:15 UTCPublished CVE record published
2026-06-17 02:09 UTCUpdated Record last modified

scapy scapy DOWNGRADE

Affected: 2.4.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.4.0

1. Check installed version

apt-cache policy scapy || rpm -q scapy || scapy --version

2. No fixed release: DOWNGRADE to a release before 2.4.0 (Debian / Ubuntu)

apt-cache madison scapy sudo apt install scapy=<VERSION_BEFORE_2.4.0> sudo apt-mark hold scapy

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list scapy sudo dnf downgrade scapy-<VERSION_BEFORE_2.4.0> sudo dnf versionlock add scapy

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

fedoraproject fedora MITIGATE

Affected: 29 · 30

Fixed in: no fixed release known

Safe to downgrade to: a release before 29

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-1010142?

scapy: downgrade or apply the listed mitigation; fedora: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2019-1010142 being exploited?

CVE-2019-1010142 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-1010142 affect?

CVE-2019-1010142 affects scapy, fedora. Severity is high (CVSS 7.5). scapy 2.4.0 is affected by: Denial of Service. The impact is: infinite loop, resource consumption and program unresponsive. The component is: _RADIUSAttrPacketListField.getfield(self..). The attack vector is: over the network or in a pcap.

How urgent is CVE-2019-1010142?

Priority 58/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs