Skip to content
Fencer Intel
high 8.7

CVE-2017-2589 json

Insecure cookie sharing in Hawtio

published 2018-07-26 8 y ago modified 2026-06-17 4 mo ago also GHSA-m4j5-hgqq-5jf2 , EUVD-2022-4488

cvss
8.7
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 60%
public exploits
0
none known

Summary

It was discovered that the hawtio servlet 1.4 uses a single HttpClient instance to proxy requests with a persistent cookie store (cookies are stored locally and are not passed between the client and the end URL) which means all clients using that proxy are sharing the same cookies.

Patch / fix

  • maven io.hawt:project 1.5.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-2589 updated cvss 8.7

hawtio: Proxy is sharing cookies among all the clients

  • Red Hat JBoss A-MQ 6 hawtio hawtio Red Hat JBoss Fuse 6 hawtio hawtio
    affected: no fix available
  • Red Hat OpenShift Enterprise 2 hawtio
    under investigation
  • Red Hat JBoss A-MQ 6.3 Red Hat JBoss Fuse 6.3
    fixed: vendor fix RHSA-2017:1832

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.93% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.0 8.7 CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
NVD 3.0 9.0 CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
NVD 2.0 6.0 AV:N/AC:M/Au:S/C:P/I:P/A:P
GitHub 3.0 9.0 CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven io.hawt:project
<1.5.0
1.5.0

Affected products

  • Red Hat hawtio

Classification

Weakness
  • CWE-285 Improper Authorization
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.