Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

Infinite Loop in scapy

CVE-2019-1010142GHSA-mpf2-q34c-fc6j

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (scapy 2.4.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI scapy

    Affected
    >= 2.4rc1, < 2.4.1
    Fixed in
    2.4.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2019-1010142: 2.79% estimated exploitation activity in the next 30 days; percentile 86.44 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

scapy is affected by a Denial of Service vulnerability resulting in an infinite loop and resource consumption rendering the program unresponsive. The component is: RADIUSAttrPacketListField.getfield(self..). The attack vector is over the network or in a pcap. both work.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-mpf2-q34c-fc6j

  2. Revision 1 · created ·

    Published from osv record PYSEC-2019-120

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2019-1010142

Advisory: Infinite Loop in scapy
IDs: CVE-2019-1010142, GHSA-mpf2-q34c-fc6j
Record: https://patchnext.com/advisories/cve-2019-1010142 (revision 2, source checked 26 Oct 2026, 13:22 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: scapy 2.4.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI scapy: affected >= 2.4rc1, < 2.4.1; fixed in 2.4.1

## Suggested inspection (read-only)
- `python -m pip show scapy`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on scapy.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/PYSEC-2019-120 (OSV record PYSEC-2019-120 lists affected ranges: PyPI scapy >=0 <2.4.1 (fixed))
- Verified: https://github.com/advisories/GHSA-mpf2-q34c-fc6j (GitHub-reviewed advisory GHSA-mpf2-q34c-fc6j lists affected ranges: PyPI scapy >=2.4rc1 <2.4.1)

Commands are suggestions: review each one before running it.

Loading voting…