7 matches found
CVE-2018-9427
In CopyToOMX of OMXNodeInstance.cpp there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to remote arbitrary code execution with no additional execution privileges needed. User interaction is needed for exploitation. Product: Android Versions: Android-8.0...
Out-of-bounds
In CopyToOMX of OMXNodeInstance.cpp there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to remote arbitrary code execution with no additional execution privileges needed. User interaction is needed for exploitation. Product: Android Versions: Android-8.0...
CVE-2018-9427
In CopyToOMX of OMXNodeInstance.cpp there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to remote arbitrary code execution with no additional execution privileges needed. User interaction is needed for exploitation. Product: Android Versions: Android-8.0...
CVE-2018-9427
In CopyToOMX of OMXNodeInstance.cpp there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to remote arbitrary code execution with no additional execution privileges needed. User interaction is needed for exploitation. Product: Android Versions: Android-8.0...
CVE-2018-9427
CVE-2018-9427 affects Android 8.0 and 8.1, tied to the Media framework. The issue is an out-of-bounds write in CopyToOMX of OMXNodeInstance.cpp caused by an incorrect bounds check, leading to remote code execution. Exploitation details in the provided sources indicate the impact is high (RCE) wit...
CVE-2018-9427: Out-of-bounds Write
In CopyToOMX of OMXNodeInstance.cpp there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to remote arbitrary code execution with no additional execution privileges needed. User interaction is needed for exploitation. Product: Android Versions: Android-8.0...
PT-2018-19005
Name of the Vulnerable Software and Affected Versions Android versions 8.0 through 8.1 Description The issue is related to an incorrect bounds check in the CopyToOMX function of OMXNodeInstance.cpp, which could lead to a possible out-of-bounds write. This might result in remote arbitrary code...