CVE-2023-33913
First published: Mon Aug 07 2023(Updated: )
In DRM/oemcrypto, there is a possible out of bounds write due to an incorrect calculation of buffer size.This could lead to remote escalation of privilege with System execution privileges needed
Credit: security@unisoc.com security@unisoc.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Google Android | =11.0 | |
| Google Android | =12.0 | |
| unisoc s8000 | ||
| unisoc t606 | ||
| unisoc t610 | ||
| unisoc t612 | ||
| unisoc t616 | ||
| unisoc t618 | ||
| unisoc t760 | ||
| unisoc t770 | ||
| unisoc t820 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the vulnerability ID for this issue?
The vulnerability ID for this issue is CVE-2023-33913.
What is the severity of CVE-2023-33913?
The severity of CVE-2023-33913 is high with a severity value of 7.2.
What is the affected software?
The affected software includes Google Android versions 11.0 and 12.0.
Is Unisoc S8000 affected by CVE-2023-33913?
No, Unisoc S8000 is not vulnerable to CVE-2023-33913.
How can I fix CVE-2023-33913?
To fix CVE-2023-33913, it is recommended to apply the latest security patches and updates from Google for Android.
- agent/type
- agent/author
- agent/softwarecombine
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-api
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/severity
- agent/weakness
- agent/references
- agent/tags
- agent/event
- agent/first-publish-date
- agent/description
- agent/source
- vendor/google
- canonical/google android
- version/google android/11.0
- version/google android/12.0
- vendor/unisoc
- canonical/unisoc s8000
- canonical/unisoc t606
- canonical/unisoc t610
- canonical/unisoc t612
- canonical/unisoc t616
- canonical/unisoc t618
- canonical/unisoc t760
- canonical/unisoc t770
- canonical/unisoc t820