CVE-2013-4875
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 · uneditedThe Uboot bootloader on the Verizon Wireless Network Extender SCS-2U01 allows physically proximate attackers to bypass the intended boot process and obtain a login prompt by connecting a crafted HDMI cable and sending a SysReq interrupt.
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 confidenceThe Uboot bootloader on the Verizon Wireless Network Extender SCS-2U01 contains a flaw allowing physically proximate attackers to bypass the intended boot sequence by connecting a crafted HDMI cable and sending a SysReq interrupt, thereby obtaining an unauthorized login prompt.
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= scs-2u01CVSS 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
- Local
- Complexity
- High
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:H/Au:N/C:C/I:C/A:C
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelLocate the physical Network Extender device and inspect its label or packaging for the model number. Alternatively, check procurement records or inventory documentation for the installed base of Verizon Network Extenders.Affected if The device model is exactly scs-2u01 (Verizon Wireless Network Extender SCS-2U01)
-
Verify physical location and access controlsInspect the physical location where the Network Extender is deployed. Check whether the device is in a locked cabinet, secure room, or restricted area with limited physical access.Affected if The device is in an unrestricted or publicly accessible location where a physically proximate attacker could connect cables to it
-
Confirm HDMI or video output exposureExamine the rear or side panel of the device for accessible HDMI, VGA, or other video output ports. Determine if these ports are physically reachable without opening an enclosure.Affected if HDMI or video output ports on the device are exposed and reachable without specialized tools
-
Assess SysReq input pathwayVerify whether a keyboard can be connected to the device (via USB or directly) to send a SysReq interrupt, or whether the HDMI-CEC interface could accept such signals.Affected if The device accepts keyboard input or HDMI-CEC commands that could transmit a SysReq signal
You are affected if you have a Verizon Wireless Network Extender SCS-2U01 device with exposed HDMI/video ports and keyboard input pathways in a physically uncontrolled environment, allowing a proximate attacker to trigger the Uboot bootloader bypass.
Generated from the published advisory. Verify against your own configuration.
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 dataPhysical security controls are the primary mitigation—deploy the device in locked cabinets or secure facilities with restricted access. Hardware redesign would be required to fundamentally eliminate this boot bypass vector.
- Consultation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,336.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-4875 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-4875 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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