Telepresence System SoftwareApplication · Cisco
CVE-2012-0331
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 · uneditedCisco TelePresence Video Communication Server with software before X7.0.1 allows remote attackers to cause a denial of service (device crash) via a crafted SIP packet, as demonstrated by a SIP INVITE message from a Tandberg device, aka Bug ID CSCtq73319.
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 confidenceCisco TelePresence Video Communication Server (VCS) before version X7.0.1 contains a denial of service vulnerability where remote attackers can send a specially crafted SIP INVITE message (as demonstrated from Tandberg devices) that causes the device to crash due to improper handling of the SIP packet.
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 System SoftwareApplication
<= x7.0= x5.2= x6.0= x6.1
Telepresence Video Communication ServerHardware / appliance
all versionsCVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/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 checksWork through these to decide whether this CVE applies to you.
-
Determine the installed VCS versionAccess the VCS administrative interface or run 'xCommand SystemUnitSoftwareVersion' via the API to retrieve the current software versionAffected if The installed version is before X7.0.1 (for example, x5.2, x6.0, x6.1, or x7.0)
-
Confirm SIP service is enabledCheck the VCS configuration under 'SIP' settings or run 'xStatus SIP' to verify if SIP protocol handling is activeAffected if SIP is enabled and the device is processing SIP traffic
-
Verify SIP listening interfacesReview the SIP configuration to determine which network interfaces (LAN1, LAN2, or both) are listening for SIP trafficAffected if The VCS is accepting SIP connections on any interface
-
Assess network exposure to untrusted sourcesCheck firewall or access list rules to determine if the SIP ports (typically 5060/5061) are exposed to external or untrusted networksAffected if The SIP service is reachable from untrusted network segments without filtering
The environment is affected if the VCS version is before X7.0.1 and SIP is enabled and accessible to remote attackers sending malicious INVITE messages.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade Cisco TelePresence VCS to version X7.0.1 or later. If immediate patching is not feasible, implement SIP traffic filtering at network boundaries or place the VCS behind a session border controller to limit exposure to untrusted SIP sources.
Fix this in Telepresence System Software
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0331 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-0331 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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