You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Radu Cotescu (Jira)" <ji...@apache.org> on 2021/10/05 16:16:00 UTC

[jira] [Resolved] (SLING-10852) Upgrade ESAPI to 2.2.3.0

     [ https://issues.apache.org/jira/browse/SLING-10852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radu Cotescu resolved SLING-10852.
----------------------------------
    Resolution: Fixed

Merged PR#11 in [commit db72cf1|https://github.com/apache/sling-org-apache-sling-xss/commit/db72cf1].

> Upgrade  ESAPI to 2.2.3.0
> -------------------------
>
>                 Key: SLING-10852
>                 URL: https://issues.apache.org/jira/browse/SLING-10852
>             Project: Sling
>          Issue Type: Improvement
>          Components: XSS Protection API
>            Reporter: Arun Kumar Ram
>            Assignee: Radu Cotescu
>            Priority: Major
>             Fix For: XSS Protection API 2.2.16
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The {{esapi}} package is vulnerable to XML External Entity (XXE) attacks. The {{loadPropertiesFromFile()}} method in the {{XmlEsapiPropertyLoader}} class allows external entities to be defined in user-controlled XML input files that can be used to configured the application. A remote attacker with control over the input file used to configure the application may craft a malicious XML file that could lead to Denial of Service (DoS), and in certain circumstances Remote Code Execution (RCE)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)