CVE-2024-53838: Exynos_parsing_user_data_registered_itu_t_t35 Out of Bounds Write in VendorVideoAPI

:unknown: Updated 02 Oct 2025

Summary

01/12/2024
Yes i
Moderate
Not published

CVE-2024-53838: In Exynos_parsing_user_data_registered_itu_t_t35 of VendorVideoAPI.cpp, there is a possible out of bounds write due to an incorrect bounds check. Affects :unknown: versions >= Pixel-family specific:0, < Pixel-family specific:2024-12-05. Fixed in Pixel-family specific:2024-12-05. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The VendorVideoAPI is a component of the Android ecosystem that handles video processing and related functionalities. It is integral to the performance of multimedia applications on devices, particularly those in the Pixel family. This API is designed to manage various video formats and data streams, ensuring smooth playback and recording. However, it has been found to contain a vulnerability that could be exploited to escalate privileges locally.

Vulnerability Detail

In the function Exynos_parsing_user_data_registered_itu_t_t35 of VendorVideoAPI.cpp, there exists a flaw related to an incorrect bounds check, which can lead to an out of bounds write. This vulnerability allows an attacker to write data outside the intended memory boundaries, potentially leading to local escalation of privileges. The exploitation of this vulnerability does not require any additional execution privileges or user interaction, making it particularly concerning for device security.

How To Fix

Minimum fixed version

Pixel-family specific:2024-12-05

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

Currently, there are no specific workarounds available to mitigate this vulnerability other than applying the patch. Users are advised to keep their devices updated to minimize risks.

Conclusion

CVE-2024-53838 represents a significant security risk within the VendorVideoAPI due to an out of bounds write vulnerability. Users are strongly encouraged to update their devices to the latest version to mitigate this risk. Regular monitoring for vulnerabilities using tools like Vulert can help maintain device security.

See every vulnerability recorded for :unknown: →

Share this vulnerability

FAQ

CVE-2024-53838 is a vulnerability in the VendorVideoAPI that allows for an out of bounds write, potentially leading to local privilege escalation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If your device is affected, you should update to the patched version of the VendorVideoAPI, which is available in the system updates released on December 5, 2024.

No, user interaction is not required to exploit this vulnerability, making it more dangerous.

The potential consequences include unauthorized access to system privileges, which could allow attackers to execute malicious actions on the device.

Related vulnerabilities

Recent vulnerabilities recorded for :unknown:.

How To Fix

Minimum fixed version

Pixel-family specific:2024-12-05

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback