dbcve.org
Ace 4710Hardware / appliance · Cisco

CVE-2010-2822

HIGH · 7.8 CVSS v2.0 Published 2010-08-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
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
Unspecified vulnerability in the RTSP inspection feature on the Cisco Application Control Engine (ACE) Module with software before A2(3.2) for Catalyst 6500 series switches and 7600 series routers, and the Cisco Application Control Engine (ACE) 4710 appliance with software before A3(2.6), allows remote attackers to cause a denial of service (device reload) via crafted RTSP packets over TCP, aka Bug IDs CSCta85227 and CSCtg14858.

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

A denial of service vulnerability in the RTSP (Real Time Streaming Protocol) inspection feature of Cisco Application Control Engine (ACE) modules and appliances allows remote attackers to cause device reload by sending specially crafted RTSP packets over TCP. The vulnerability affects ACE modules for Catalyst 6500/7600 series and ACE 4710 appliances running software versions prior to A2(3.2) and A3(2.6) respectively.

MitigationUpgrade Cisco ACE software to version A2(3.2) or later for Catalyst 6500/7600 modules, or A3(2.6) or later for ACE 4710 appliances. Schedule a maintenance window to apply the software update and verify RTSP inspection functionality after upgrade.

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
Ace 4710Hardware / appliance
Affected:all versions= a1\(2.0\)= a1\(8.0\)= a3\(2.0\)= a3\(2.5\)
Ace ModuleHardware / appliance
Affected:<= a2\(3.1.0\)

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

AV:N/AC:L/Au:N/C:N/I:N/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 ACE product type
    Determine if the device is a Cisco ACE 4710 appliance or an ACE module installed in a Catalyst 6500/7600 series switch. Use 'show version' or check the physical device labeling.
    Affected if The device is a Cisco ACE 4710 appliance or ACE module for Catalyst 6500/7600 series.
  2. Check the installed software version
    Run 'show version' on the ACE CLI to retrieve the running software version. Compare the displayed version to the affected ranges: ACE 4710 versions a1(2.0), a1(8.0), a3(2.0), a3(2.5) are vulnerable; ACE Module versions a2(3.1.0) and earlier are vulnerable.
    Affected if The version matches one of the affected versions or falls within the vulnerable ranges.
  3. Verify RTSP inspection is enabled
    Examine the ACE configuration using 'show running-config' or 'show policy-map' to determine if RTSP inspection is configured. Look for 'inspect rtsp' or RTSP-related policy-map configurations.
    Affected if RTSP inspection is enabled and applied to traffic.
  4. Confirm RTSP traffic is allowed to the ACE
    Check access lists or traffic policies that permit RTSP traffic (typically TCP port 554 and other RTSP ports) reaching the ACE device. Review the interface configuration and service policy bindings.
    Affected if RTSP traffic can reach the ACE device and is matched by the RTSP inspection policy.

The environment is affected if the device is a Cisco ACE 4710 or ACE Module running a vulnerable software version with RTSP inspection enabled and accessible to RTSP traffic.

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

Upgrade Cisco ACE software to version A2(3.2) or later for Catalyst 6500/7600 modules, or A3(2.6) or later for ACE 4710 appliances. Schedule a maintenance window to apply the software update and verify RTSP inspection functionality after upgrade.

Fix this in Ace 4710 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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