How To Secure OAM 10g Configuration Files
(Doc ID 1609162.1)
Last updated on FEBRUARY 03, 2019
Applies to:COREid Access - Version 10.1.4.0.1 to 10.1.4.3.0
Information in this document applies to any platform.
OAM 10g configuration files are stored in a clear, and are readable by anyone who has access to the host server. Eg. information such as LDAP master account and password are exposed in /access/oblix/config/ldap/AppDB.xml.
The passwords contained in these files are weakly obfuscated. Anyone who has access to this file can use this information to defeat OAM protection.
Example exploit: With the master LDAP credentials, an attacker can gain access to LDAP and obtain the OAM Shared Secret Encryption key. This can be used by an attacker to generate OAM user token for any user.
How to mitigate this vulnerability?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document