J00Ru

A problematic vulnerability has been found in FFmpeg, affecting the `decode pulses` function. This issue leads to memory corruption and can be initiated remotely.

A critical issue affects the function `decode slice header` of the file `libavcodec/h64.c`, leading to memory corruption. The attack can be launched remotely.

A problem has been found in the decode frame function of the libavcodec/ansi.c file. This issue leads to an integer coercion error and can be exploited remotely.

A problematic issue has been found in FFmpeg, affecting the `add yblock` function of the `libavcodec/snow.h` file. This manipulation leads to memory corruption and can be initiated remotely.

A problem has been found in FFmpeg. It is related to an unknown function in the libavcodec/dxtroy.c file, which leads to an integer coercion error. This issue can be exploited remotely.

A problem has been found that affects the `msrle decode frame` function of the file libavcodec/msrle.c. This issue leads to memory corruption and can be initiated remotely.

The issue is related to a heap-based buffer over-read in the `tt cmap14 validate` function located in `sfnt/ttcmap.c`.

The issue is related to the zlib component in the Compression module, which fails to initialize memory for a specific data structure. This allows remote attackers to execute arbitrary code via a crafted web site.

The issue concerns the `t42 parse encoding` function in `type42/t42parse.c`, which does not properly update the current position for immediates-only mode. This allows remote attackers to cause a denial of service, specifically an infinite loop, by providing a Type42 font.

The issue is related to several functions in FreeType, including `t1 parse font matrix`, `cid parse font matrix`, `t42 parse font matrix`, and `ps parser load field`, which do not check return values. This allows remote attackers to cause a denial of service, resulting in uninitialized memory access and application crash, or possibly have other unspecified impacts through a crafted font.

win32k.sys in the kernel-mode drivers in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows Server 2012, and Windows RT allows local users to gain privileges via a crafted application, aka "Win32k Multiple Fetch Vulnerability," a different vulnerability than CVE-2013-1342, CVE-2013-1343, CVE-2013-1344, and CVE-2013-3864.

win32k.sys in the kernel-mode drivers in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows Server 2012, and Windows RT allows local users to gain privileges via a crafted application, aka "Win32k Multiple Fetch Vulnerability," a different vulnerability than CVE-2013-1342, CVE-2013-1343, CVE-2013-1344, and CVE-2013-3865.

Elevation of privilege issues exist due to the Windows kernel-mode driver's improper handling of objects in memory. An attacker who successfully exploits these issues could gain elevated privileges and read arbitrary amounts of kernel memory.

win32k.sys in the kernel-mode drivers in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows Server 2012, and Windows RT allows local users to gain privileges via a crafted application, aka "Win32k Multiple Fetch Vulnerability," a different vulnerability than CVE-2013-1342, CVE-2013-1343, CVE-2013-3864, and CVE-2013-3865.

win32k.sys in the kernel-mode drivers in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows Server 2012, and Windows RT allows local users to gain privileges via a crafted application, aka "Win32k Multiple Fetch Vulnerability," a different vulnerability than CVE-2013-1342, CVE-2013-1344, CVE-2013-3864, and CVE-2013-3865.

The NT Virtual DOS Machine (NTVDM) subsystem in the kernel in Microsoft Windows XP SP3, Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2, Windows 7 SP1, and Windows 8 on 32-bit platforms does not properly validate kernel-memory addresses, which allows local users to gain privileges or cause a denial of service (memory corruption) via a crafted application, aka "Windows Kernel Memory Corruption Vulnerability," a different vulnerability than CVE-2013-3196 and CVE-2013-3198.

The NT Virtual DOS Machine (NTVDM) subsystem in the kernel in Microsoft Windows XP SP3, Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2, Windows 7 SP1, and Windows 8 on 32-bit platforms does not properly validate kernel-memory addresses, which allows local users to gain privileges or cause a denial of service (memory corruption) via a crafted application, aka "Windows Kernel Memory Corruption Vulnerability," a different vulnerability than CVE-2013-3196 and CVE-2013-3197.

An issue exists where the Windows kernel does not properly handle objects in memory, allowing local users to obtain sensitive information from kernel memory. This could be achieved via a crafted application.

The issue is related to a race condition in the win32k.sys kernel-mode driver, which allows local users to gain privileges via a crafted application. This is due to improper handling of objects in memory. An attacker who successfully exploits this could gain elevated privileges and read arbitrary amounts of kernel memory.

A race condition in the win32k.sys kernel-mode driver allows local users to gain privileges and read the contents of arbitrary kernel memory locations via a crafted application.