We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
Log4j has the security risk of remote code execution.
see: https://issues.apache.org/jira/projects/LOG4J2/issues/LOG4J2-3201
upgrade log4j jar, or add JVM params to avoid the problem.
No response
master
InLong Manager, InLong Agent, InLong DataProxy, InLong DataProxy-SDK, InLong TubeMQ, InLong Sort
The text was updated successfully, but these errors were encountered:
healchow
Successfully merging a pull request may close this issue.
What happened
Log4j has the security risk of remote code execution.
see: https://issues.apache.org/jira/projects/LOG4J2/issues/LOG4J2-3201
What you expected to happen
upgrade log4j jar, or add JVM params to avoid the problem.
How to reproduce
see: https://issues.apache.org/jira/projects/LOG4J2/issues/LOG4J2-3201
Environment
No response
InLong version
master
InLong Component
InLong Manager, InLong Agent, InLong DataProxy, InLong DataProxy-SDK, InLong TubeMQ, InLong Sort
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: