CONTENTUM.COMA specialist. A plan. A result.

Vulnerabilities · 2017 · Apache

CVE-2017-12621
Apache Commons Jelly vulnerability

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.

High priority: this vulnerability is rated critical and can be attacked over the network without a login.

Affected products

Commons Jelly. The exact versions are in the references.

What to do now

  • Check your exposureFind out whether Apache Commons Jelly runs anywhere in your environment, including systems of suppliers.
  • UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
  • Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.

References

More vulnerabilities in Apache products

Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.