diff options
| author | 2026-09-27 15:06:22 +0900 | |
|---|---|---|
| committer | 2026-09-29 16:39:28 +0200 | |
| commit | f168c10b52325b00da6355989a18a11743b33f89 (patch) | |
| tree | 186ef3afe45963fcfca15daf8efebf0f2151360e /test/xml_behavior.test | |
| parent | 8b48fa72d359de89215f50cbf6ac8c77ae5de9b4 (diff) | |
| download | libplist-f168c10b52325b00da6355989a18a11743b33f89.tar.gz libplist-f168c10b52325b00da6355989a18a11743b33f89.tar.bz2 | |
bytearray: Handle realloc() failure in byte_array_grow()
byte_array_grow() assigned the result of realloc() directly to
ba->data and increased the capacity even if realloc() failed, so the
following memcpy() in byte_array_append() wrote to NULL + len.
On failure, free the old buffer and leave the byte array in a failed
state (data == NULL), which byte_array_append() already ignores. The
callers check for that state:
- the writers (bin, xml, json, openstep and the text output formats)
return PLIST_ERR_NO_MEM instead of handing out a NULL/truncated buffer
- node_to_xml() base64-encodes <data> directly into the grown buffer,
so it must bail out there (only guarded by assert() before)
- the OpenStep parser returns PLIST_ERR_NO_MEM for <hex data> instead of
silently returning truncated data
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Diffstat (limited to 'test/xml_behavior.test')
0 files changed, 0 insertions, 0 deletions
