CVE-2018-18313

Perl before 5.26.3 has a buffer over-read via a crafted regular expression that triggers disclosure of sensitive information from process memory.

Weakness

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

Affected Software

Name	Vendor	Start Version	End Version
Perl	Perl	*	5.26.3 (excluding)
Red Hat Software Collections for Red Hat Enterprise Linux 6	RedHat	rh-perl524-perl-4:5.24.0-381.el6	*
Red Hat Software Collections for Red Hat Enterprise Linux 7	RedHat	rh-perl526-perl-4:5.26.3-405.el7	*
Red Hat Software Collections for Red Hat Enterprise Linux 7	RedHat	rh-perl526-perl-Module-CoreList-1:5.20181130-1.el7	*
Red Hat Software Collections for Red Hat Enterprise Linux 7	RedHat	rh-perl524-perl-4:5.24.0-381.el7	*
Red Hat Software Collections for Red Hat Enterprise Linux 7.4 EUS	RedHat	rh-perl526-perl-4:5.26.3-405.el7	*
Red Hat Software Collections for Red Hat Enterprise Linux 7.4 EUS	RedHat	rh-perl526-perl-Module-CoreList-1:5.20181130-1.el7	*
Red Hat Software Collections for Red Hat Enterprise Linux 7.4 EUS	RedHat	rh-perl524-perl-4:5.24.0-381.el7	*
Red Hat Software Collections for Red Hat Enterprise Linux 7.5 EUS	RedHat	rh-perl526-perl-4:5.26.3-405.el7	*
Red Hat Software Collections for Red Hat Enterprise Linux 7.5 EUS	RedHat	rh-perl526-perl-Module-CoreList-1:5.20181130-1.el7	*
Red Hat Software Collections for Red Hat Enterprise Linux 7.5 EUS	RedHat	rh-perl524-perl-4:5.24.0-381.el7	*
Red Hat Software Collections for Red Hat Enterprise Linux 7.6 EUS	RedHat	rh-perl526-perl-4:5.26.3-405.el7	*
Red Hat Software Collections for Red Hat Enterprise Linux 7.6 EUS	RedHat	rh-perl526-perl-Module-CoreList-1:5.20181130-1.el7	*
Red Hat Software Collections for Red Hat Enterprise Linux 7.6 EUS	RedHat	rh-perl524-perl-4:5.24.0-381.el7	*
Perl	Ubuntu	bionic	*
Perl	Ubuntu	cosmic	*
Perl	Ubuntu	devel	*
Perl	Ubuntu	esm-infra-legacy/trusty	*
Perl	Ubuntu	esm-infra/bionic	*
Perl	Ubuntu	esm-infra/xenial	*
Perl	Ubuntu	trusty	*
Perl	Ubuntu	trusty/esm	*
Perl	Ubuntu	upstream	*
Perl	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-18313
CWE	https://cwe.mitre.org/data/definitions/125.html

Out-of-bounds Read

Weakness

Affected Software

Potential Mitigations

References

CVE-2018-18313

Out-of-bounds Read

Weakness

Affected Software

Potential Mitigations

Related Attack Patterns

References