Fix use of kernel.open or IO.read or similar sinks with a non-constant value
#665
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ruby-pg/spec/helpers.rb
Lines 477 to 480 in dae9173
Call to Kernel.open with a non-constant value. Consider replacing it with File.open. If Kernel.open is given a file name that starts with a | character, it will execute the remaining string as a shell command. If a malicious user can control the file name, they can execute arbitrary code. The same vulnerability applies to IO.read, IO.write, IO.binread, IO.binwrite, IO.foreach, IO.readlines and URI.open.
fix the problem, replace the call to
openon line 477 withFile.open. This change ensures that the file is opened for writing without the risk of command injection, asFile.opendoes not interpret file names starting with|as shell commands. No additional imports or changes are needed, asFileis part of Ruby's core library. The change should be made only to the affected line, preserving the rest of the logic and block structure.References
Command Injection. Ruby on Rails Cheat Sheet: Command Injection
Command Injection in RDoc