CVE-2019-10126

A flaw was found in the Linux kernel. A heap based buffer overflow in mwifiex_uap_parse_tail_ies function in drivers/net/wireless/marvell/mwifiex/ie.c might lead to memory corruption and possibly other consequences.

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

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].

Related Attack Patterns

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

References

• http://lists.opensuse.org/opensuse-security-announce/2019-07/msg00014.html
• http://lists.opensuse.org/opensuse-security-announce/2019-07/msg00025.html
• http://packetstormsecurity.com/files/153702/Slackware-Security-Advisory-Slackware-14.2-kernel-Updates.html
• http://packetstormsecurity.com/files/154245/Kernel-Live-Patch-Security-Notice-LSN-0054-1.html
• http://packetstormsecurity.com/files/154951/Kernel-Live-Patch-Security-Notice-LSN-0058-1.html
• http://www.securityfocus.com/bid/108817
• https://access.redhat.com/errata/RHSA-2019:3055
• https://access.redhat.com/errata/RHSA-2019:3076
• https://access.redhat.com/errata/RHSA-2019:3089
• https://access.redhat.com/errata/RHSA-2019:3309
• https://access.redhat.com/errata/RHSA-2019:3517
• https://access.redhat.com/errata/RHSA-2020:0174
• https://access.redhat.com/errata/RHSA-2020:0204
• https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10126
• https://lists.debian.org/debian-lts-announce/2019/06/msg00010.html
• https://lists.debian.org/debian-lts-announce/2019/06/msg00011.html
• https://seclists.org/bugtraq/2019/Jul/33
• https://seclists.org/bugtraq/2019/Jun/26
• https://security.netapp.com/advisory/ntap-20190710-0002/
• https://support.f5.com/csp/article/K95593121
• https://usn.ubuntu.com/4093-1/
• https://usn.ubuntu.com/4094-1/
• https://usn.ubuntu.com/4095-1/
• https://usn.ubuntu.com/4095-2/
• https://usn.ubuntu.com/4117-1/
• https://usn.ubuntu.com/4118-1/
• https://www.debian.org/security/2019/dsa-4465