dbcve.org
Dpc3939 Wireless Residential Voice Gateway FirmwareOperating system · Cisco

CVE-2015-6361

MEDIUM · 6.5 CVSS v2.0 Published 2015-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
The administrative web interface on Cisco DPC3939 (XB3) devices with firmware 121109aCMCST allows remote authenticated users to execute arbitrary commands via unspecified fields, aka Bug ID CSCuw86170.

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 administrative web interface on Cisco DPC3939 (XB3) devices with firmware 121109aCMCST contains a command injection vulnerability allowing remote authenticated users to execute arbitrary operating system commands via unspecified input fields in the web management interface.

MitigationApply vendor firmware updates if available; otherwise, restrict administrative web interface access to trusted networks only, disable remote management if not required, and monitor for unauthorized access attempts.

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
Dpc3939 Wireless Residential Voice Gateway FirmwareOperating system
Affected:= 121109acmcst_base

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
Authentication
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:S/C:P/I:P/A:P

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 model
    Access the device administrative interface or check the device label/marketing materials to confirm the model is Cisco DPC3939 (XB3) Wireless Residential Voice Gateway
    Affected if The device is not a Cisco DPC3939 (XB3)
  2. Check the firmware version
    Log into the administrative web interface and navigate to the status or firmware information page, or use the device's web-based diagnostic tools to display the current firmware version
    Affected if The firmware version is exactly 121109acmcst_base (this specific version is vulnerable)
  3. Verify the administrative web interface is enabled
    Attempt to access the device's web management interface via HTTP or HTTPS on the default management ports (typically 80 or 443)
    Affected if The administrative web interface responds and is accessible
  4. Check if remote management is enabled
    In the administrative interface, navigate to the remote management or administration settings to determine if remote web access is permitted from outside the local network
    Affected if Remote management is enabled and the web interface is accessible from external networks
  5. Assess network exposure of the management interface
    Determine if the device's web management port is exposed to untrusted networks by checking router/firewall port forwarding rules or NAT configurations
    Affected if The administrative interface is reachable from untrusted networks (such as the internet)

A user is affected if they have a Cisco DPC3939 (XB3) device running firmware version 121109acmcst_base with the administrative web interface accessible, particularly if remote management is enabled or the interface is exposed to untrusted networks.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware updates if available; otherwise, restrict administrative web interface access to trusted networks only, disable remote management if not required, and monitor for unauthorized access attempts.

Fix this in Dpc3939 Wireless Residential Voice Gateway Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2015-6361 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