dbcve.org
Wide Area Application ServicesApplication · Cisco

CVE-2017-12250

MEDIUM · 5.3 CVSS v3.0 Published 2017-09-21
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 HTTP web interface for Cisco Wide Area Application Services (WAAS) could allow an unauthenticated, remote attacker to cause an HTTP Application Optimization (AO) related process to restart, causing a partial denial of service (DoS) condition. The vulnerability is due to lack of input validation of user-supplied input parameters within an HTTP request. An attacker could exploit this vulnerability by sending a crafted HTTP request through the targeted device. An exploit could allow the attacker to cause a DoS condition due to a process unexpectedly restarting. The WAAS could drop traffic during the brief time the process is restarting. Cisco Bug IDs: CSCvc63048.

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 confidence

The vulnerability exists in the HTTP web interface of Cisco WAAS due to insufficient input validation of user-supplied parameters in HTTP requests. An unauthenticated remote attacker can send specially crafted HTTP requests that cause the HTTP Application Optimization (AO) process to restart unexpectedly, resulting in a partial denial of service as traffic is dropped during the restart period.

MitigationApply the relevant Cisco patch or upgrade to a fixed software version per Cisco's advisory for CSCvc63048. Until patches can be applied, consider restricting HTTP web interface access to trusted networks or implementing rate limiting on the management interface.

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\(3a\)

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
None
Integrity
None
Availability
Low

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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 installation
    Locate the Cisco WAAS software on the system or check the running processes/services for 'waas' or 'Wide Area Application Services' components
    Affected if The system is running Cisco Wide Area Application Services software
  2. Check installed WAAS version
    Use the command 'show version' or 'show software version' in the WAAS CLI, or check the installed packages for version 6.2(3a)
    Affected if The installed version is exactly 6.2(3a)
  3. Verify HTTP web interface is accessible
    Attempt to access the WAAS HTTP management interface on ports 80/443, or check the HTTP server configuration via 'show http server' in WAAS CLI
    Affected if The HTTP web interface is enabled and reachable on the network
  4. Confirm HTTP Application Optimization is enabled
    Check the WAAS configuration for AO policy settings using 'show optimization' or 'show traffic-policy' commands in WAAS CLI, or inspect if HTTP AO is listed as active
    Affected if HTTP Application Optimization feature is enabled and processing HTTP traffic

A system is affected if it runs Cisco WAAS version 6.2(3a) with both the HTTP web interface and HTTP Application Optimization feature enabled, allowing unauthenticated attackers to trigger AO process restarts via malformed HTTP requests.

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 relevant Cisco patch or upgrade to a fixed software version per Cisco's advisory for CSCvc63048. Until patches can be applied, consider restricting HTTP web interface access to trusted networks or implementing rate limiting on the management interface.

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
12.0 hours of engineering $2,130
Get help mitigating

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 locally
dbcve dependency scanner

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