You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Java] CWE-117: CodeQL query to detect Log Injection #144
List the CVE ID(s) associated with this vulnerability. GitHub will automatically link CVE IDs to the GitHub Advisory Database.
There is no CVE for this.
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.
Are you planning to discuss this vulnerability submission publicly? (Blog Post, social networks, etc). We would love to have you spread the word about the good work you are doing
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).
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.
Activity
kevinbackhouse commentedon Jan 14, 2021
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.
ghsecuritylab commentedon Jan 14, 2021
Your submission is now in status Closed.
For information, the evaluation workflow is the following:
CodeQL initial assessment > SecLab review > CodeQL review > SecLab finalize > Pay > Closed
dellalibera commentedon Jan 14, 2021
Hi @kevinbackhouse , yes sure. Feel free to close this issue. Hopefully, I will continue to work on the PR later this year.
xcorail commentedon Feb 4, 2021
@porcupineyhairs please create a new issue ... I don't know how our internal tracking will work :)
And close this one once done