During Jelly (xml) file parsing with Apache Xerces, if a custom doctype entity is declared with a SYSTEM entity with a URL and that entity is used in the body of the Jelly file, during parser instantiation the parser will attempt to connect to said URL. This could lead to XML External Entity (XXE) attacks in Apache Commons Jelly before 1.0.1.
The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Commons_jelly | Apache | * | 1.0.1 (excluding) |
| Jenkins-commons-jelly | Ubuntu | esm-apps/xenial | * |
| Jenkins-commons-jelly | Ubuntu | trusty | * |
| Jenkins-commons-jelly | Ubuntu | upstream | * |
| Jenkins-commons-jelly | Ubuntu | xenial | * |