CVE-2022-46395: Unknown Package Memory Corruption Vulnerability

:unknown: Updated 02 Oct 2025

Summary

01/05/2023
Yes i
High
Not published

CVE-2022-46395: In tbd of tbd, there is a possible memory corruption due to a use after free. Affects :unknown: versions >= SoCVersion:0, < SoCVersion:2023-05-05. Fixed in SoCVersion:2023-05-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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The affected package is part of the Android ecosystem, which is widely used for mobile devices and applications. Android provides a rich application framework that allows developers to build innovative apps and games for mobile users. However, like any software, it is susceptible to vulnerabilities that can compromise the security and functionality of applications. This specific vulnerability relates to memory management, which is critical for maintaining application stability and security.

Vulnerability Detail

In the affected package, there is a potential memory corruption issue caused by a use after free condition. This vulnerability can lead to local escalation of privileges without requiring additional execution privileges. The exploitation of this vulnerability does not necessitate user interaction, making it particularly concerning. Attackers could exploit this flaw to gain unauthorized access to sensitive information or execute arbitrary code within the context of the application.

How To Fix

Minimum fixed version

SoCVersion:2023-05-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 mentioned for this vulnerability. The best course of action is to apply the patch as soon as it becomes available.

Conclusion

CVE-2022-46395 represents a significant security risk due to a memory corruption vulnerability in an unknown Android package. It is crucial for developers and users to update their applications to the patched version to protect against potential exploitation. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities in real-time.

See every vulnerability recorded for :unknown: →

Share this vulnerability

FAQ

CVE-2022-46395 is a vulnerability in an unknown package within the Android ecosystem that can lead to memory corruption due to a use after free condition.

Exploitation of this vulnerability can allow attackers to escalate privileges locally, potentially leading to unauthorized access to sensitive data or execution of malicious code.

No, user interaction is not needed for exploitation, which makes it more dangerous.

You should update the affected package to the patched version released on May 5, 2023, to mitigate the risk associated with this vulnerability.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application against this vulnerability using the Vulert playground at Vulert Scanner without needing to sign up.

Related vulnerabilities

Recent vulnerabilities recorded for :unknown:.

How To Fix

Minimum fixed version

SoCVersion:2023-05-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