- 24 Nov, 2020 1 commit
-
-
Rosen Penev authored
[clang-tidy] Found with bugprone-macro-parentheses Signed-off-by:
Rosen Penev <rosenp@gmail.com>
-
- 21 Nov, 2020 1 commit
-
-
Nikias Bassen authored
-
- 08 Jun, 2020 1 commit
-
-
Martin Szulecki authored
-
- 03 Jun, 2020 1 commit
-
-
Rosen Penev authored
[clang-tidy] Found with readability-redundant-control-flow Signed-off-by:
Rosen Penev <rosenp@gmail.com>
-
- 14 May, 2020 1 commit
-
-
Nikias Bassen authored
-
- 11 May, 2020 1 commit
-
-
Nikias Bassen authored
-
- 09 Dec, 2019 3 commits
-
-
Nikias Bassen authored
-
Nikias Bassen authored
-
XD authored
This improves performance by at least 30% for large files, and also reduces the memory footprint.
-
- 07 Nov, 2019 1 commit
-
-
Nikias Bassen authored
Add plist_to_bin_free() and plist_to_xml_free() functions that free memory allocated by plist_to_bin()/plist_to_xml()
-
- 18 Jan, 2019 1 commit
-
-
Nikias Bassen authored
-
- 10 Dec, 2018 2 commits
-
-
Nikias Bassen authored
-
Nikias Bassen authored
-
- 30 Nov, 2018 1 commit
-
-
Nikias Bassen authored
-
- 29 Nov, 2018 1 commit
-
-
Nikias Bassen authored
-
- 31 May, 2017 1 commit
-
-
Nikias Bassen authored
ASAN reported possible undefined behaviour when writing float/double values to misaligned addresses.
-
- 29 May, 2017 1 commit
-
-
Nikias Bassen authored
These misaligned reads reported by ASAN might lead to undefined behavior.
-
- 20 Apr, 2017 2 commits
-
-
Nikias Bassen authored
Credit to Christophe Fergeau
-
Nikias Bassen authored
-
- 19 Apr, 2017 1 commit
-
-
Nikias Bassen authored
-
- 26 Mar, 2017 1 commit
-
-
Nikias Bassen authored
Because on 32-bit platforms 32-bit pointers and 64-bit sizes have been used for the sanity checks of the offset table and object references, the range checks would fail in certain interger-overflowish situations, causing heap buffer overflows or other unwanted behavior. Fixed by wideing the operands in question to 64-bit.
-
- 10 Feb, 2017 2 commits
-
-
Nikias Bassen authored
Passing a size of 0xFFFFFFFFFFFFFFFF to parse_string_node() might result in a memcpy with a size of -1, leading to undefined behavior. This commit makes sure that the actual node data (which depends on the size) is in the range start_of_object..start_of_object+size. Credit to OSS-Fuzz
-
Nikias Bassen authored
Credit to OSS-Fuzz
-
- 09 Feb, 2017 1 commit
-
-
Nikias Bassen authored
Credit to OSS-Fuzz
-
- 07 Feb, 2017 4 commits
-
-
Nikias Bassen authored
-
Nikias Bassen authored
Credit to OSS-Fuzz
-
Nikias Bassen authored
Credit to OSS-Fuzz
-
Nikias Bassen authored
Credit to Wang Junjie <zhunkibatu@gmail.com> (#93)
-
- 06 Feb, 2017 2 commits
-
-
Nikias Bassen authored
-
Nikias Bassen authored
-
- 05 Feb, 2017 5 commits
-
-
Nikias Bassen authored
-
Nikias Bassen authored
This commit adds proper debug/error messages being printed if the binary plist parser encounters anything abnormal. To enable debug logging, libplist must be configured with --enable-debug, and the environment variable PLIST_BIN_DEBUG must be set to "1".
-
Nikias Bassen authored
-
Nikias Bassen authored
-
Nikias Bassen authored
-
- 04 Feb, 2017 1 commit
-
-
Nikias Bassen authored
Issue #92 pointed out an problem with (invalid) bplist files which have exactly one structured node whose subnode reference itself. The recursion check used a fixed size array with the size of the total number of objects. In this case the number of objects is 1 but the recursion check code wanted to set the node_index for the level 1 which leads to an OOB write on the heap. This commit fixes/improves two things: 1) Prevent OOB write by using a dynamic data storage for the used node indexes (plist_t of type PLIST_ARRAY) 2) Reduces the memory usage of large binary plists, because not the total number of nodes in the binary plist, but the number of recursion levels is important for the recursion check.
-
- 03 Feb, 2017 2 commits
-
-
Nikias Bassen authored
As reported in #91, the code that will read the big endian integer value of variable size did not check if the actual number of bytes is still withing the range of the actual plist data. This commit fixes the issue with proper bounds checking.
-
Nikias Bassen authored
-
- 01 Feb, 2017 2 commits
-
-
Nikias Bassen authored
-
Nikias Bassen authored
The sizes where effectively parsed by calling parse_uint_node() which allocates a node_t (along with plist_data_t) that is immediately freed after retrieving the integer value it holds. This commit changes the code to directly operate on the binary stream to 'just' read the size instead, reducing the memory footprint further.
-