dbcve.org
Modular Encoding Platform D9036 SoftwareOperating system · Cisco

CVE-2015-6412

CRITICAL · 9.8 CVSS v3.0 Published 2016-01-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Cisco Modular Encoding Platform D9036 Software before 02.04.70 has hardcoded (1) root and (2) guest passwords, which makes it easier for remote attackers to obtain access via an SSH session, aka Bug ID CSCut88070.

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

Cisco Modular Encoding Platform D9036 Software versions prior to 02.04.70 contain hardcoded root and guest passwords embedded in the firmware. Attackers with network access to the device can use these credentials to authenticate via SSH and gain unauthorized administrative access to the encoding platform.

MitigationUpgrade Cisco D9036 Software to version 02.04.70 or later to obtain the patched firmware with removed hardcoded credentials. If immediate patching is not feasible, restrict SSH access via firewall rules or disable external SSH access and use out-of-band management.

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
Modular Encoding Platform D9036 SoftwareOperating system
Affected:= 02.00.80= 02.01.50= 02.02.30= 02.03.30

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
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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 checks

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

  1. Confirm device model
    Log into the device or check hardware inventory to verify the device is a Cisco Modular Encoding Platform D9036
    Affected if The device is a Cisco D9036 encoding platform
  2. Check software version
    Access the device management interface or use CLI command to display the software version (typically via 'show version' or through the web management console)
    Affected if The installed version is 02.00.80, 02.01.50, 02.02.30, or 02.03.30
  3. Verify SSH service status
    Check if SSH service is enabled on the device via management interface or CLI command (such as 'show ip ssh' or checking service configuration)
    Affected if SSH is enabled and accessible from the network
  4. Check SSH access exposure
    Review network access controls, firewall rules, or interface configurations to determine if TCP port 22 is reachable from untrusted networks
    Affected if SSH port 22 is exposed to external or untrusted networks

The environment is affected if it is a D9036 device running software version 02.00.80, 02.01.50, 02.02.30, or 02.03.30 with SSH service enabled and accessible from the network.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Cisco D9036 Software to version 02.04.70 or later to obtain the patched firmware with removed hardcoded credentials. If immediate patching is not feasible, restrict SSH access via firewall rules or disable external SSH access and use out-of-band management.

Recommended fix High confidence

Cisco D9036 Software version 02.04.70 or later

  1. Identify the current Cisco D9036 Software version by accessing the device CLI or management interface
  2. Schedule a maintenance window as the upgrade may require system downtime
  3. Download Cisco D9036 Software version 02.04.70 or later from Cisco's official download portal (tools.cisco.com)
  4. Review Cisco upgrade documentation for the D9036 platform before proceeding
  5. Upload the new software image to the device following Cisco's standard upgrade procedures
  6. Perform the upgrade to version 02.04.70 or later
  7. After upgrade, verify the new version is running: show version
  8. Change any default credentials immediately after upgrade and ensure strong, unique passwords are configured
Caveat Standard upgrade risks apply - review release notes for D9036 02.04.70 for any configuration or feature changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Modular Encoding Platform D9036 Software Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-6412 — 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-6412 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