aboutsummaryrefslogtreecommitdiff
path: root/ChangeLog.12
diff options
context:
space:
mode:
authorSiddhesh Poyarekar <siddhesh@redhat.com>2014-01-27 16:49:33 +0530
committerSiddhesh Poyarekar <siddhesh@redhat.com>2014-01-27 16:49:33 +0530
commitd7b00f98106a0f1e3d753b135eeb97dfdf6e2e74 (patch)
tree4b8860ccb6e18818323f06063edba56aa4f2d3d3 /ChangeLog.12
parentaf37a8a3496327a6e5617a2c76f17aa1e8db835e (diff)
downloadglibc-d7b00f98106a0f1e3d753b135eeb97dfdf6e2e74.zip
glibc-d7b00f98106a0f1e3d753b135eeb97dfdf6e2e74.tar.gz
glibc-d7b00f98106a0f1e3d753b135eeb97dfdf6e2e74.tar.bz2
Fix invalid memory access when parsing netgroup files with blank lines (BZ #16506)
The netgroups file parsing code tries to access the character before the newline in parsed lines to see if it is a backslash (\). This results in an access before the block allocated for the line if the line is blank, i.e. does not have anything other than the newline character. This doesn't seem like it will cause any crashes because the byte belongs to the malloc metadata block and hence access to it will always succeed. There could be an invalid alteration in code flow where a blank line is seen as a continuation due to the preceding byte *happening* to be '\\'. This could be done by interposing malloc, but that's not really a security problem since one could interpose getnetgrent_r itself and achieve a similar 'exploit'. The possibility of actually exploiting this is remote to impossible since it also requires the previous line to end with a '\\', which would happen only on invalid configurations.
Diffstat (limited to 'ChangeLog.12')
0 files changed, 0 insertions, 0 deletions