CVE-2018-1124

procps-ng before version 3.3.15 is vulnerable to multiple integer overflows leading to a heap corruption in file2strvec function. This allows a privilege escalation for a local attacker who can create entries in procfs by starting processes, which could result in crashes or arbitrary code execution in proc utilities run by other users.

Weakness

A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().

Affected Software

Name	Vendor	Start Version	End Version
Procps-ng	Procps-ng_project	*	3.3.15 (excluding)
Red Hat Enterprise Linux 6	RedHat	procps-0:3.2.8-45.el6_9.3	*
Red Hat Enterprise Linux 6.6 Advanced Update Support	RedHat	procps-0:3.2.8-30.el6_6.1	*
Red Hat Enterprise Linux 6.6 Telco Extended Update Support	RedHat	procps-0:3.2.8-30.el6_6.1	*
Red Hat Enterprise Linux 6.7 Extended Update Support	RedHat	procps-0:3.2.8-35.el6_7.1	*
Red Hat Enterprise Linux 7	RedHat	procps-ng-0:3.3.10-17.el7_5.2	*
Red Hat Enterprise Linux 7.3 Advanced Update Support	RedHat	procps-ng-0:3.3.10-10.el7_3.1	*
Red Hat Enterprise Linux 7.3 Telco Extended Update Support	RedHat	procps-ng-0:3.3.10-10.el7_3.1	*
Red Hat Enterprise Linux 7.3 Update Services for SAP Solutions	RedHat	procps-ng-0:3.3.10-10.el7_3.1	*
Red Hat Enterprise Linux 7.4 Extended Update Support	RedHat	procps-ng-0:3.3.10-16.el7_4.1	*
Red Hat Virtualization 4 for Red Hat Enterprise Linux 7	RedHat	imgbased-0:1.0.17-0.1.el7ev	*
Red Hat Virtualization 4 for Red Hat Enterprise Linux 7	RedHat	redhat-release-virtualization-host-0:4.2-3.1.el7	*
Red Hat Virtualization 4 for Red Hat Enterprise Linux 7	RedHat	redhat-virtualization-host-0:4.2-20180531.0	*
Procps	Ubuntu	artful	*
Procps	Ubuntu	bionic	*
Procps	Ubuntu	devel	*
Procps	Ubuntu	trusty	*
Procps	Ubuntu	upstream	*
Procps	Ubuntu	xenial	*

Potential Mitigations

Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking.
D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
Run or compile the software using features or extensions that randomly arrange the positions of a program’s executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code.
Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as “rebasing” (for Windows) and “prelinking” (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking.
For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].

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

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

Heap-based Buffer Overflow

Weakness

Affected Software

Potential Mitigations

References

CVE-2018-1124

Heap-based Buffer Overflow

Weakness

Affected Software

Potential Mitigations

Related Attack Patterns

References