dbcve.org
Media Processing SoftwareApplication · Cisco

CVE-2011-1623

HIGH · 10.0 CVSS v2.0 Published 2011-06-02
Fix available
A fix is available. Upgrade to after 1.1.3 or later.
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 Media Processing Software before 1.2 on Media Experience Engine (MXE) 5600 devices has a default root password, which makes it easier for context-dependent attackers to obtain access via (1) the local console, (2) an SSH session, or (3) a TELNET session, aka Bug ID CSCto77737.

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 Media Processing Software before version 1.2 on Media Experience Engine (MXE) 5600 devices ships with a default root password that is publicly known. Attackers with network access via SSH, TELNET, or physical access via console can authenticate using these default credentials to gain full root privileges on the device.

MitigationChange the default root password immediately to a strong, unique credential and update to Cisco Media Processing Software version 1.2 or later. Consider disabling TELNET in favor of SSH and restricting physical and network access to management interfaces.

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
Media Processing SoftwareApplication
Affected:<= 1.1.3= 1.0.0= 1.0.1= 1.1.0= 1.1.1
Media Experience Engine 5600Hardware / appliance
Affected:all versions

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
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

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

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

  1. Check Cisco Media Processing Software version
    Access the device management interface or run 'show version' via console/SSH and identify the installed Cisco Media Processing Software version number
    Affected if The installed version is 1.0.0, 1.0.1, 1.1.0, 1.1.1, or any version 1.1.3 or lower (versions prior to 1.2)
  2. Confirm Cisco MXE 5600 model
    Verify the device model via 'show hardware' or physical label inspection to confirm it is a Cisco Media Experience Engine 5600
    Affected if The device is a Cisco MXE 5600 (all versions are affected per vendor advisory)
  3. Verify root password has been changed
    Log into the device as root (via console, SSH, or TELNET) and confirm the password has been changed from the publicly known default credential; if you do not know the original default, contact Cisco TAC for the default credentials and compare
    Affected if The root password remains at the default value (publicly known from CVE-2011-1623 disclosure)
  4. Check for exposed management services
    Review device configuration or run 'show ip interface' to determine if SSH, TELNET, or console access are enabled and accessible over network
    Affected if SSH, TELNET, or console access is enabled and reachable from untrusted networks

You are affected if the device is a Cisco MXE 5600 running any version of Cisco Media Processing Software prior to 1.2 AND the root password has not been changed from the default value.

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
Upgrade available Upgrade to a release after 1.1.3
Interim mitigation

Change the default root password immediately to a strong, unique credential and update to Cisco Media Processing Software version 1.2 or later. Consider disabling TELNET in favor of SSH and restricting physical and network access to management interfaces.

Recommended fix High confidence

Cisco Media Processing Software 1.2 or later

  1. Download Cisco Media Processing Software version 1.2 or later from the Cisco website
  2. Verify the integrity of the downloaded image using Cisco's published checksums
  3. Schedule a maintenance window for the upgrade
  4. Back up current configuration following Cisco best practices
  5. Upgrade the Media Processing Software on the Media Experience Engine (MXE) 5600
  6. After upgrade, change the default root password immediately using the 'passwd' command
  7. Verify SSH and TELNET access works with the new credentials
  8. Confirm the upgrade was successful and the vulnerability is resolved

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

Fix this in Media Processing Software Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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