GHSA-58qw-p7qm-5rvh Eclipse Jetty XmlParser allows arbitrary DOCTYPE declarations

• Maven org.eclipse.jetty:jetty-xml: >= 10.0.0-alpha0, < 10.0.16 → fixed in 10.0.16 • Maven org.eclipse.jetty:jetty-xml: >= 11.0.0-alpha0, < 11.0.16 → fixed in 11.0.16 • Maven org.eclipse.jetty:jetty-xml: >= 12.0.0.alpha0, < 12.0.0 → fixed in 12.0.0 • Maven org.eclipse.jetty:jetty-xml: < 9.4.52.v20230823 → fixed in 9.4.52.v20230823

From the reporter > `XmlParser` is vulnerable to XML external entity (XXE) vulnerability. > XmlParser is being used when parsing Jetty’s xml configuration files. An attacker might exploit > this vulnerability in order to achieve SSRF or cause a denial of service. > One possible scenario is importing a (remote) malicious WAR into a Jetty’s server, while the > WAR includes a malicious web.xml. Impact There are no circumstances in a normally deployed Jetty server where potentially hostile XML is given to the XmlParser class without the attacker already having arbitrary access to the server. I.e. in order to exploit `XmlParser` the attacker would already have the ability to deploy and execute hostile code. Specifically, Jetty has no protection against malicious web application and potentially hostile web applications should only be run on an isolated virtualisation. Thus this is not considered a vulnerability of the Jetty server itself, as any such usage of the jetty XmlParser is equally vulnerable as a direct usage of the JVM supplied SAX parser. No CVE will be allocated to this advisory. However, any direct usage of the `XmlParser` class by an application may be vulnerable. The impact would greatly depend on how the application uses `XmlParser`, but it could be a denial of service due to large entity expansion, or possibly the revealing local files if the XML results are accessible remotely. Patches Ability to configure the SAXParserFactory to fit the needs of your particular XML parser implementation have been merged as part of PR #10067 Workarounds Don't use Jetty's `XmlParser` to parse data from users.