BF Specification of CVE-2019-14814 Heap Overflow in Marvell wifi diver in Linux kernel up to excluding v5.3

../../../../BF/images/BFCVE/CVE-2019-14814(simple)-0.png
Missing verification of 'rate_ie->len' towards a upper limit leads to use of an inconsistent size for an object, allowing a pointer reposition over its bounds, which, when used in 'memcpy()' leads to a heap buffer overflow. If exploited, this can lead to denial of service – system crash; and possibly arbitrary code execution.

//generated// Missing Code (in ‘mwifiex_set_uap_rates()’) to Range Verify length (rate_ie->len > MWIFIEX_SUPPORTED_RATES) In Use in Codebase (drivers/net/wireless/marvell/mwifiex/uap_cmd.c#L268) Admin (Linux kernel of Wifi Driver) leads to Inconsistent Value (‘rate_ie->len’)

, which propagates to Wrong Size (in ‘memcpy(…, rate_ie + 1, rate_ie->len)’) Sequential Reposition (pointer) Heap Used Codebase (drivers/net/wireless/marvell/mwifiex/uap_cmd.c#L276) in Kernel (Linux kernel of Wifi Driver) that results in Overbound Pointer (‘rate_ie + 1’)

, which propagates to Overbound Pointer (in ‘ptr->offsets[entries] = gf_bs_read_u64(bs);’) Sequential Write (object) Huge Heap Used Third-Party (src/isomedia/box_code_base.c#L58) in Userland that results in Buffer Overflow

, which can be exploited toward ACE (everything could be lost) or DOS (availability loss) security failure.



vendor:product: linux:linux_kernel:*


Bug Report


Code with Bug


Code with Fix


NVD Entry

ClassDefinition
DVRData Verification (DVR) class – Data are verified (i.e., semantics check) or corrected (i.e., assign or remove) improperly.
MADMemory Addressing (MAD) class – The pointer to an object is initialized, dereferenced, repositioned, or reassigned to an improper memory address.
MUSMemory Use (MUS) class – An object is initialized, read, written, or cleared improperly.
OperationDefinition
VerifyVerify operation – Check data semantics (e.g., proper value/meaning) in order to accept (and possibly correct) or reject it.
RepositionReposition operation – Change the pointer to another position inside its object.
WriteWrite operation – Change the data value of an object in memory to another meaningful value.
Cause/ConsequenceDefinition
Code BugCode Bug type – An error in the implementation of an operation – proper operands over an improper operation. A first cause for the chain of weaknesses underlying a software security vulnerability. Must be fixed to resolve the vulnerability.
   Missing CodeMissing Code bug - The operation is entirely absent.
Data Error/FaultData Fault/Error type – The data of an object has harmed semantics or inconsistent or wrong value.
   Inconsistent ValueInconsistent Value fault/error – The data value does not correspond to related data value (e.g., inconstancy between the value of a size variable and the actual buffer size).
   Wrong SizeWrong Size fault/error – The value used as size or length (i.e., the number of elements) does not match an object's memory size or length (e.g., to limit a pointer reposition or index increment/decrement in a repetition statement).
Address Error/FaultAddress Fault/Error type – The address of an object is wrong.
   Overbound PointerOverbound Pointer fault/error – Holds an address that is above the upper boundary of its object.
Memory Corruption/Disclosure Final ErrorMemory Corruption/Disclosure final error type – An exploitable or undefined system behavior caused by memory addressing, allocation, use, or deallocation bugs.
   Buffer OverflowBuffer Overflow final error – Write data above the upper bound of an object (i.e., buffer overwrite).
Operation AttributeDefinition
MechanismMechanism operation attribute type – Shows how the operation the operation with a bug or faulty operand is performed.
   RangeRange operation attribute – The operation checks data are within a (min, max) interval.
   SequentialSequential operation attribute – The operation is via iterating over the object elements.
Source CodeSource Code operation attribute type – Shows where the code of the operation with a bug or faulty operand resides within the software, firmware, or hardware.
   CodebaseCodebase operation attribute – The operation is in the programmer's code - in the application itself.
   Third-PartyThird-Party operation attribute – The operation code is in a third-party source.
Execution SpaceExecution Space operation attribute type – Shows where the operation with a bug or faulty operand is executed and the privilege level at which it runs.
   AdminAdmin operation attribute – The bugged code runs in an environment with access control policy with unlimited (admin user) permission.
   KernelKernel operation attribute – The bugged code runs in an environment with privilege levels with access privileged instructions (e.g., ring 0 in x86 architecture).
   UserlandUserland operation attribute – The bugged code runs in an environment with privilege levels, but in unprivileged mode (e.g., ring 3 in x86 architecture).
Operand AttributeDefinition
Data StateData State operand attribute type – Shows where the data comes from.
   In UseIn Use operand attribute – Data are from a volatile storage (e.g., RAM, cache memory).
Address StateAddress State operand attribute type – Shows where the address is (i.e., its location) in the memory layout.
   Heap
Size KindSize Kind operand attribute type – Shows what is used as the size or length (i.e., the number of elements) of an object - e.g., as the limit for traversal over the elements.
   UsedUsed operand attribute – A supplied value to be used as the size or length (i.e., the number of elements) of an object.
Address KindAddress Kind operand attribute type - Shows how much memory is accessed (i.e., the span) outside the bounds of an object.
   Huge