SQL Developer (MOSC)

MOSC Banner

log4j 1.2.13 in libraries being flagged

in SQL Developer (MOSC) 4 commentsAnswered

Hello in the latest version of sql developer (23.1.1.345.2114) their is a log4j-1.2.13.jar present. I am trying to fix findings that keep reporting this as a vulnerability. In our case the sql developer instance is under the oracle reports (12.2.1.4) server home.

The documentation on MOSC indicate that installing the latest version of sql dveloper into the home should resolve the vulnerability, how ever it looks like the jar is still present and is being flagged.

Is there any other options I can try? do we need to have the copy of sql developer in the reports home if users don't use it? can we just remove the old 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