Kostya Serebryany

The issue in the GNU C Library (glibc) might allow context-dependent attackers to cause a denial of service, resulting in an application crash. This can be demonstrated by using the fnmatch library function with a specific pattern.

The issue is caused by a heap-based buffer overflow in the `xmlFAParsePosCharGroup` function. This can be exploited by a remote attacker using a specially crafted XML document, potentially allowing them to execute arbitrary code or cause a denial of service due to memory corruption.

The issue is related to the XPC Services API in LaunchServices, which has inadequate access control. This allows an attacker to bypass event-handler restrictions and modify events of arbitrary apps using a crafted app. The estimated number of potentially affected devices is not specified. There is no information about real-world incidents where this issue was exploited.

The issue allows context-dependent attackers to read arbitrary files or cause a denial of service due to an XML external entity (XXE) vulnerability in the `xmlStringLenDecodeEntities` function. This vulnerability can be exploited by remote attackers to disclose protected information or cause resource consumption.

The issue is related to a heap-based buffer over-read in the `T1 Get Private Dict` function located in `type1/t1parse.c`.

The issue is related to a buffer over-read in the skip comment function in psaux/psobjs.c. This occurs because ps parser skip PS token is mishandled during an FT New Memory Face operation.

A buffer over-read issue occurs in the `T1 Get Private Dict` function within `type1/t1parse.c` due to a lack of checks on the new values of `cur` and `limit` before proceeding. This issue affects FreeType versions prior to 2.6.1.

The issue allows context-dependent attackers to cause a denial of service, resulting in an application crash, by providing a malformed pattern that triggers an out-of-bounds read in the fnmatch function.

The issue is a heap-based buffer overflow in the `xmlGROW` function in `parser.c` in libxml2. This allows context-dependent attackers to obtain sensitive process memory information via unspecified vectors. A remote attacker could provide a specially crafted XML or HTML file that, when processed by an application using libxml2, would cause that application to use an excessive amount of CPU, leak potentially sensitive information, or crash the application.

The issue is related to the xmlParseMisc function in parser.c, which allows context-dependent attackers to cause a denial of service due to an out-of-bounds heap read. This is related to incorrect entities boundaries and start tags.

The issue is related to the xmlParseConditionalSections function in the libxml2 library, which can cause a denial of service due to an out-of-bounds read when parsing specially crafted XML data. This can lead to a crash. The problem arises because the function does not properly handle intermediary entities when it encounters invalid input.