Wide Area Application ServicesApplication · Cisco
CVE-2012-1348
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 Wide Area Application Services (WAAS) appliances with software 4.4, 5.0, and 5.1 include a one-way hash of a password within output text, which might allow remote attackers to obtain sensitive information via a brute-force attack on the hash string, aka Bug ID CSCty17279.
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 confidenceCisco WAAS appliances versions 4.4, 5.0, and 5.1 expose a one-way password hash in text output, allowing remote attackers to capture the hash and perform offline brute-force attacks to recover the plaintext password.
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
Wide Area Application ServicesApplication
= 4.4= 5.0= 5.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
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/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 Cisco WAAS installationLocate any Cisco WAAS appliances or software installations in your environment. Check for processes named 'waas' or services related to Wide Area Application Services.Affected if Cisco WAAS is not present in your environment, you are not affected.
-
Check WAAS versionRun the command 'show version' or access the WAAS CLI and execute 'show version' to identify the installed Cisco WAAS version.Affected if If the version is 4.4, 5.0, or 5.1, your version is within the affected range.
-
Review system output for password hashesExamine any text-based outputs from the WAAS system, including command outputs, logs, and administrative interfaces. Look for strings resembling password hashes (alphanumeric sequences) in contexts where passwords should not be visible.Affected if If password hashes appear in plain text output, the vulnerability is present.
-
Check log files for hash disclosureReview WAAS log files in /var/log/ or the system logging destination for any entries containing password hash data in readable format.Affected if Log files contain exposed password hashes, indicating the vulnerability is exploitable.
You are affected if Cisco WAAS versions 4.4, 5.0, or 5.1 are running AND password hashes are being exposed in system outputs or logs.
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 WAAS to a patched version beyond 5.1 and change any passwords that may have been exposed, as the hash disclosure enables offline password cracking attacks.
Fix this in Wide Area Application Services
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-1348 — 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-2012-1348 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