CVE-2025-48734 Fix : Beanutils commons #341
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue:
Apache Commons BeanUtils versions prior to 1.11.0 (1.x) and 2.0.0-M2 (2.x) allowed unauthorized access to the declaredClass property of Java enum objects via PropertyUtilsBean.getProperty() or PropertyUtilsBean.getNestedProperty(). This vulnerability could allow an attacker to access the enum’s classloader and potentially execute arbitrary code. The root cause was that the protective BeanIntrospector introduced in version 1.9.2 was not enabled by default in older versions.
Root Cause:
PropertyUtilsBean allowed access to the declaredClass property of enum objects, enabling attackers to access the ClassLoader. The protective BeanIntrospector introduced in version 1.9.2 suppressed access to declaredClass but was not enabled by default.
Fix:
Upgraded commons-beanutils:commons-beanutils from version 1.9.4 to 1.11.0. This upgrade enables the protective BeanIntrospector by default, preventing unauthorized access to enum classloaders.
The fix is included as part of the forced wsc library upgrade from 64.0.0 to 65.0.0, which brought in the updated BeanUtils version.