CVE-2022-34300

In tinyexr 1.0.1, there is a heap-based buffer over-read in tinyexr::DecodePixelData.

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

Name	Vendor	Start Version	End Version
Tinyexr	Tinyexr_project	1.0.1 (including)	1.0.1 (including)
Asymptote	Ubuntu	bionic	*
Asymptote	Ubuntu	impish	*
Asymptote	Ubuntu	kinetic	*
Asymptote	Ubuntu	lunar	*
Asymptote	Ubuntu	mantic	*
Chromium-browser	Ubuntu	trusty	*
Chromium-browser	Ubuntu	upstream	*
Chromium-browser	Ubuntu	xenial	*
Godot	Ubuntu	impish	*
Godot	Ubuntu	kinetic	*
Godot	Ubuntu	lunar	*
Godot	Ubuntu	mantic	*
Goxel	Ubuntu	bionic	*
Goxel	Ubuntu	impish	*
Goxel	Ubuntu	kinetic	*
Goxel	Ubuntu	lunar	*
Goxel	Ubuntu	mantic	*
Love	Ubuntu	bionic	*
Love	Ubuntu	impish	*
Love	Ubuntu	kinetic	*
Love	Ubuntu	lunar	*
Love	Ubuntu	mantic	*
Mame	Ubuntu	bionic	*
Mame	Ubuntu	impish	*
Mame	Ubuntu	kinetic	*
Mame	Ubuntu	lunar	*
Mame	Ubuntu	mantic	*
Psychtoolbox-3	Ubuntu	bionic	*
Psychtoolbox-3	Ubuntu	impish	*
Psychtoolbox-3	Ubuntu	kinetic	*
Psychtoolbox-3	Ubuntu	lunar	*
Psychtoolbox-3	Ubuntu	mantic	*
Qt6-webengine	Ubuntu	kinetic	*
Qt6-webengine	Ubuntu	lunar	*
Qt6-webengine	Ubuntu	mantic	*
Qtwebengine-opensource-src	Ubuntu	bionic	*
Qtwebengine-opensource-src	Ubuntu	impish	*
Qtwebengine-opensource-src	Ubuntu	kinetic	*
Qtwebengine-opensource-src	Ubuntu	lunar	*
Qtwebengine-opensource-src	Ubuntu	mantic	*
Rbdoom3bfg	Ubuntu	bionic	*
Rbdoom3bfg	Ubuntu	impish	*
Rbdoom3bfg	Ubuntu	kinetic	*
Rbdoom3bfg	Ubuntu	lunar	*
Rbdoom3bfg	Ubuntu	mantic	*
Renderdoc	Ubuntu	impish	*
Renderdoc	Ubuntu	kinetic	*
Renderdoc	Ubuntu	lunar	*
Renderdoc	Ubuntu	mantic	*
Tinyexr	Ubuntu	impish	*
Tinyexr	Ubuntu	kinetic	*
Tinyexr	Ubuntu	lunar	*
Tinyexr	Ubuntu	mantic	*

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-2022-34300
CWE	https://cwe.mitre.org/data/definitions/125.html

Out-of-bounds Read