dbcve.org
Ace ModuleHardware / appliance · Cisco

CVE-2010-2825

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 SIP inspection feature on the Cisco Application Control Engine (ACE) Module with software A2(1.x) before A2(1.6), A2(2.x) before A2(2.3), and A2(3.x) before A2(3.1) for Catalyst 6500 series switches and 7600 series routers, and the Cisco Application Control Engine (ACE) 4710 appliance with software before A3(2.4), allows remote attackers to cause a denial of service (device reload) via crafted SIP packets over (1) TCP or (2) UDP, aka Bug IDs CSCta65603 and CSCta71569.

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 exists in the SIP inspection feature of Cisco Application Control Engine (ACE) Module for Catalyst 6500/7600 series and ACE 4710 appliances. Remote attackers can trigger device reload by sending specially crafted SIP packets over TCP or UDP.

MitigationUpgrade to fixed software versions (A2(1.6), A2(2.3), A2(3.1), or A3(2.4)+) per Cisco advisory. If immediate patching is not feasible, consider disabling SIP inspection or implementing packet filtering at upstream devices until upgrade can be scheduled.

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 ModuleHardware / appliance
Affected:<= a2\(3.1.0\)<= a2\(3.1.6\)<= a2\(3.2.2.0\)
Ace 4710Hardware / appliance
Affected:all versions= a1\(2.0\)= a1\(2.3\)= a1\(8.0\)= a3\(1.0\)= a3\(2.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 device type
    Run 'show version' or 'show module' command to confirm the device is a Cisco ACE Module (for Catalyst 6500/7600) or ACE 4710 Appliance
    Affected if The device is a Cisco ACE Module or ACE 4710 Appliance
  2. Check the ACE software version
    Run 'show version' and look for the software version string (for example, A2(3.1), A2(3.2), A3(1), etc.)
    Affected if The version falls within <= a2(3.1.0), <= a2(3.1.6), <= a2(3.2.2.0) for ACE Module, or matches any version for ACE 4710 including a1(2.0), a1(2.3), a1(8.0), a3(1.0), a3(2.0)
  3. Verify if SIP inspection is enabled
    Run 'show service-policy' and 'show ip inspect' or check the active service policies for SIP inspection configuration using 'show running-config | include sip'
    Affected if SIP inspection is configured and active on any interface or service policy
  4. Check for recent reloads or SIP-related crash information
    Run 'show log' or 'show tech-support' and look for messages indicating unexpected reloads or SIP inspection failures
    Affected if Device has reloaded unexpectedly or logs show SIP inspection crash entries correlating with the timing of the issue

A user is affected if they run a vulnerable Cisco ACE version with SIP inspection enabled and have received specially crafted SIP packets over TCP or UDP that may have caused or could cause device reload.

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 to fixed software versions (A2(1.6), A2(2.3), A2(3.1), or A3(2.4)+) per Cisco advisory. If immediate patching is not feasible, consider disabling SIP inspection or implementing packet filtering at upstream devices until upgrade can be scheduled.

Fix this in Ace Module Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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