dbcve.org
iOSOperating system · Cisco

CVE-2007-4293

HIGH · 7.1 CVSS v2.0 Published 2007-08-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/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
Cisco IOS 12.0 through 12.4 allows remote attackers to cause a denial of service (device crash) via (1) "abnormal" MGCP messages, aka CSCsd81407; and (2) a large facsimile packet, aka CSCej20505.

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 · moderate confidence

This is a denial of service vulnerability in Cisco IOS versions 12.0 through 12.4 where malformed MGCP (Media Gateway Control Protocol) messages or large facsimile packets can cause the affected device to crash. The vulnerability exists in two separate but related issues identified by Cisco bug IDs CSCsd81407 and CSCej20505.

MitigationOrganizations should upgrade to a patched Cisco IOS version beyond 12.4, or implement network-level filtering to block abnormal MGCP messages and suspicious fax traffic destined for affected devices if immediate upgrade is not feasible.

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
iOSOperating system
Affected:= 12.0= 12.1= 12.2= 12.3= 12.4

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

AV:N/AC:M/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 IOS version
    Execute 'show version' on the device CLI and locate the version string in the output (e.g., '12.4(15)T1')
    Affected if The version begins with 12.0, 12.1, 12.2, 12.3, or 12.4, indicating the device runs an affected IOS train
  2. Determine if MGCP protocol is enabled
    Execute 'show running-config | include mgcp' or 'show mgcp' to check for MGCP-related configuration lines
    Affected if MGCP is actively configured or enabled in the running configuration, exposing the device to malformed MGCP packet attacks (CSCsd81407)
  3. Check for fax-related features
    Execute 'show running-config | include fax' or review the configuration for H.323 fax relay, fax pass-through, or T.38 fax relay settings
    Affected if Fax relay, fax pass-through, or fax-related features are configured, exposing the device to large facsimile packet attacks (CSCej20505)

The device is affected if it runs any Cisco IOS version 12.0 through 12.4 AND has either MGCP protocol or fax features enabled, as both can trigger the denial of service condition.

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

Organizations should upgrade to a patched Cisco IOS version beyond 12.4, or implement network-level filtering to block abnormal MGCP messages and suspicious fax traffic destined for affected devices if immediate upgrade is not feasible.

Fix this in iOS Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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