-
Notifications
You must be signed in to change notification settings - Fork 1.8k
CPP: Add query for CWE-377 Insecure Temporary File #6947
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for another contribution, @ihsinme. Here is my first round of comments.
cpp/ql/src/experimental/Security/CWE/CWE-377/InsecureTemporaryFile.ql
Outdated
Show resolved
Hide resolved
cpp/ql/src/experimental/Security/CWE/CWE-377/InsecureTemporaryFile.ql
Outdated
Show resolved
Hide resolved
cpp/ql/src/experimental/Security/CWE/CWE-377/InsecureTemporaryFile.ql
Outdated
Show resolved
Hide resolved
cpp/ql/src/experimental/Security/CWE/CWE-377/InsecureTemporaryFile.ql
Outdated
Show resolved
Hide resolved
cpp/ql/src/experimental/Security/CWE/CWE-377/InsecureTemporaryFile.ql
Outdated
Show resolved
Hide resolved
It looks like our CI is failing with a couple of errors:
Sounds like there's a hidden non-ASCII character around line 94.
|
Good afternoon. |
Co-authored-by: Mathias Vorreiter Pedersen <mathiasvp@github.com>
Good afternoon @MathiasVP. Please tell me what the error is during the assembly. (I fixed the previous error) |
It's still complaining about a non-ASCII character:
|
please run the checks again. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Our request is looking for situations of unsafe work with files. use validation functions in the first place without guaranteeing that the file will not be created later. in the second case, he looks for places to work with the file, when his name is predictable and there are no restrictions on access rights.
CVE-2012-0786
CVE-2018-6198
CVE-2007-5936
links to real work results, I will add later. I am currently working on them with developers.