dbcve.org
Unified Videoconferencing System 5110 FirmwareApplication · Cisco

CVE-2010-3038

HIGH · 10.0 CVSS v2.0 Published 2010-11-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 Unified Videoconferencing (UVC) System 5110 and 5115, when the Linux operating system is used, has a default password for the (1) root, (2) cs, and (3) develop accounts, which makes it easier for remote attackers to obtain access via the (a) FTP or (b) SSH daemon, aka Bug ID CSCti54008.

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 Cisco Unified Videoconferencing (UVC) Systems 5110 and 5115 running Linux contain hardcoded default passwords for root, cs, and develop accounts. Attackers can remotely authenticate via FTP or SSH using these credentials to gain unauthorized system access with the privileges of those accounts.

MitigationImmediately change all default passwords to strong, unique credentials. Disable unused FTP and SSH access, or restrict SSH to specific management IPs via ACLs. Consider disabling the 'develop' account entirely if not needed.

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
Unified Videoconferencing System 5110 FirmwareApplication
Affected:= 7.0.1.13.3
Unified Videoconferencing System 5115 FirmwareApplication
Affected:= 7.0.1.13.3
Unified Videoconferencing System 5110Hardware / appliance
Affected:all versions
Unified Videoconferencing System 5115Hardware / 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. Identify the Cisco UVC device model
    Access the device admin interface or check the physical device label for the model number (5110 or 5115). The vulnerability affects only these two models.
    Affected if The device is a Cisco Unified Videoconferencing System 5110 or 5115.
  2. Check the firmware version
    Log into the device admin interface or use the command line interface to retrieve the firmware version. The specific affected version is 7.0.1.13.3.
    Affected if The firmware version is 7.0.1.13.3 OR if determining whether all versions are affected (the advisory indicates all versions contain the hardcoded credentials).
  3. Verify if default accounts exist with default passwords
    Attempt to authenticate via SSH or FTP using the accounts root, cs, and develop with their known default passwords. Alternatively, check the device user management interface to see if these accounts are present and active.
    Affected if Any of the root, cs, or develop accounts are present and can be accessed using default credentials.
  4. Check if FTP service is enabled and accessible
    From an external host, attempt to connect to the device FTP port (port 21). If the service responds and accepts authentication, it is exposed.
    Affected if FTP service is enabled and accepts connections from untrusted networks.
  5. Check if SSH service is enabled and accessible
    From an external host, attempt to connect to the device SSH port (port 22). If the service responds and accepts authentication, it is exposed.
    Affected if SSH service is enabled and accepts connections from untrusted networks.

A user is affected if they have a Cisco UVC 5110 or 5115 device with any firmware version where the default accounts root, cs, or develop retain their default passwords and FTP or SSH services are accessible.

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

Immediately change all default passwords to strong, unique credentials. Disable unused FTP and SSH access, or restrict SSH to specific management IPs via ACLs. Consider disabling the 'develop' account entirely if not needed.

Fix this in Unified Videoconferencing System 5110 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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