CVE-2022-20109: ion Package Local Escalation of Privilege Due to Use After Free

:unknown: Updated 02 Oct 2025

Summary

01/05/2022
Yes i
High
Not published

CVE-2022-20109: In ion, there is a possible use after free due to improper update of reference count. Affects :unknown: versions >= SoCVersion:0, < SoCVersion:2022-05-05. Fixed in SoCVersion:2022-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 ion package is a memory management subsystem in the Android operating system that provides a mechanism for allocating and sharing memory buffers between different processes. It is designed to optimize memory usage and improve performance in mobile applications. However, the ion package has been found to have a vulnerability that can lead to local escalation of privilege, allowing unauthorized access to system resources.

Vulnerability Detail

In the ion package, there exists a use after free vulnerability caused by improper updates to the reference count of memory buffers. This flaw can be exploited by an attacker to gain elevated privileges on the device without requiring any additional execution privileges. The exploitation of this vulnerability can lead to unauthorized access to sensitive data or system resources, posing a significant security risk.

How To Fix

Minimum fixed version

SoCVersion:2022-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 available to mitigate this vulnerability other than applying the patch. Users are advised to update to the fixed version as soon as it becomes available.

Conclusion

The ion package vulnerability CVE-2022-20109 poses a significant risk of local escalation of privilege due to a use after free error. It is essential for users to update to the patched version to safeguard their devices from potential exploitation. Regular monitoring and updates are crucial for maintaining security.

See every vulnerability recorded for :unknown: →

Share this vulnerability

FAQ

CVE-2022-20109 is a vulnerability in the ion package of the Android operating system that allows for local escalation of privilege due to a use after free error.

An attacker can exploit this vulnerability by manipulating the reference count of memory buffers, allowing them to gain unauthorized access to system resources.

No, user interaction is not needed for exploitation, making it particularly dangerous.

If you are using the ion package, it is crucial to update to the patched version released on 2022-05-05 to protect against this vulnerability.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By utilizing the Vulert playground, you can check if your application is affected without needing to sign up.

Related vulnerabilities

Recent vulnerabilities recorded for :unknown:.

How To Fix

Minimum fixed version

SoCVersion:2022-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