CVE-2018-12366

An invalid grid size during QCMS (color profile) transformations can result in the out-of-bounds read interpreted as a float value. This could leak private data into the output. This vulnerability affects Thunderbird < 60, Thunderbird < 52.9, Firefox ESR < 60.1, Firefox ESR < 52.9, and Firefox < 61.

Weakness

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

Affected Software

Name	Vendor	Start Version	End Version
Enterprise_linux_desktop	Redhat	6.0 (including)	6.0 (including)
Enterprise_linux_desktop	Redhat	7.0 (including)	7.0 (including)
Enterprise_linux_server	Redhat	6.0 (including)	6.0 (including)
Enterprise_linux_server	Redhat	7.0 (including)	7.0 (including)
Enterprise_linux_server_aus	Redhat	7.6 (including)	7.6 (including)
Enterprise_linux_server_eus	Redhat	7.5 (including)	7.5 (including)
Enterprise_linux_server_eus	Redhat	7.6 (including)	7.6 (including)
Enterprise_linux_server_tus	Redhat	7.6 (including)	7.6 (including)
Enterprise_linux_workstation	Redhat	6.0 (including)	6.0 (including)
Enterprise_linux_workstation	Redhat	7.0 (including)	7.0 (including)
Red Hat Enterprise Linux 6	RedHat	firefox-0:60.1.0-5.el6	*
Red Hat Enterprise Linux 6	RedHat	thunderbird-0:52.9.1-1.el6	*
Red Hat Enterprise Linux 7	RedHat	firefox-0:60.1.0-4.el7_5	*
Red Hat Enterprise Linux 7	RedHat	thunderbird-0:52.9.1-1.el7_5	*
Firefox	Ubuntu	artful	*
Firefox	Ubuntu	bionic	*
Firefox	Ubuntu	devel	*
Firefox	Ubuntu	trusty	*
Firefox	Ubuntu	upstream	*
Firefox	Ubuntu	xenial	*
Thunderbird	Ubuntu	artful	*
Thunderbird	Ubuntu	bionic	*
Thunderbird	Ubuntu	devel	*
Thunderbird	Ubuntu	trusty	*
Thunderbird	Ubuntu	upstream	*
Thunderbird	Ubuntu	xenial	*

Potential Mitigations

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.

https://cwe.mitre.org/data/definitions/540.html

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

Out-of-bounds Read

Weakness

Affected Software

Potential Mitigations

References

CVE-2018-12366

Out-of-bounds Read

Weakness

Affected Software

Potential Mitigations

Related Attack Patterns

References