-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
[🐞] Found 3 gosec issues: CWE-78 and CWE-242 #5
Comments
OK, issue closed, but what's decision do you have? 😉 I mean, it's normal to have this issues now (Fiber is too young), but if we can use external tools (like gosec) for checking security (an not so) issues at code and save our users — let's do it! 😀 This is some info about G103 (CWE-242) issue: I fixed two similar issues at #4, but I need help, because I'm not author of Fiber, unfortunately, and don't know why it's important to use |
@koddr Thanks for your contribution!
|
@Fenny thx for awesome framework, btw 😃
Potentially, how we can solve this? Or not any other ways to do this (so easy as unsafe)? |
@koddr , So changing this won't matter since it's still being used by the |
Your environment:
1.2.3
]:1.2.3
macOS 10.14.6
]:macOS 10.14.6
1.13.7
]:1.13.7
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
$ gosec ./...
Issue G204 (CWE-78): Subprocess launched with function call as argument or cmd arguments:
Issue G103 (CWE-242): Use of unsafe calls should be audited:
Expected behavior
No security issues on report.
Screenshots
No need.
Additional context
Full console output:
The text was updated successfully, but these errors were encountered: