CVE-2019-17401

libyal liblnk 20191006 has a heap-based buffer over-read in the networksharenameoffset20 code block of liblnklocationinformationreaddata in liblnklocationinformation.c, a different issue than CVE-2019-17264. NOTE: the vendor has disputed this as described in the GitHub issue...

CVE-2019-17401

libyal liblnk 20191006 has a heap-based buffer over-read in the networksharenameoffset20 code block of liblnklocationinformationreaddata in liblnklocationinformation.c, a different issue than CVE-2019-17264. NOTE: the vendor has disputed this as described in the GitHub issue...

Heap overflow

DISPUTED libyal liblnk 20191006 has a heap-based buffer over-read in the networksharenameoffset20 code block of liblnklocationinformationreaddata in liblnklocationinformation.c, a different issue than CVE-2019-17264. NOTE: the vendor has disputed this as described in the GitHub issue...

CVE-2019-17401

libyal liblnk 20191006 has a heap-based buffer over-read in the networksharenameoffset20 code block of liblnklocationinformationreaddata in liblnklocationinformation.c, a different issue than CVE-2019-17264. NOTE: the vendor has disputed this as described in the GitHub issue...

CVE-2019-17401

libyal liblnk 20191006 has a heap-based buffer over-read in the networksharenameoffset20 code block of liblnklocationinformationreaddata in liblnklocationinformation.c, a different issue than CVE-2019-17264. NOTE: the vendor has disputed this as described in the GitHub issue...

CVE-2019-17401

libyal liblnk 20191006 has a heap-based buffer over-read in the networksharenameoffset20 code block of liblnklocationinformationreaddata in liblnklocationinformation.c, a different issue than CVE-2019-17264. NOTE: the vendor has disputed this as described in the GitHub issue...

CVE-2019-17401

CVE-2019-17401 refers to a heap/over-read issue in libyal liblnk 20191006, specifically in liblnk_location_information_read_data within the network_share_name_offset>20 code block. This is described as a different issue from CVE-2019-17264, and the vendor has disputed it (GitHub issue referenc...

CVE-2019-17264

In libyal liblnk before 20191006, liblnklocationinformationreaddata in liblnklocationinformation.c has a heap-based buffer over-read because an incorrect variable name is used for a certain offset. NOTE: the vendor has disputed this as described in the GitHub issue...

CVE-2019-17264

In libyal liblnk before 20191006, liblnklocationinformationreaddata in liblnklocationinformation.c has a heap-based buffer over-read because an incorrect variable name is used for a certain offset. NOTE: the vendor has disputed this as described in the GitHub issue...

CVE-2019-17263

In libyal libfwsi before 20191006, libfwsiextensionblockcopyfrombytestream in libfwsiextensionblock.c has a heap-based buffer over-read because rejection of an unsupported size only considers values less than 6, even though values of 6 and 7 are also unsupported. NOTE: the vendor has disputed thi...

CVE-2019-17264

In libyal liblnk before 20191006, liblnklocationinformationreaddata in liblnklocationinformation.c has a heap-based buffer over-read because an incorrect variable name is used for a certain offset. NOTE: the vendor has disputed this as described in the GitHub issue...

Heap overflow

DISPUTED In libyal libfwsi before 20191006, libfwsiextensionblockcopyfrombytestream in libfwsiextensionblock.c has a heap-based buffer over-read because rejection of an unsupported size only considers values less than 6, even though values of 6 and 7 are also unsupported. NOTE: the vendor has...

CVE-2019-17263

In libyal libfwsi before 20191006, libfwsiextensionblockcopyfrombytestream in libfwsiextensionblock.c has a heap-based buffer over-read because rejection of an unsupported size only considers values less than 6, even though values of 6 and 7 are also unsupported. NOTE: the vendor has disputed thi...

Heap overflow

DISPUTED In libyal liblnk before 20191006, liblnklocationinformationreaddata in liblnklocationinformation.c has a heap-based buffer over-read because an incorrect variable name is used for a certain offset. NOTE: the vendor has disputed this as described in the GitHub issue...

CVE-2019-17264

CVE-2019-17264 concerns the libyal liblnk library. Affected: liblnk prior to 20191006. The issue is a heap-based buffer over-read in liblnk_location_information_read_data caused by using an incorrect variable name for an offset. The vendor has disputed this in the related GitHub issue. Impact is ...

CVE-2019-17264

In libyal liblnk before 20191006, liblnklocationinformationreaddata in liblnklocationinformation.c has a heap-based buffer over-read because an incorrect variable name is used for a certain offset. NOTE: the vendor has disputed this as described in the GitHub issue...

CVE-2019-17263

In libyal libfwsi (before 20191006), the vulnerability CVE-2019-17263 stems from libfwsi_extension_block_copy_from_byte_stream in libfwsi_extension_block.c, which performs a heap-based buffer over-read due to improper validation of unsupported input sizes. The rejection logic only checks values

CVE-2019-17263

In libyal libfwsi before 20191006, libfwsiextensionblockcopyfrombytestream in libfwsiextensionblock.c has a heap-based buffer over-read because rejection of an unsupported size only considers values less than 6, even though values of 6 and 7 are also unsupported. NOTE: the vendor has disputed thi...

CVE-2019-17263

In libyal libfwsi before 20191006, libfwsiextensionblockcopyfrombytestream in libfwsiextensionblock.c has a heap-based buffer over-read because rejection of an unsupported size only considers values less than 6, even though values of 6 and 7 are also unsupported. NOTE: the vendor has disputed thi...

CVE-2019-17263

In libyal libfwsi before 20191006, libfwsiextensionblockcopyfrombytestream in libfwsiextensionblock.c has a heap-based buffer over-read because rejection of an unsupported size only considers values less than 6, even though values of 6 and 7 are also unsupported. NOTE: the vendor has disputed thi...