dbcve.org
Wide Area Application ServicesApplication · Cisco

CVE-2018-0329

MEDIUM · 5.3 CVSS v3.1 Published 2018-06-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
A vulnerability in the default configuration of the Simple Network Management Protocol (SNMP) feature of Cisco Wide Area Application Services (WAAS) Software could allow an unauthenticated, remote attacker to read data from an affected device via SNMP. The vulnerability is due to a hard-coded, read-only community string in the configuration file for the SNMP daemon. An attacker could exploit this vulnerability by using the static community string in SNMP version 2c queries to an affected device. A successful exploit could allow the attacker to read any data that is accessible via SNMP on the affected device. Note: The static credentials are defined in an internal configuration file and are not visible in the current operation configuration ('running-config') or the startup configuration ('startup-config'). Cisco Bug IDs: CSCvi40137.

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 confidence

Cisco WAAS software contains a hard-coded, read-only SNMP community string embedded in an internal configuration file not visible in running-config or startup-config. An unauthenticated remote attacker can exploit this by sending SNMPv2c queries with the static community string to read any SNMP-accessible data from the affected device.

MitigationApply the Cisco patch for CSCvi40137 which removes the hard-coded community string. Until patched, restrict SNMP access via ACLs to trusted management networks or disable SNMP if not required.

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
Affected:= 6.2\(3\)= 6.4\(1\)

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Cisco WAAS version
    Use the command 'show version' or check the installed package version via CLI. Compare the version number to the affected releases 6.2(3) and 6.4(1).
    Affected if The installed version matches exactly 6.2(3) or 6.4(1)
  2. Confirm SNMP is enabled
    Execute 'show snmp' or 'show snmp community' in WAAS CLI to verify SNMP is active and configured.
    Affected if SNMP is enabled and accessible on the device
  3. Inspect running and startup configuration
    Run 'show running-config' and 'show startup-config' and search for SNMP community strings. Note whether any community strings appear in these outputs.
    Affected if SNMP community strings are visible in standard configuration outputs (the hard-coded string is specifically NOT visible in these outputs)
  4. Check for hard-coded community string in internal configuration
    Access the device file system or internal configuration files outside of standard CLI commands. Look for SNMP community string definitions in hidden or internal configuration files not exposed by show commands.
    Affected if A read-only SNMP community string exists in internal config files that does not appear in running-config or startup-config

User is affected if Cisco WAAS version is exactly 6.2(3) or 6.4(1), SNMP is enabled, and a hard-coded SNMP community string exists in internal configuration files.

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

Apply the Cisco patch for CSCvi40137 which removes the hard-coded community string. Until patched, restrict SNMP access via ACLs to trusted management networks or disable SNMP if not required.

Fix this in Wide Area Application Services Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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