Description
Apache Commons Configuration uses a third-party library to parse 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. So if a YAML file was loaded from an untrusted source, it could therefore load and execute code out of the control of the host application.
Remediation
References
https://lists.apache.org/thread.html/d0e00f2e147a9e9b13a6829133092f349b2882bf6860397368a52600%40%3Cannounce.tomcat.apache.org%3E
https://lists.apache.org/thread.html/r16a2e949e35780c8974cf66104e812410f3904f752df6b66bf292269%40%3Ccommits.servicecomb.apache.org%3E
https://lists.apache.org/thread.html/rde2186ad6ac0d6ed8d51af7509244adcf1ce0f9a3b7e1d1dd3b64676%40%3Ccommits.camel.apache.org%3E
https://www.oracle.com/security-alerts/cpuoct2020.html
Related Vulnerabilities
CVE-2022-45688 Vulnerability in maven package cn.hutool:hutool-json
CVE-2022-39368 Vulnerability in maven package org.eclipse.californium:scandium
CVE-2022-39230 Vulnerability in npm package fhir-works-on-aws-authz-smart
CVE-2019-10361 Vulnerability in maven package org.jenkins-ci.plugins.m2release:m2release
CVE-2016-10027 Vulnerability in maven package org.igniterealtime.smack:smack-tcp