PixHardware / appliance · Cisco
CVE-2007-2463
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 Adaptive Security Appliance (ASA) and PIX 7.1 before 7.1(2)49 and 7.2 before 7.2(2)17 allows remote attackers to cause a denial of service (device reload) via unknown vectors related to VPN connection termination and password expiry.
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 confidenceThis is a denial of service vulnerability affecting Cisco ASA and PIX firewall devices running versions 7.1 before 7.1(2)49 and 7.2 before 7.2(2)17. The vulnerability is triggered during VPN connection termination when password expiry conditions are encountered, causing the device to reload unexpectedly.
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
PixHardware / appliance
<= 7.2= 7.1
Adaptive Security Appliance SoftwareOperating system
<= 7.2.2= 7.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify device model and software versionRun `show version` on the Cisco ASA or PIX CLI to display the device model and installed software versionAffected if Device is a Cisco ASA or PIX running software version 7.1 before 7.1(2)49 or 7.2 before 7.2(2)17
-
Verify VPN feature is configuredRun `show vpn-sessiondb` or `show run | include vpn` to confirm VPN is enabled on the deviceAffected if VPN is not configured or not active on the device (not affected if no VPN functionality exists)
-
Check for VPN user accounts with password expiryRun `show run | include username` to list local VPN user accounts, then check individual user configurations with `show run username <username>` for `password-expire` directiveAffected if Local VPN user accounts exist with password expiry rules configured (the vulnerability triggers during VPN termination when password expiry conditions are encountered)
-
Confirm AAA VPN authentication configurationRun `show run | include aaa` to check if AAA authentication is configured for VPN, and examine any authentication server group settings with `show run | include tunnel-group`Affected if AAA authentication is configured for VPN connections (the vulnerability can be triggered when password expiry conditions are encountered during VPN session termination)
A user is affected if their Cisco ASA or PIX device runs version 7.1 before 7.1(2)49 or version 7.2 before 7.2(2)17, has VPN configured, and has VPN users with password expiry settings or AAA authentication that encounters password expiry during session termination.
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 ASA/PIX devices to version 7.1(2)49 or later for the 7.1 branch, or 7.2(2)17 or later for the 7.2 branch. Schedule a maintenance window and ensure configurations are backed up before applying the update.
Fix this in Pix
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-2463 — 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-2007-2463 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