Security readout for executives and security teams
Plain-English summary
This flaw affects a specific Comcast firmware build for Cisco DPC3939 gateways. It may let a local user, or someone who already gained command access, read files from the device. The sources do not provide CVSS, confirmed exploitation, or a vendor fix.
Executive priority
Prioritize asset identification first. Business urgency rises if affected gateways are still in production, manage sensitive network traffic, or have weak local access controls.
Technical view
CVE-2017-9480 describes arbitrary file read in Comcast firmware dpc3939-P20-18-v303r20421746-170221a-CMCST on Cisco DPC3939 devices via UPnP access to /var/IGD/. The CVE notes local access and references command access obtained through CVE-2017-9479 as an example precondition.
Likely exposure
Likely limited to organizations using Comcast-provided Cisco DPC3939 gateways on the named firmware build. Exposure appears local or post-compromise, not clearly internet-remote from the supplied evidence.
Exploitation context
The source bundle does not show KEV listing, public active exploitation, or exploit maturity. The CVE text frames exploitation by local users, including users with command access after CVE-2017-9479 exploitation.
Researcher notes
Evidence is narrow: one CVE description and one Bastille advisory reference. The supplied data names one firmware build and attack surface, but no CVSS, CWE, patch status, or verified exploitation.
Mitigation direction
- Inventory Cisco DPC3939 gateways and confirm the exact Comcast firmware build.
- Check Comcast and Cisco guidance for fixed firmware or replacement options.
- Limit local administrative and command access to affected gateways.
- Segment or replace unsupported affected gateways where vendor fixes are unavailable.
Validation and detection
- Confirm whether any Cisco DPC3939 devices run the named Comcast firmware.
- Review device management exposure and who can obtain local or command access.
- Check logs for unusual UPnP or administrative activity on affected gateways.
- Document any dependency on CVE-2017-9479 for realistic attack paths.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2017-9480 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/BastilleResearch/CableTap/blob/master/doc/advisories/bastille-23.upnp-directory-write.txtCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.