Database Administration (MOSC)

MOSC Banner

CVE-2021-4104 log4j 1.2 and Oracle Database vulnerability using JMS Appdender

in Database Administration (MOSC) 1 commentAnswered

Hello,

There was another update regarding log4j attack.

Version 1.2 is also vulnerable to the similar attack if using JMS Appender.

My Oracle DB returns a bunch of JMS tags in jms.xml and others. I wonder if Oracle is using it. so far it looks like just some files left over with installation. These search results came on both my Oracle DBs. Does anyone know if it's being used or just files remaining offline?


CVE-2021-4104 log4

"JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions."

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