dbcve.org
Telepresence Recording ServerApplication · Cisco

CVE-2012-3076

HIGH · 9.0 CVSS v2.0 Published 2012-07-12
Fix available
A fix is available. Upgrade to after 1.7.3 or later.
See remediation →
96/100
Remediation priority · Urgent
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 TelePresence Recording Server before 1.8.0 allows remote authenticated users to execute arbitrary commands via unspecified vectors, aka Bug ID CSCth85804.

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 TelePresence Recording Server versions prior to 1.8.0 contains a command injection vulnerability allowing authenticated remote users to execute arbitrary operating system commands through unspecified vectors in the web interface.

MitigationUpgrade Cisco TelePresence Recording Server to version 1.8.0 or later. If immediate upgrade is not feasible, implement network segmentation to restrict administrative interface access to trusted IP addresses only 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
Telepresence Recording ServerApplication
Affected:<= 1.7.3\(3\)= 1.6.1\(2\)= 1.6.2\(31\)= 1.6.3\(4\)= 1.7.0\(190\)= 1.7.1\(22\)= 1.7.2.1

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

AV:N/AC:L/Au:S/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 Cisco TelePresence Recording Server installation
    Check for the product by accessing the web interface and looking for Cisco TelePresence branding, or check system documentation/inventory for this software. Look for HTTP responses containing 'Cisco TelePresence Recording Server' or similar branding.
    Affected if The software is installed and running
  2. Determine installed version number
    Access the administrative web interface and navigate to the About, System Info, or Help page to find the version number. Alternatively, check the HTTP server banner or any version information displayed in the login page or admin console.
    Affected if The version number matches any of these affected versions: 1.6.1(2), 1.6.2(31), 1.6.3(4), 1.7.0(190), 1.7.1(22), 1.7.2.1, or any version 1.7.3(3) or earlier
  3. Verify administrative web interface is accessible
    Attempt to access the web interface URL (typically on ports 80 or 443) and confirm the administrative login page or console loads. Check if the interface is reachable from network locations.
    Affected if The administrative web interface is accessible from your network
  4. Confirm authentication is required for the web interface
    Verify that the web interface requires credentials to access administrative functions. Attempt to access protected pages without logging in to see if authentication is enforced.
    Affected if The interface is accessible without any authentication or uses default/weak credentials that may have been compromised

You are affected if Cisco TelePresence Recording Server is installed with a version at or below 1.7.3(3), the administrative web interface is network-accessible, and an attacker with valid credentials could inject commands through web parameters.

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.7.3
Interim mitigation

Upgrade Cisco TelePresence Recording Server to version 1.8.0 or later. If immediate upgrade is not feasible, implement network segmentation to restrict administrative interface access to trusted IP addresses only and monitor for unauthorized access attempts.

Recommended fix High confidence

1.8.0 or later

  1. Confirm current installed version of Cisco TelePresence Recording Server
  2. Obtain version 1.8.0 or later from Cisco's official support portal (tools.cisco.com)
  3. Follow Cisco's standard upgrade procedure for TelePresence Recording Server
  4. Verify the upgrade was successful and the version is 1.8.0 or later
  5. Validate that the administrative web interface is functioning correctly

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

Fix this in Telepresence Recording Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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