CVE-2015-1832: Apache Derby XML External Entity Reference Vulnerability
Summary
CVE-2015-1832: Improper Restriction of XML External Entity Reference in Apace Derby. Affects org.apache.derby:derby versions < 10.12.1.1. Fixed in 10.12.1.1. How to fix ↓
Also tracked for
- derby · Debian:11
The same CVE-2015-1832 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Apache Derby is an open-source relational database management system implemented entirely in Java. It provides a small footprint, yet fully functional, database engine that can be embedded into Java applications or run in a client-server mode. The vulnerability in Apache Derby (before version 10.12.1.1) arises from an improper restriction of XML external entity reference in the SqlXmlUtil code. When a Java Security Manager is not in place, this vulnerability allows context-dependent attackers to read arbitrary files or cause a denial of service by exploiting vectors involving XmlVTI and the XML datatype.
Vulnerability Detail
The XML external entity (XXE) vulnerability in Apache Derby allows attackers to read arbitrary files or cause resource consumption. By exploiting this vulnerability, an attacker can manipulate XML input to include external entities, which can lead to the disclosure of sensitive information or denial of service. This vulnerability is particularly severe when a Java Security Manager is not implemented, as it allows attackers to bypass security restrictions and access files outside the intended scope of the application.
How To Fix
Latest published version: 10.17.1.0 as of 22 Oct 2026
Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
10.12.1.1
This is the first release that contains the fix.
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
If upgrading to the latest version of Apache Derby is not feasible, a workaround is to implement a Java Security Manager. Enabling a Java Security Manager helps restrict the actions that can be performed by the Apache Derby code, including preventing the exploitation of XXE vulnerabilities. Consult the Apache Derby documentation for instructions on how to configure and enable the Java Security Manager in your environment.
Conclusion
The XML external entity reference vulnerability in Apache Derby poses a significant security risk, allowing attackers to read arbitrary files or cause resource consumption. To protect your application, it is crucial to upgrade to Apache Derby version 10.12.1.1 or later. Alternatively, enable a Java Security Manager to restrict the actions that can be performed by Apache Derby code. For further assistance and support in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.apache.derby:derby →
FAQ
Apache Derby is an open-source relational database management system implemented entirely in Java. It provides a small footprint, yet fully functional, database engine that can be embedded into Java applications or run in a client-server mode.
An XML external entity (XXE) vulnerability is a type of security vulnerability that allows attackers to read arbitrary files or cause resource consumption by manipulating XML input to include external entities. In the case of Apache Derby, this vulnerability can be exploited to access sensitive files or cause denial of service.
The consequences of this vulnerability include unauthorized access to sensitive information stored in files, potential data breaches, and denial of service attacks that can impact the availability of the Apache Derby database.
To mitigate this vulnerability, it is recommended to upgrade to Apache Derby version 10.12.1.1 or later. Alternatively, you can enable a Java Security Manager to restrict the actions that can be performed by Apache Derby code.
Yes, if upgrading to the latest version of Apache Derby is not feasible, you can implement a Java Security Manager. Enabling a Java Security Manager helps mitigate the risk of XXE vulnerabilities.
Related vulnerabilities
Recent vulnerabilities recorded for org.apache.derby:derby.
