-
Notifications
You must be signed in to change notification settings - Fork 250
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
[Java] CWE-117: CodeQL query to detect Log Injection #144
Comments
Hi @dellalibera. It looks like this one hasn't made any progress since last year. Is it ok if I drop it from our bounty pipeline for now? You can resubmit it when it's ready. |
Your submission is now in status Closed. For information, the evaluation workflow is the following: |
Hi @kevinbackhouse , yes sure. Feel free to close this issue. Hopefully, I will continue to work on the PR later this year. |
@dellalibera Do you mind if I take this up then? |
@porcupineyhairs please create a new issue ... I don't know how our internal tracking will work :) |
CVE ID(s)
List the CVE ID(s) associated with this vulnerability. GitHub will automatically link CVE IDs to the GitHub Advisory Database.
Report
Log Injection query is available in c# query, javascript (experimental) query but it is not available in java query.
I created a query to detect a log injection vulnerability in java code.
Link to the PR: PR github/codeql#3882
Result(s)
The query was able to detect a potential Log Forging (now fixed) in the
generator-jhipster
project.This is the PR fixing the potential Log Forging: prevent potential log forging, and here the fixed code https://github.com/jhipster/generator-jhipster/pull/11708/files.
To test the query, I used the vulnerable version of that file. I created a project using
jhipster
(Creating an application), and then I run the query on the project already created; the query was able to detect the vulnerability mentioned in the PR (once I created the project, before generating the database, I replaced the fixed code, with its previous version).There is also a CVE (another project): CVE-2020-4072: Log Forging in generator-jhipster-kotlin, that mentions the equivalent
java
file of thegenerator-jhipter
project: commit: prevent log forging when doing password reset init request.The text was updated successfully, but these errors were encountered: