Adaptive Security Appliance SoftwareOperating system · Cisco
CVE-2007-4786
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 · uneditedCisco Adaptive Security Appliance (ASA) running PIX 7.0 before 7.0.7.1, 7.1 before 7.1.2.61, 7.2 before 7.2.2.34, and 8.0 before 8.0.2.11, when AAA is enabled, composes %ASA-5-111008 messages from the "test aaa" command with cleartext passwords and sends them over the network to a remote syslog server or places them in a local logging buffer, which allows context-dependent attackers to obtain sensitive information.
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 confidenceWhen AAA (authentication, authorization, and accounting) is enabled on Cisco ASA and PIX devices running vulnerable software versions (7.0 before 7.0.7.1, 7.1 before 7.1.2.61, 7.2 before 7.2.2.34, and 8.0 before 8.0.2.11), the 'test aaa' command generates syslog messages (%ASA-5-111008) containing cleartext passwords. These credentials are transmitted to remote syslog servers or stored in local logging buffers, allowing context-dependent attackers to intercept them.
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.0, < 7.0.7.1>= 7.1, < 7.1.2.61>= 7.2, < 7.2.2.34>= 8.0, < 8.0.2.11CVSS 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
- Adjacent
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
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 the Cisco ASA software versionUse the 'show version' command on the ASA device CLI to display the installed software versionAffected if The version falls within the affected ranges: 7.0.x before 7.0.7.1, 7.1.x before 7.1.2.61, 7.2.x before 7.2.2.34, or 8.0.x before 8.0.2.11
-
Verify AAA is enabledUse the 'show aaa-server' command to list configured AAA server groups, or check the running configuration for 'aaa-server' statementsAffected if AAA server groups are configured and AAA authentication/authorization is enabled
-
Examine remote syslog server configurationUse the 'show logging' command to display the current logging configuration, including configured syslog serversAffected if Remote syslog servers are configured (logging host interface command)
-
Search local logging buffers for exposed credentialsUse the 'show log' command to view buffered log messages, and search for the pattern '%ASA-5-111008' which indicates the test aaa command outputAffected if Log buffer contains %ASA-5-111008 messages with visible plaintext passwords
-
Review syslog server logs for credential exposureIf you have access to remote syslog servers, search historical logs for %ASA-5-111008 messages containing credentialsAffected if Remote syslog servers contain historical logs with plaintext passwords from test aaa commands
You are affected if your ASA runs a vulnerable software version (7.0-7.0.7, 7.1-7.1.2.60, 7.2-7.2.2.33, or 8.0-8.0.2.10), AAA is enabled, and either local log buffers or remote syslog servers contain %ASA-5-111008 messages with cleartext passwords from the test aaa command.
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.0.7.17.1.2.617.2.2.34
Apply the vendor patches by upgrading to the fixed software versions (7.0.7.1, 7.1.2.61, 7.2.2.34, or 8.0.2.11 or later). Additionally, review syslog configurations and logging buffers to ensure no sensitive credentials were previously exposed.
Fix this in Adaptive Security Appliance Software
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-4786 — 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-4786 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