How severe is CVE-2017-6910?

CVE-2017-6910 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2017-6910 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (78th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2017-6910?

CVE-2017-6910 primarily affects Kaazing Kaazing Gateway. In total, 13 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2017-6910?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2017-6910 published?

CVE-2017-6910 was published on 2018-04-12 and last updated on 2026-06-17.

CVE-2017-6910

CVE-2017-6910 is a high-severity vulnerability in Kaazing Kaazing Gateway with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-200.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v2: 5.0
EPSS exploit prediction: 2% (78th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-200
Affected product: Kaazing Kaazing Gateway
Published: 2018-04-12
Last modified: 2026-06-17

Description

The 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.

Frequently asked questions

What is CVE-2017-6910?: The 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.
How severe is CVE-2017-6910?: CVE-2017-6910 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2017-6910 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (78th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-6910?: CVE-2017-6910 primarily affects Kaazing Kaazing Gateway. In total, 13 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2017-6910?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2017-6910 published?: CVE-2017-6910 was published on 2018-04-12 and last updated on 2026-06-17.

References

https://support.kaazing.com/hc/en-us/articles/115004752368

Affected products (13)

cpe:2.3:a:kaazing:kaazing_gateway:*:*:*:*:*:*:*:*
cpe:2.3:a:kaazing:kaazing_gateway:4.5.3:*:*:*:*:*:*:*
cpe:2.3:a:kaazing:kaazing_gateway:4.5.3:hotfix1:*:*:*:*:*:*
cpe:2.3:a:kaazing:kaazing_gateway:*:hotfix1:*:*:jms:*:*:*
cpe:2.3:a:kaazing:kaazing_gateway:*:*:*:*:jms:*:*:*
cpe:2.3:a:kaazing:kaazing_gateway:4.0.5:*:*:*:jms:*:*:*
cpe:2.3:a:kaazing:kaazing_gateway:4.0.6:*:*:*:jms:*:*:*
cpe:2.3:a:kaazing:kaazing_gateway:4.0.6:hotfix2:*:*:jms:*:*:*
cpe:2.3:a:kaazing:kaazing_gateway:4.0.7:*:*:*:jms:*:*:*
cpe:2.3:a:kaazing:kaazing_gateway:4.4.2:hotfix1:*:*:jms:*:*:*
cpe:2.3:a:kaazing:kaazing_gateway:4.5.3:hotfix1:*:*:jms:*:*:*
cpe:2.3:a:tenefit:kaazing_websocket_gateway:*:*:*:*:community:*:*:*
cpe:2.3:a:tenefit:kaazing_websocket_gateway:*:*:*:*:enterprise:*:*:*

Other CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) vulnerabilities

CVE-2026-27604 — Critical (CVSS 10.0): FOSSBilling is a free, open-source billing and client management system. Starting in version 0.5.4 and prior to version…
CVE-2026-40965 — Critical (CVSS 10.0): Cloud Foundry UAA versions v76.12.0 through v78.12.0 are vulnerable to a private key exposure. The server contains a…
CVE-2026-42826 — Critical (CVSS 10.0): Exposure of sensitive information to an unauthorized actor in Azure DevOps allows an unauthorized attacker to disclose…
CVE-2025-29270 — Critical (CVSS 10.0): Incorrect access control in the realtime.cgi endpoint of Deep Sea Electronics devices DSE855 v1.1.0 to v1.1.26 allows…
CVE-2025-61481 — Critical (CVSS 10.0): An issue in MikroTik RouterOS v.7.14.2 and SwOS v.2.18 exposes the WebFig management interface over cleartext HTTP by…
CVE-2025-53624 — Critical (CVSS 10.0): The Docusaurus gists plugin adds a page to your Docusaurus instance, displaying all public gists of a GitHub user.…

Browse all CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) vulnerabilities →