Skip to content
Fencer Intel
high 8.8

CVE-2017-7556 json

Cross-Site Request Forgery in hawtio

published 2017-08-17 9 y ago modified 2026-06-17 4 mo ago also GHSA-q4q2-fvwf-6ghv , EUVD-2022-4882

cvss
8.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 52%
public exploits
0
none known

Summary

Hawtio versions up to and including 1.5.3 are vulnerable to CSRF vulnerability allowing remote attackers to trick the user to visit their website containing a malicious script which can be submitted to hawtio server on behalf of the user.

Patch / fix

  • maven io.hawt:project 1.5.4

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-7556 updated cvss 5.3

Hawtio: CSRF flaw via jolokia

  • Red Hat JBoss A-MQ 6 hawtio hawtio Red Hat JBoss Fuse 6 hawtio hawtio
    affected: no fix planned “Out of support scope”
  • Red Hat JBoss Fuse Service Works 6 hawtio hawtio
    affected: no fix planned “Will not fix”
  • Red Hat OpenShift Enterprise 3 hawtio
    not affected: vulnerable code not present

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.68% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P
GitHub 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected packages

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

Affected products

  • Red Hat, Inc. hawtio

Classification

Weakness
  • CWE-352 Cross-Site Request Forgery

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.