Organizations running Symantec Identity Manager (IM) versions 14.5.x or 15.0 may be flagged for Apache Log4j Core vulnerabilities. Security scans typically recommend upgrading to Log4j version 2.25.4 or higher to mitigate these risks.
IM 14.5 and 15.0
Vulnerabilities within older versions of the Apache Log4j Core library (CVE-2021-44228 and others) require the replacement of specific JAR files with secure versions provided by engineering.
The remediation is included in Fix Pack 6. It is recommended to upgrade to this version to receive the Log4j 2.25.4 updates automatically.
A specific hotfix (HF_LOG4J_FIX.zip) is required to update libraries to version 2.25.4.
log4j-core-2.25.4.jar and log4j-api-2.25.4.jar to the following locations:../IAM_Suite/IdentityManager/tools/lib../IAM_Suite/IdentityManager/tools/samples/Support/IMInfo../IAM_Suite/IdentityManager/tools/SelectiveExportUtility../iam_im.ear/library../PatchDeployerTool/lib../PatchDeployerTool/patch/iam_im.ear/library../IAM Suite/Identity Manager/tools/ImportExportUtility/ImportExportUtil.bat (and .sh)../IAM Suite/Identity Manager/tools/PasswordTool/pwdtools.bat (and .sh)/modules/com/ca/iam/log4j2/core/main/ and /api/main/.module.xml version references to 2.25.4 in both directories.log4j-api.jar and log4j-core.jar and replace them in ..\\CA\\Identity Manager\\Bulk Loader\\lib\\.Important: Do not leave old copies of the JAR files in the same location with a
.jarextension (e.g.,.jar.bak) to avoid class-loading conflicts.
The following components use log4j-mitigated.jar (version 1.2.17), which has had vulnerable classes physically removed and does not require an upgrade to 2.x at this time: