Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

migrate log4j v1 to log4j v2 #184

Closed
AlvaroVega opened this issue Dec 13, 2021 · 2 comments
Closed

migrate log4j v1 to log4j v2 #184

AlvaroVega opened this issue Dec 13, 2021 · 2 comments

Comments

@AlvaroVega
Copy link
Member

AlvaroVega commented Dec 13, 2021 •
edited
Loading

Perseo-core is using:

  • slf4j which uses log4j version 1.2,
  • log4j version 1.2

https://logging.apache.org/log4j/1.2/

Security Vulnerabilities

A security vulnerability, CVE-2019-17571 has been identified against Log4j 1. Log4j includes a SocketServer that accepts serialized log events and deserializes them without verifying whether the objects are allowed or not. This can provide an attack vector that can be expoited. Since Log4j 1 is no longer maintained this issue will not be fixed. Users are urged to upgrade to Log4j 2.
@AlvaroVega AlvaroVega pinned this issue Dec 13, 2021
@AlvaroVega
Copy link
Member Author

https://logging.apache.org/log4j/2.x/manual/migration.html

@AlvaroVega AlvaroVega mentioned this issue Dec 13, 2021
Merged
@fgalan
Copy link
Member

fgalan commented Feb 16, 2022

Fixed in PR #185

@fgalan fgalan closed this as completed Feb 16, 2022
@AlvaroVega AlvaroVega unpinned this issue Feb 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@AlvaroVega @fgalan