Skip to content

Product

Eclipse Foundation Eclipse GlassFish vulnerabilities

11 published CVES affecting Eclipse Foundation Eclipse GlassFish, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
11
Critical
4
High
1
Medium
6
Low
0
Unscored
0
CISA KEV
0

Latest Eclipse Foundation Eclipse GlassFish CVEs

Newest publication first

  1. CriticalCVSS 9.6 EPSS 0.43%

    In Eclipse GlassFish versions 8.0.x before 8.0.4, CSRF + SSRF in DownloadServlet ContentSources leaks the admin gfresttoken to attacker-controlled host if the victim is authenticated into the Admin Console -> full unauthenticated takeover of Eclipse GlassFish domain until the tok...

  2. MediumCVSS 6.3 EPSS 0.30%

    Eclipse Grizzly in versions before 5.0.2, cannot properly parse the trailer section in malformed trailer header's line, which can be leveraged to perform HTTP request smuggling. Grizzly 5.0.1 supports system properties that enable the behavior that fixes the vulnerability - set o...

  3. CriticalCVSS 9.1 EPSS 0.84%

    An authenticated Remote Code Execution (RCE) vulnerability was identified in GlassFish's Administration Console. A user with access to the panel can send crafted requests that allow the execution of arbitrary operating system commands with the privileges of the application servic...

  4. CriticalCVSS 9.6 EPSS 0.65%

    A critical Remote Code Execution (RCE) vulnerability was identified in the server-side template rendering mechanism used by the Glassfish gadget handler. The application processes .xml files and evaluates user-supplied values within a context where Expression Language (EL) “expre...

  5. CriticalCVSS 9.8 EPSS 0.70%

    An unsafe parsing of OpenMQ's configuration in OpenMQ versions <6.5.2 and <6.9.0, allows a remote attacker to read arbitrary files from a MQ Broker's server. A full exploitation could read unauthorized files of the OpenMQ’s host OS. In some scenarios RCE could be achieved. This i...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.