OpenIDM Security Advisory #201602
Security vulnerabilities have been discovered in OpenIDM components. These issues are present in versions of OpenIDM including 3.x and 4.0.x.
April 1, 2016
Security vulnerabilities have been discovered in OpenIDM components. These issues are present in versions of OpenIDM including 3.x and 4.0.x.
This advisory provides guidance on how to ensure your deployments can be secured. Workarounds or patches are available for all of the issues.
The maximum severity of issues in this advisory is High. Deployers should take steps as outlined in this advisory and deploy the recommended workarounds or resolutions as described within each issue below.
Issue #201602-01: Unencrypted Repo JDBC Password
| Product | OpenIDM |
|---|---|
| Affected versions | 3.0.0, 3.1.0, 4.0.0 |
| Fixed versions | Unresolved |
| Component | OpenIDM JDBC Repository Server |
| Severity | High |
| Issue Tracker ID | OPENIDM-2852 |
Description:
JDBC Repository passwords are no longer auto-encrypted by OpenIDM when the repository is activated. As a result, the password stored within the repository configuration as well as those written to the JSON configuration files (repo.jdbc.json or datasource.jdbc-default.json) and the OpenIDM log will appear in clear-text.
Workaround:
Manually encrypt the JDBC Repository password using the OpenIDM Command-Line Interface as detailed in the following Knowledge Article: Repository password is not encrypted in OpenIDM 4.x log and configuration files.
Resolution:
None
Change Log
The following table tracks changes to the security advisory:
| Date | Description |
|---|---|
| February 24, 2021 | Added ForgeRock Identity Platform taxon to improve categorization |