CVE-2019-7635

SDL (Simple DirectMedia Layer) through 1.2.15 and 2.x through 2.0.9 has a heap-based buffer over-read in Blit1to4 in video/SDL_blit_1.c.

The product reads data past the end, or before the beginning, of the intended buffer.

Name	Vendor	Start Version	End Version
Simple_directmedia_layer	Libsdl	*	1.2.15 (including)
Simple_directmedia_layer	Libsdl	2.0.0 (including)	2.0.9 (including)
Red Hat Enterprise Linux 7	RedHat	SDL-0:1.2.15-17.el7	*
Red Hat Enterprise Linux 8	RedHat	SDL-0:1.2.15-38.el8	*
Libsdl1.2	Ubuntu	bionic	*
Libsdl1.2	Ubuntu	cosmic	*
Libsdl1.2	Ubuntu	disco	*
Libsdl1.2	Ubuntu	esm-infra-legacy/trusty	*
Libsdl1.2	Ubuntu	esm-infra/bionic	*
Libsdl1.2	Ubuntu	esm-infra/xenial	*
Libsdl1.2	Ubuntu	trusty	*
Libsdl1.2	Ubuntu	trusty/esm	*
Libsdl1.2	Ubuntu	upstream	*
Libsdl1.2	Ubuntu	xenial	*
Libsdl2	Ubuntu	bionic	*
Libsdl2	Ubuntu	cosmic	*
Libsdl2	Ubuntu	disco	*
Libsdl2	Ubuntu	esm-apps/bionic	*
Libsdl2	Ubuntu	esm-apps/xenial	*
Libsdl2	Ubuntu	esm-infra-legacy/trusty	*
Libsdl2	Ubuntu	trusty	*
Libsdl2	Ubuntu	trusty/esm	*
Libsdl2	Ubuntu	upstream	*
Libsdl2	Ubuntu	xenial	*
Libsdl2-image	Ubuntu	bionic	*
Libsdl2-image	Ubuntu	cosmic	*
Libsdl2-image	Ubuntu	disco	*
Libsdl2-image	Ubuntu	esm-apps/bionic	*
Libsdl2-image	Ubuntu	esm-apps/xenial	*
Libsdl2-image	Ubuntu	esm-infra-legacy/trusty	*
Libsdl2-image	Ubuntu	trusty	*
Libsdl2-image	Ubuntu	trusty/esm	*
Libsdl2-image	Ubuntu	upstream	*
Libsdl2-image	Ubuntu	xenial	*
Sdl-image1.2	Ubuntu	bionic	*
Sdl-image1.2	Ubuntu	cosmic	*
Sdl-image1.2	Ubuntu	disco	*
Sdl-image1.2	Ubuntu	esm-apps/bionic	*
Sdl-image1.2	Ubuntu	esm-apps/xenial	*
Sdl-image1.2	Ubuntu	esm-infra-legacy/trusty	*
Sdl-image1.2	Ubuntu	trusty	*
Sdl-image1.2	Ubuntu	trusty/esm	*
Sdl-image1.2	Ubuntu	upstream	*
Sdl-image1.2	Ubuntu	xenial	*

Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.

NVD	https://nvd.nist.gov/vuln/detail/CVE-2019-7635
CWE	https://cwe.mitre.org/data/definitions/125.html

Out-of-bounds Read