CVE-2017-6910
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 · uneditedThe HTTP and WebSocket engine components in the server in Kaazing Gateway before 4.5.3 hotfix-1, Gateway - JMS Edition before 4.0.5 hotfix-15, 4.0.6 before hotfix-4, 4.0.7, 4.0.9 before hotfix-19, 4.4.x before 4.4.2 hotfix-1, 4.5.x before 4.5.3 hotfix-1, and Gateway Community and Enterprise Editions before 5.6.0 allow remote attackers to bypass intended access restrictions and obtain sensitive information via vectors related to HTTP request handling.
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 confidenceThe HTTP and WebSocket engine components in Kaazing Gateway contain an access control bypass vulnerability in HTTP request handling. Remote attackers can circumvent intended security restrictions to gain unauthorized access to sensitive information through specially crafted HTTP requests.
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< 4.5.3= 4.5.3>= 4.4.0, < 4.4.2>= 4.5.0, < 4.5.3= 4.0.5= 4.0.6= 4.0.7= 4.4.2< 5.6.0CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/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 Kaazing Gateway versionLocate the gateway installation and check the version. Common locations: gateway.xml <gateway> version attribute, pom.xml in the installation directory, or run the gateway binary with --version flag if available. Also check any build or deployment manifests.Affected if Installed version matches: 4.0.5, 4.0.6, 4.0.7, any 4.4.x before 4.4.2, any 4.5.x before 4.5.3, any 4.5.3, or any Tenefit version below 5.6.0
-
Confirm HTTP service is enabledExamine the gateway.xml configuration file for a <service> element with type属性 set to 'http' or 'proxy' pointing to an HTTP destination. The vulnerability exists in the HTTP request handling engine.Affected if An HTTP or WebSocket service is configured and active in the gateway configuration
-
Check for access control rulesReview gateway.xml for <security> elements, particularly <realm> definitions and <constraint> mappings that define which paths require authentication. Look for any URI mappings under <mime-mapping> or <service> that may lack explicit authorization constraints.Affected if HTTP services are exposed without proper constraint definitions, or access control rules rely solely on the vulnerable HTTP handling logic
-
Verify exposed HTTP endpointsIdentify all publicly accessible HTTP URIs in the configuration by reviewing <service> elements with type='http' and their <accept> or <location> attributes. Check if any sensitive paths (such as /admin, /api, /internal) are exposed without explicit IP or authentication constraints.Affected if Sensitive HTTP endpoints are accessible without additional authentication layers beyond the gateway's built-in security
You are affected if you run any Kaazing Gateway version 4.0.5 through 4.5.3, or any Tenefit Kaazing Websocket Gateway below 5.6.0, and have HTTP services enabled in your configuration.
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 data4.4.24.5.35.6.0
Apply the vendor-supplied hotfixes for the specific version in use (hotfix-1 for 4.5.3, hotfix-15 for 4.0.5, hotfix-4 for 4.0.6, hotfix-19 for 4.0.9, hotfix-1 for 4.4.2, or upgrade to 5.6.0+ for Community/Enterprise editions).
- Consultation2.0 h
- Implementation4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6910 — 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-2017-6910 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