Enterprise Manager Generic (MOSC)

MOSC Banner

Log4j Remediation EM 13.4

in Enterprise Manager Generic (MOSC) 1 commentAnswered

Server Red Hat Enterprise Linux Server release 7.9 (Maipo)

OMR 19c

OMS 13.4 no patches

To temporarily remediate the log4j issue we set permissions to 000

The files still showed on a scan, but access to OEM remained unchanged. We then thought we'd rename them. Rename seemed to do no harm, but they still showed on a scan. We then moved them off the server to a zip file. Now we cannot login to OEM every user gets an error that the username or password is invalid. We put the files back, but still cannot login. Any suggestions?

./user_projects/domains/GCDomain/servers/EMGC_OMS1/tmp/_WL_user/emdb/r251e3/database/jet/emsaasui/emcdbms-ui/ear/APP-INF/lib/log4j-1.2.16.jar

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center