You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Libde265 v1.0.12 was discovered that requested allocation size exceeds maximum supported size of 0x10000000000
Description
Libde265 v1.0.12 was discovered that requested allocation size 0xffffffffffff5b00 (0xffffffffffff6b00 after adjustments for alignment, red zones etc.) exceeds maximum supported size of 0x10000000000 (thread T0).
This vulnerability allows attackers to cause a Denial of Service (DoS) and cause the system storage space to be used up.
It is important to note that we recommend reproducing this vulnerability in a docker environment, as it is likely to affect your operating system and storage space!
The following two images show that my docker storage space was full at the time of fuzzing this vulnerability.
=================================================================
==69==ERROR: AddressSanitizer: requested allocation size 0xffffffffffff5b00 (0xffffffffffff6b00 after adjustments for alignment, red zones etc.) exceeds maximum supported size of 0x10000000000 (thread T0)
#0 0x4c662d in operator new[](unsigned long) (/afltest/libde265/dec265/dec265+0x4c662d)#1 0x4c90d6 in convert_to_8bit(unsigned char const*, int, int, int, int) /afltest/libde265/dec265/dec265.cc:243:18#2 0x4c90d6 in display_sdl(de265_image const*) /afltest/libde265/dec265/dec265.cc:298:12#3 0x4cba68 in output_image(de265_image const*) /afltest/libde265/dec265/dec265.cc:353:12#4 0x4cd633 in main /afltest/libde265/dec265/dec265.cc:802:20#5 0x7ffff790d082 in __libc_start_main /build/glibc-BHL3KM/glibc-2.31/csu/../csu/libc-start.c:308:16
==69==HINT: if you don't care about these errors you may set allocator_may_return_null=1SUMMARY: AddressSanitizer: allocation-size-too-big (/afltest/libde265/dec265/dec265+0x4c662d) in operator new[](unsigned long)==69==ABORTING
Libde265 v1.0.12 was discovered that requested allocation size exceeds maximum supported size of 0x10000000000
Description
Libde265 v1.0.12 was discovered that requested allocation size 0xffffffffffff5b00 (0xffffffffffff6b00 after adjustments for alignment, red zones etc.) exceeds maximum supported size of 0x10000000000 (thread T0).
This vulnerability allows attackers to cause a Denial of Service (DoS) and cause the system storage space to be used up.
It is important to note that we recommend reproducing this vulnerability in a docker environment, as it is likely to affect your operating system and storage space!
The following two images show that my docker storage space was full at the time of fuzzing this vulnerability.
Version
ASAN Log
./dec265/dec265 --noaccel --disable-deblocking --disable-sao -L poc2libde265
Reproduction
PoC
poc2libde265: https://github.com/Frank-Z7/z-vulnerabilitys/blob/main/poc2libde265
Reference
https://github.com/strukturag/libde265
Environment
Credit
Zeng Yunxiang
Song Jiaxuan
The text was updated successfully, but these errors were encountered: