CVE-2017-6910: The HTTP and WebSocket engine components in the server in Kaazing Gateway before 4.5.3 hotfix-1, Gateway - JMS

Q: How do I fix CVE-2017-6910?

kaazing gateway: upgrade to 4.4.2, 4.5.3; kaazing websocket gateway: upgrade to 5.6.0. Exact commands for each OS are on this page.

Q: Is CVE-2017-6910 being exploited?

CVE-2017-6910 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2017-6910 affect?

CVE-2017-6910 affects kaazing gateway, kaazing websocket gateway. Severity is high (CVSS 7.5). 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

Q: How urgent is CVE-2017-6910?

Priority 51/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 7.5REMOTEUPGRADEUPGRADE

CVE-2017-6910 is a high-severity flaw (CVSS 7.5) affecting kaazing gateway, kaazing websocket gateway. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 handl

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.9% (top 20%)
CISA exploited list	No
Weakness	CWE-200
Published	2018-04-12
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: kaazing · tenefit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-04-12 15:29 UTCPublished CVE record published
2026-06-17 01:23 UTCUpdated Record last modified

kaazing kaazing gateway UPGRADE

Affected: < 4.5.3 · 4.5.3 · 4.5.3 hotfix1 · >= 4.4.0 and < 4.4.2 · >= 4.5.0 and < 4.5.3 · 4.0.5 · 4.0.6 · 4.0.6 hotfix2

Fixed in: 4.4.2, 4.5.3

Safe to downgrade to: a release before 4.0.5

1. Check installed version

apt-cache policy kaazing-gateway || rpm -q kaazing-gateway || kaazing-gateway --version

2. UPGRADE to 4.4.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade kaazing-gateway

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade kaazing-gateway

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 4.0.5 (Debian / Ubuntu)

apt-cache madison kaazing-gateway sudo apt install kaazing-gateway=<VERSION_BEFORE_4.0.5> sudo apt-mark hold kaazing-gateway

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list kaazing-gateway sudo dnf downgrade kaazing-gateway-<VERSION_BEFORE_4.0.5> sudo dnf versionlock add kaazing-gateway

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

tenefit kaazing websocket gateway UPGRADE

Affected: < 5.6.0

Fixed in: 5.6.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy kaazing-websocket-gateway || rpm -q kaazing-websocket-gateway || kaazing-websocket-gateway --version

2. UPGRADE to 5.6.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade kaazing-websocket-gateway

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade kaazing-websocket-gateway

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-6910?

kaazing gateway: upgrade to 4.4.2, 4.5.3; kaazing websocket gateway: upgrade to 5.6.0. Exact commands for each OS are on this page.

Is CVE-2017-6910 being exploited?

CVE-2017-6910 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-6910 affect?

CVE-2017-6910 affects kaazing gateway, kaazing websocket gateway. Severity is high (CVSS 7.5). 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

How urgent is CVE-2017-6910?

Priority 51/100. High severity; Remotely exploitable, no login, no user action

References

← Back to latest CVEs