First published: Fri Mar 13 2020(Updated: )
A flaw was found in the Apache Commons Configuration, where it uses a third-party library to process YAML files, which by default, allows the instantiation of classes if the YAML includes special statements. Apache Commons Configuration versions 2.2, 2.3, 2.4, 2.5, 2.6 did not change the default settings of this library. If a YAML file was loaded from an untrusted source, it could load and execute code out of the control of the host application.
Credit: security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/commons-configuration | <2.7 | 2.7 |
Apache Commons Configuration | =2.2 | |
Apache Commons Configuration | =2.3 | |
Apache Commons Configuration | =2.4 | |
Apache Commons Configuration | =2.5 | |
Apache Commons Configuration | =2.6 | |
Oracle Database | =11.2.0.4 | |
Oracle Database | =12.1.0.2 | |
Oracle Database | =12.2.0.1 | |
Oracle Database | =18c | |
Oracle Database | =19c | |
Oracle Healthcare Foundation | =7.1.1 | |
Oracle Healthcare Foundation | =7.2.0 | |
Oracle Healthcare Foundation | =7.2.1 | |
Oracle Healthcare Foundation | =7.3.0 |
There is currently no mitigation available for this vulnerability.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Appears in the following advisories)
The vulnerability ID for this flaw in Apache Commons Configuration is CVE-2020-1953.
CVE-2020-1953 has a severity level of critical (10).
Apache Commons Configuration versions 2.2, 2.3, 2.4, 2.5, 2.6 are affected by CVE-2020-1953.
To fix the vulnerability CVE-2020-1953, upgrade Apache Commons Configuration to version 2.7.
You can find more information about CVE-2020-1953 in the references section of the vulnerability description.