How To Secure OAM 10g Configuration Files (Doc ID 1609162.1)

Last updated on JUNE 07, 2017

Applies to:

COREid Access - Version 10.1.4.0.1 to 10.1.4.3.0
Information in this document applies to any platform.

Goal

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? 
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms