Eclipse GlassFish 存在通过特定端点进行服务器端请求伪造 (Server Side Request Forgery) 攻击的漏洞

攻击者利用此 SSRF 漏洞可以绕过访问控制，访问 GlassFish 服务器内部的网络资源。这可能包括访问数据库、内部 API 或其他敏感服务。攻击者还可以利用此漏洞读取本地文件，或者将恶意请求发送到其他内部系统，从而造成进一步的损害。虽然该漏洞的直接影响可能有限，但它可能被用作攻击链中的一个环节，用于横向移动或进一步渗透。

Organizations running GlassFish version 6.2.5 or earlier, particularly those with sensitive data stored within the GlassFish environment or exposed through internal services, are at risk. Shared hosting environments utilizing GlassFish are also vulnerable, as they may lack the ability to independently patch the underlying server software.

• java / server: Monitor GlassFish server logs for unusual outbound requests, particularly those targeting internal IP addresses or sensitive endpoints. Use network monitoring tools to detect suspicious traffic originating from the GlassFish server.

journalctl -u glassfish | grep -i "request to"

• generic web: Use a web application firewall (WAF) to filter outbound requests and block those that appear malicious. Configure the WAF to inspect HTTP headers and request bodies for suspicious patterns. • generic web: Check access logs for requests to unusual or unexpected internal endpoints. • generic web: Examine response headers for signs of SSRF exploitation, such as redirects to internal resources.

1. 2025-07-16Disclosure

   disclosure

1. 已保留2024-10-01
2. 发布日期2025-07-16
3. 修改日期2025-07-18
4. EPSS 更新日期2026-04-02

最有效的缓解措施是升级到 GlassFish 6.2.6 或更高版本，该版本修复了此漏洞。如果无法立即升级，可以考虑以下临时缓解措施：限制 GlassFish 控制台的访问权限，只允许授权用户访问。配置防火墙或代理服务器，阻止对敏感内部资源的未经授权的访问。审查 GlassFish 控制台的配置，确保没有暴露不必要的端点。在升级后，确认漏洞已修复，可以通过尝试发起 SSRF 请求来验证。