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-2022-23305 @ Maven-log4j:log4j-1.2.17 #34

Open
skyler-kim opened this issue Oct 11, 2022 · 0 comments
Open

CVE-2022-23305 @ Maven-log4j:log4j-1.2.17 #34

skyler-kim opened this issue Oct 11, 2022 · 0 comments

Comments

@skyler-kim
Copy link
Owner

skyler-kim commented Oct 11, 2022

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

By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. 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: skyler-kim
Repository: astlab2
Repository Url: https://github.com/skyler-kim/astlab2
CxAST-Project: skyler-kim/astlab2
CxAST platform scan: f8a2173e-3455-4972-918e-88d3370a431f
Branch: main
Application: astlab2
Severity: HIGH
State: NOT_IGNORED
Status: RECURRENT
CWE: CWE-89


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


References
Advisory
Mail Thread
Advisory

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