diff options
author | 2019-03-11 22:28:35 -0400 | |
---|---|---|
committer | 2019-03-11 23:00:39 -0400 | |
commit | 79369681ab3d6785aabf39bd8080cd4f30507524 (patch) | |
tree | 3e9c4e05a8d81cda621b00fff8573469a1830702 /completions | |
parent | commands: allow tiled sticky containers to be moved (diff) | |
download | sway-79369681ab3d6785aabf39bd8080cd4f30507524.tar.gz sway-79369681ab3d6785aabf39bd8080cd4f30507524.tar.zst sway-79369681ab3d6785aabf39bd8080cd4f30507524.zip |
Repair swaynag crash reading message from stdin
When swaynag is run with the -l/--detailed-message option, a crash may
occur if the detailed message read from stdin is large enough. E.g.:
swaynag -m hello -l < ~/.config/sway/config
The root cause is that the read_from_stdin() function under-allocates
memory for the destination buffer which causes that buffer to be overflowed
when copying line data to it with snprintf().
The repair is to allocate one more byte for the terminating null byte.
N.B. although getline() returns the number of bytes read excluding a
terminating null byte, the line buffer is terminated with a null byte. Thus
we have a guarantee that the line buffer will be null terminated (which is
important when copying with snprintf()).
Diffstat (limited to 'completions')
0 files changed, 0 insertions, 0 deletions