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.

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

CVE-2021-4104 @ Maven-log4j:log4j-1.2.17 #65

Closed
apcxtest opened this issue Aug 17, 2023 · 0 comments
Closed

CVE-2021-4104 @ Maven-log4j:log4j-1.2.17 #65

apcxtest opened this issue Aug 17, 2023 · 0 comments

Comments

@apcxtest
Copy link
Owner

Vulnerable Package issue exists @ Maven-log4j:log4j-1.2.17 in branch main

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.

Namespace: apcxtest
Repository: test-repo-pub
Repository Url: https://github.com/apcxtest/test-repo-pub
CxAST-Project: apcxtest/test-repo-pub
CxAST platform scan: a314b9e1-0b75-4c05-86f0-fa4203a6e7fd
Branch: main
Application: test-repo-pub
Severity: MEDIUM
State: TO_VERIFY
Status: RECURRENT
CWE: CWE-502


Additional Info
Attack vector: NETWORK
Attack complexity: HIGH
Confidentiality impact: HIGH
Availability impact: HIGH


References
Advisory
Disclosure
Advisory
Mail Thread
Other
Other

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant