Spa501g FirmwareOperating system · Cisco
CVE-2019-1923
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 · uneditedA vulnerability in Cisco Small Business SPA500 Series IP Phones could allow a physically proximate attacker to execute arbitrary commands on the device. The vulnerability is due to improper input validation in the device configuration interface. An attacker could exploit this vulnerability by accessing the configuration interface, which may require a password, and then accessing the device's physical interface and inserting a USB storage device. A successful exploit could allow the attacker to execute arbitrary commands on the device in an elevated security context. At the time of publication, this vulnerability affected Cisco Small Business SPA500 Series IP Phones firmware releases 7.6.2SR5 and prior.
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 confidenceCommand injection vulnerability in Cisco Small Business SPA500 Series IP phones due to improper input validation in the device configuration interface. A physically proximate attacker who accesses the configuration interface (potentially password-protected) and then uses the physical USB port can inject and execute arbitrary commands in an elevated security context.
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
Spa501g FirmwareOperating system
<= 7.6.2sr5
Spa502g FirmwareOperating system
<= 7.6.2sr5
Spa504g FirmwareOperating system
<= 7.6.2sr5
Spa508g FirmwareOperating system
<= 7.6.2sr5
Spa509g FirmwareOperating system
<= 7.6.2sr5
Spa512g FirmwareOperating system
<= 7.6.2sr5
Spa514g FirmwareOperating system
<= 7.6.2sr5
Spa525g2 FirmwareOperating system
<= 7.6.2sr5CVSS 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
- Physical
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 phone modelPhysically inspect the device or check the configuration interface under Admin Login > System > Product Info to confirm the model number (SPA501g, SPA502g, SPA504g, SPA508g, SPA509g, SPA512g, SPA514g, or SPA525g2)Affected if The model is any of the eight listed affected models
-
Check the installed firmware versionAccess the web-based configuration interface, log in as admin, and navigate to Admin Login > System > Product Info to view the firmware version numberAffected if The firmware version is 7.6.2sr5 or lower
-
Verify configuration interface password statusNavigate to Admin Login > Web Server in the configuration interface and confirm whether a password is set for administrative accessAffected if The configuration interface has no password or uses default credentials, allowing easier exploitation
-
Check USB port configurationInspect the device hardware to confirm the presence of an active USB port; in the configuration interface, check Admin Login > Hardware > USB settings if availableAffected if The device has an accessible USB port that can be used for the injection vector
A user is affected if they have any of the eight listed SPA500 series models running firmware version 7.6.2sr5 or lower, with an accessible configuration interface and an active USB port available for physical proximity exploitation.
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 dataUpdate phone firmware beyond 7.6.2SR5 when patches are released; restrict physical access to devices; enforce strong configuration interface passwords; consider network isolation of voice infrastructure.
Fix this in Spa501g Firmware
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1923 — 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-2019-1923 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