A blind XPath injection vulnerability was discovered in Apache Software Foundation Apache Ivy, which allows threat actors to exfiltrate data and access sensitive information that is restricted to only the machine that runs Apache Ivy.
This vulnerability exists in the parsing of XML files in versions lesser than 2.5.2 while parsing its own configuration, Maven POMs (Project Object Models), which allows external document downloading and expansion of any entity references.
Threat actors can exploit this Blind XPath injection vulnerability to manipulate or execute the Ivy in different ways or access sensitive information inside the machine. This vulnerability is due to improper restriction of XML External Entity reference.
It is a dependency manager which resolves project dependencies and is a part of the Apache Ant project. It uses an XML file for defining project dependencies to list the necessary resources to build a project.
The CVE ID for this vulnerability has been given as CVE-2022-46751, and the CVSS score is yet to be confirmed.
Apache Ivy 2.5.2 version released
Prior to Apache Ivy version 2.5.2, Apache Ivy has DTD processing by default while parsing Maven POMs and other files.
However, as part of fixing the bug, Apache has released Apache Ivy version 2.5.2, which disables DTD (Document Type Definition) processing for all the files excluding Maven POMs, which allows only a DTD snippet to be included that is used for dealing with existing Maven POMs.
These are not valid XML files but are accepted by Maven POMs. Apache Ivy is a part of the Apache Ant project that specializes in automating software build processes which originated from the Apache Tomcat Project 2000.
Users are recommended to upgrade to the latest version of Apache Ivy 2.5.2 to prevent this vulnerability from getting exploited. As an alternative, Java system properties can be used to restrict the processing of external DTDs.
Keep informed about the latest Cyber Security News by following us on GoogleNews, Linkedin, Twitter, and Facebook.
