Airport Base Station FirmwareOperating system · Apple

CVE-2019-8580

HIGH · 7.5 CVSS v3.1 Published 2020-10-27
Fix available
A fix is available. Upgrade to 7.8.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Source-routed IPv4 packets were disabled by default. This issue is fixed in AirPort Base Station Firmware Update 7.8.1, AirPort Base Station Firmware Update 7.9.1. Source-routed IPv4 packets may be unexpectedly accepted.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The AirPort Base Station firmware had a vulnerability where source-routed IPv4 packets were unexpectedly accepted instead of being rejected by default. Source routing allows a sender to specify the path a packet takes through the network, which can be exploited to bypass security controls, perform man-in-the-middle attacks, or circumvent network segmentation.

MitigationUpdate AirPort Base Station firmware to version 7.8.1 or 7.9.1 (or later) to ensure source-routed IPv4 packets are disabled by default, as per the vendor fix.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Airport Base Station FirmwareOperating system
Affected:< 7.8.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device as an AirPort Base Station
    Access the AirPort Utility application on a Mac (found in /Applications/Utilities/) or use the AirPort Base Station admin web interface by entering the device's IP address in a browser. Confirm the device model is an Apple AirPort Base Station (including Express, Extreme, or Time Capsule variants).
    Affected if The device is any model of Apple AirPort Base Station.
  2. Check the installed firmware version
    In AirPort Utility, select the base station and click 'Edit' then 'Version' to display the firmware version. Alternatively, access the web admin interface at the base station's IP address and navigate to the status or summary page to view the firmware build number.
    Affected if The displayed firmware version is below 7.8.1 (for example, 7.7.9, 7.6.x, or earlier).
  3. Verify source-routed IPv4 packet handling
    Access the AirPort Base Station web admin interface and navigate to the Network or Advanced settings tab. Look for options related to 'IP Forwarding', 'Source Routing', or 'Router' settings. Check whether source-routed packets are explicitly allowed or blocked.
    Affected if Source-routed IPv4 packets are explicitly allowed or the option to reject source-routed packets is missing or disabled.
  4. Test for source routing acceptance externally
    From an external host, use a tool like hping3 or scapy to send ICMP packets with source routing options (such as -s flag in hping3) targeting the AirPort Base Station's public IP. A vulnerable device will accept and process these packets; a patched device will reject them.
    Affected if The AirPort Base Station responds to or processes source-routed packets (the packets are not dropped at the network perimeter).

A user is affected if they are running an AirPort Base Station with firmware version below 7.8.1 and source-routed IPv4 packets are being accepted by the device.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 7.8.1 or later
Fixed in 7.8.1
Interim mitigation

Update AirPort Base Station firmware to version 7.8.1 or 7.9.1 (or later) to ensure source-routed IPv4 packets are disabled by default, as per the vendor fix.

Fix this in Airport Base Station Firmware Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-8580 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-8580 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data