Filtered by vendor Hawt Subscriptions
Filtered by product Hawtio Subscriptions
Total 7 CVE
CVE Vendors Products Updated CVSS v3.1
CVE-2023-33544 1 Hawt 1 Hawtio 2023-06-08 5.5 Medium
hawtio 2.17.2 is vulnerable to Path Traversal. it is possible to input malicious zip files, which can result in the high-risk files after decompression being stored in any location, even leading to file overwrite.
CVE-2017-7556 1 Hawt 1 Hawtio 2019-10-09 N/A
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.
CVE-2017-2594 1 Hawt 1 Hawtio 2019-10-09 N/A
hawtio before versions 2.0-beta-1, 2.0-beta-2 2.0-m1, 2.0-m2, 2.0-m3, and 1.5 is vulnerable to a path traversal that leads to a NullPointerException with a full stacktrace. An attacker could use this flaw to gather undisclosed information from within hawtio's root.
CVE-2017-2589 2 Hawt, Redhat 2 Hawtio, Jboss Fuse 2019-10-09 N/A
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.
CVE-2019-9827 1 Hawt 1 Hawtio 2019-07-10 N/A
Hawt Hawtio through 2.5.0 is vulnerable to SSRF, allowing a remote attacker to trigger an HTTP request from an affected server to an arbitrary host via the initial /proxy/ substring of a URI.
CVE-2014-0121 2 Hawt, Redhat 2 Hawtio, Jboss Fuse 2018-01-11 N/A
The admin terminal in Hawt.io does not require authentication, which allows remote attackers to execute arbitrary commands via the k parameter.
CVE-2014-0120 2 Hawt, Redhat 2 Hawtio, Jboss Fuse 2018-01-11 N/A
Cross-site request forgery (CSRF) vulnerability in the admin terminal in Hawt.io allows remote attackers to hijack the authentication of arbitrary users for requests that run commands on the Karaf server, as demonstrated by running "shutdown -f."