-
Notifications
You must be signed in to change notification settings - Fork 253
[Go]: Add support of github.com/jackc/pgx and related packages #481
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
Comments
Hi @japroc, |
Hi @japroc, any updates on this? |
Hi antonio-morales, I faced some problems with writing tests. And completely forgot about that issue :) |
Do you have an update? |
I'm closing the issue, but feel free to open it again if you have updates on it. |
Your submission is now in status Closed. For information, the evaluation workflow is the following: |
Query
Link to pull request with your CodeQL query:
Relevant PR: github/codeql-go#607
CVE ID(s)
List the CVE ID(s) associated with this vulnerability. GitHub will automatically link CVE IDs to the GitHub Advisory Database.
Report
Describe the vulnerability. Provide any information you think will help GitHub assess the impact your query has on the open source community.
The idea of this PR is to improve default
SqlInjection.ql
query by addinggithub.com/jackc/pgx
module and related.I basically reused existing
SqlInjection.ql
query, and created a customPgxSqlInjection.ql
query. The CodeQL custom module with implements pgx sql argument is defined inPgx.qll
file. I think that pgx support should be implemented by extendingSQL::QueryString
.When this module will be moved from experimental folder to standart library, it would automatically improve existing Sqlnjection.ql query. But for now, for a demonstration, i created a separate query which imports experimental module and repeats standart query. I also added snippet for pgx usage and qhelp.
Result(s)
Provide at least one useful result found by your query, on some revision of a real project.
I have made a series of queries using lgtm.com.
There are findings:
https://lgtm.com/query/4453866281735326417/
https://lgtm.com/query/2344985243544414322/
https://lgtm.com/query/3110488658498384350/
The text was updated successfully, but these errors were encountered: