CVE-2023-43788

A vulnerability was found in libXpm due to a boundary condition within the XpmCreateXpmImageFromBuffer() function. This flaw allows a local attacker to trigger an out-of-bounds read error and read the contents of memory on the system.

Weakness

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

Affected Software

Name	Vendor	Start Version	End Version
Libxpm	X.org	*	3.5.17 (excluding)
Red Hat Enterprise Linux 8	RedHat	libXpm-0:3.5.12-11.el8	*
Red Hat Enterprise Linux 8	RedHat	motif-0:2.3.4-20.el8	*
Red Hat Enterprise Linux 9	RedHat	libXpm-0:3.5.13-10.el9	*
Red Hat Enterprise Linux 9	RedHat	motif-0:2.3.4-28.el9	*
Libxpm	Ubuntu	bionic	*
Libxpm	Ubuntu	devel	*
Libxpm	Ubuntu	esm-infra-legacy/trusty	*
Libxpm	Ubuntu	esm-infra/bionic	*
Libxpm	Ubuntu	esm-infra/focal	*
Libxpm	Ubuntu	esm-infra/xenial	*
Libxpm	Ubuntu	focal	*
Libxpm	Ubuntu	jammy	*
Libxpm	Ubuntu	lunar	*
Libxpm	Ubuntu	mantic	*
Libxpm	Ubuntu	noble	*
Libxpm	Ubuntu	oracular	*
Libxpm	Ubuntu	plucky	*
Libxpm	Ubuntu	trusty	*
Libxpm	Ubuntu	trusty/esm	*
Libxpm	Ubuntu	upstream	*
Libxpm	Ubuntu	xenial	*
Motif	Ubuntu	bionic	*
Motif	Ubuntu	focal	*
Motif	Ubuntu	lunar	*
Motif	Ubuntu	mantic	*
Motif	Ubuntu	oracular	*
Motif	Ubuntu	trusty	*
Motif	Ubuntu	trusty/esm	*
Motif	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-2023-43788
CWE	https://cwe.mitre.org/data/definitions/125.html

Out-of-bounds Read

Weakness

Affected Software

Potential Mitigations

References

CVE-2023-43788

Out-of-bounds Read

Weakness

Affected Software

Potential Mitigations

Related Attack Patterns

References