Adaptive Security Appliance SoftwareOperating system · Cisco
CVE-2008-0028
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 · uneditedUnspecified vulnerability in Cisco PIX 500 Series Security Appliance and 5500 Series Adaptive Security Appliance (ASA) before 7.2(3)6 and 8.0(3), when the Time-to-Live (TTL) decrement feature is enabled, allows remote attackers to cause a denial of service (device reload) via a crafted IP packet.
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 confidenceDenial of service vulnerability in Cisco PIX 500 Series and ASA 5500 Series security appliances allows remote attackers to cause device reload via crafted IP packets when the Time-to-Live (TTL) decrement feature is enabled. The vulnerability exists in IP packet processing and affects versions prior to 7.2(3)6 and 8.0(3).
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
Adaptive Security Appliance SoftwareOperating system
< 7.2\(3\)6= 8.0\(3\)
Pix Firewall SoftwareOperating system
< 7.2\(3\)6= 8.0\(3\)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 checksWork through these to decide whether this CVE applies to you.
-
Identify device modelLog into the device and run 'show version' or 'show hardware' to confirm the device is a Cisco PIX 500 Series or ASA 5500 Series security appliance.Affected if Device is not a Cisco PIX or ASA model, then not affected by this CVE.
-
Check installed software versionRun 'show version' and locate the 'Cisco PIX Software' or 'Cisco Adaptive Security Appliance Software' version string. Compare it against the affected versions: any version less than 7.2(3)6, or exactly version 8.0(3).Affected if Version is less than 7.2(3)6 or equals exactly 8.0(3)
-
Verify TTL decrement feature statusRun 'show running-config' or 'show configuration' and search for the 'ttl-dec' or 'time-to-live decrement' configuration command under the relevant interface or global IP configuration. Alternatively, check the configuration for any 'ttl' related settings.Affected if The TTL decrement feature is explicitly enabled in the running configuration (the device must have this feature turned on for the vulnerability to be exploitable).
The environment is affected only if the device is a Cisco PIX or ASA running software version less than 7.2(3)6 or exactly 8.0(3) AND the TTL decrement feature is enabled in the configuration.
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 data7.2
Upgrade to Cisco PIX/ASA version 7.2(3)6, 8.0(3), or later. Alternatively, disable the TTL decrement feature if immediate upgrade is not feasible.
Fix this in Adaptive Security Appliance Software
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-0028 — 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-2008-0028 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