Han Zheng

A use-after-free issue exists in the CSS rendering engine of Google Chrome. This flaw could allow a remote attacker to exploit heap corruption through a specially crafted HTML page. The Chromium security severity is rated as High.

The issue is related to an integer overflow in the Skia library of Google Chrome, which could allow a remote attacker to potentially exploit heap corruption via a crafted HTML page. The severity of this issue is considered high.

The issue is related to a stack buffer overflow in the Tracing component of Google Chrome, which could allow a remote attacker to exploit stack corruption via a crafted HTML page. This could potentially lead to security breaches. The severity of this issue is considered high.

The issue is related to a use after free vulnerability in the Autofill function of Google Chrome and Microsoft Edge browsers. This vulnerability can be exploited by a remote attacker who convinces the user to engage in specific UI interactions, potentially allowing the execution of arbitrary code via a crafted HTML page. The exploitation may lead to heap corruption.

The issue is related to a use after free vulnerability in the PDFium component of Google Chrome and Microsoft Edge browsers. This vulnerability can be exploited by a remote attacker using specially crafted PDF files, potentially allowing them to disclose protected information. The exploitation is related to heap corruption.

The issue is related to a use after free in PDFium, which can potentially allow a remote attacker to exploit heap corruption via a crafted PDF file. This could lead to the disclosure of protected information. The severity of this issue is classified as Medium by Chromium.

The issue allows for denial of service via packet injection or crafted capture file, specifically affecting the Zigbee TLV dissector in Wireshark.

The issue is related to the IEEE 1609.2 dissector in Wireshark, which can cause a crash, allowing denial of service via packet injection or crafted capture file. This is due to errors in pointer handling. A remote attacker can exploit this issue to cause a denial of service.

The issue is a stack-based buffer over-read in the disasm component, which allows attackers to cause a denial of service, resulting in a crash.

The issue is a null pointer dereference in the `ieee write file` function, which allows attackers to cause a denial of service, resulting in a crash.

A stack-based buffer over-read issue in the disasm function allows attackers to cause a denial of service.

The issue is related to a heap buffer overflow in the libtiff library when processing the `TIFFTAG INKNAMES` and `TIFFTAG NUMBEROFINKS` parameters. This can lead to a denial of service or potentially allow an attacker to execute arbitrary code, causing unexpected application termination.

A problematic issue has been found, affecting the `AP4 File::AP4 File` function of the `Mp42Hevc.cpp` file in the `mp42hevc` component. This issue leads to denial of service and can be initiated remotely.

A problematic issue was found, affecting the `ParseCommandLine` function of the `Mp4Tag/Mp4Tag.cpp` file in the `mp4tag` component. This issue leads to denial of service and can be exploited remotely.

A memory leak was discovered in Bento4 via the AP4 SttsAtom::Create function in mp42hls.

A memory leak was discovered in the AP4 AvcFrameParser::Feed function in mp4mux.

A stack overflow was discovered in the Ndisasm component of nasm.

An issue in Bento4 leads to excessive memory consumption in the `AP4 Array<AP4 ElstEntry>::EnsureCapacity` function, located in Core/Ap4Array.h.

A NULL pointer dereference issue occurs in the `AP4 File::ParseStream` function, located in `Core/Ap4File.cpp`, which is called from `AP4 File::AP4 File`.

An issue was discovered in the function `AP4 DataBuffer::ReallocateBuffer` in `Core/Ap4DataBuffer.cpp`, which leads to excessive memory consumption.