ENV#[]=: Disallow null bytes in key and value #5216
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Before this, a call to `ENV[k] = v` would not check for NUL-bytes.
`setenv(3)` would then take the key and value, and as it doesn't know
about the embedded NUL-byte(s) in the key and/or value, would truncate
at the NUL-byte.
This may not sound too terrible at first. But it can turn into a
security issue:
```cr
from_user = "DO-SOMETHING-BAD\0GOOD" # Received from user input
if from_user.ends_with?("GOOD") # Will match
ENV["FOO"] = from_user # Will set "FOO" to "DO-SOMETHING-BAD"
end
```
Papierkorb
force-pushed
the
disallow-nul-in-setenv
branch
from
e0c1b8d
to
81a4c29
Compare
asterite
requested changes
Oct 31, 2017
| def self.[]=(key : String, value : String?) | ||
| raise ArgumentError.new("Key contains null byte") if key.byte_index(0) |
There was a problem hiding this comment.
You can simply do key.check_no_null_byte
There was a problem hiding this comment.
Same applies to value, of course
There was a problem hiding this comment.
Yes I had that at first, but then chose to tell if the key or the value is the culprit
asterite
approved these changes
Oct 31, 2017
RX14
approved these changes
Oct 31, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Make
ENV#[]=raise anArgumentErrorif key or value contain a NUL byte.Before this, a call to
ENV[k] = vwould not check for NUL-bytes.setenv(3)would then take the key and value, and as it doesn't knowabout the embedded NUL-byte(s) in the key and/or value, would truncate
at the NUL-byte.
This may not sound too terrible at first. But it can turn into a
security issue:
Truncating user input is a real issue, with exploitation in the wild: https://mathiasbynens.be/notes/mysql-utf8mb4
Regards,
Korb