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
Hi,
for log4j 1.x mitigation it could be important, to scan for the file log4j.properties contens the string "JMS" because of
#configuring the custom logger log4j.logger.com.apress.logging.log4j=DEBUG, JMS
in log4j.properties could be a vulnaribility for log4j 1.x
And log4j.properties can be part of a jar or war file
Thx a lot 4 log4j_detector!
Andreas
The text was updated successfully, but these errors were encountered:
Neat idea !
Sorry, something went wrong.
No branches or pull requests
Hi,
for log4j 1.x mitigation it could be important, to scan for the file log4j.properties contens the string "JMS" because of
content like
#configuring the custom logger
log4j.logger.com.apress.logging.log4j=DEBUG, JMS
#configuring the JMS appender
log4j.appender.JMS=org.apache.log4j.net.JMSAppender
log4j.appender.JMS.topicConnectionFactoryBindingName=TopicConnectionFactory
log4j.appender.JMS.topicBindingName=loggingTopic
in log4j.properties could be a vulnaribility for log4j 1.x
And log4j.properties can be part of a jar or war file
Thx a lot 4 log4j_detector!
Andreas
The text was updated successfully, but these errors were encountered: