First published: Wed Sep 27 2017(Updated: )
Apache Commons Jelly could allow a remote attacker to bypass security restrictions, caused by improper handling of XML External Entity (XXE) entries when parsing to an XML file. By persuading a victim to open a jelly file containing a specially crafted custom doctype entity in a SYSTEM entity that contains a URL, an attacker could exploit this vulnerability to conduct XML External Entity (XXE) attacks.
Credit: security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
Apache Commons Jelly | <1.0.1 | |
IBM Cloud Pak for Business Automation | <=V23.0.1 - V23.0.1-IF001 | |
IBM Cloud Pak for Business Automation | <=V21.0.3 - V21.0.3-IF023 | |
IBM Cloud Pak for Business Automation | <=V22.0.2 - V22.0.2-IF006 and later fixes V22.0.1 - V22.0.1-IF006 and later fixes V21.0.2 - V21.0.2-IF012 and later fixes V21.0.1 - V21.0.1-IF007 and later fixes V20.0.1 - V20.0.3 and later fixes V19.0.1 - V19.0.3 and later fixes V18.0.0 - V18.0.2 and later fixes |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.