Cloud Web SecurityApplication · Cisco
CVE-2015-0689
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 Cloud Web Security before 3.0.1.7 allows remote attackers to bypass intended filtering protection mechanisms by leveraging improper handling of HTTP methods, aka Bug ID CSCut69743.
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 confidenceCisco Cloud Web Security before version 3.0.1.7 contains a vulnerability where the filtering proxy improperly handles certain HTTP methods. Attackers can bypass the intended security filtering by crafting requests using specific HTTP methods that are not properly processed by the security appliance, allowing malicious traffic to pass through unchecked.
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
Cloud Web SecurityApplication
<= 3.0.1.2CVSS 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
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 installed Cisco Cloud Web Security versionAccess the Cisco CWS admin interface or use the command-line interface to retrieve the current software version. This is typically found in the system status or about section of the management console.Affected if The installed version is 3.0.1.2 or earlier (any version <= 3.0.1.2)
-
Verify HTTP method filtering configurationCheck the Cisco CWS proxy policy settings to determine which HTTP methods are permitted for filtering. Look for any custom HTTP method rules or method exceptions configured in the filtering profile.Affected if HTTP method filtering is enabled and specific methods are allowed to bypass standard filtering rules
-
Confirm proxy service is activeVerify that the CWS filtering proxy service is running and actively processing HTTP traffic. Check the proxy service status in the admin dashboard or via CLI status commands.Affected if The filtering proxy is actively processing user traffic
-
Review HTTP traffic logs for anomalous method handlingExamine CWS logs for requests using unusual or non-standard HTTP methods (such as OPTIONS, TRACE, or custom methods) that may have bypassed filtering. Compare log entries against configured filtering policies.Affected if Traffic using certain HTTP methods is passing through without being filtered according to policy
A user is affected if Cisco Cloud Web Security version is 3.0.1.2 or earlier and the filtering proxy is actively processing HTTP traffic with method-based filtering rules in place.
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 Cloud Web Security to version 3.0.1.7 or later to remediate this vulnerability. Verify that HTTP method filtering is functioning correctly after the upgrade.
Fix this in Cloud Web Security
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0689 — 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-2015-0689 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