CVE-2022-20546: Integer Overflow in getCurrentConfigImpl in android.hardware.audio.effect@7.0-impl

platform/hardware/interfaces Updated 02 Oct 2025

Summary

01/12/2022
Yes i
Moderate
Not published

CVE-2022-20546: In getCurrentConfigImpl of Effect.cpp, there is a possible out of bounds write due to a missing bounds check. Affects platform/hardware/interfaces versions >= 13:0, < 13:2022-12-01. Fixed in 13:2022-12-01. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The android.hardware.audio.effect@7.0-impl package is a component of the Android operating system that provides audio effect functionality. It is responsible for applying various audio effects to enhance the audio experience on Android devices. This package is vulnerable to an integer overflow issue in the getCurrentConfigImpl function of the Effect.cpp file. This vulnerability can potentially allow an attacker to escalate privileges locally, requiring system execution privileges. Exploitation does not require user interaction.

Vulnerability Detail

The getCurrentConfigImpl function in Effect.cpp lacks proper bounds checking, leading to a possible out-of-bounds write. This vulnerability can be exploited to achieve local privilege escalation, potentially allowing an attacker to execute arbitrary code with system-level privileges. The impact of this vulnerability is significant as it can bypass security measures and gain unauthorized access to sensitive resources. The vulnerability was introduced in version 13 of the package and has been fixed in version 13 released on December 1, 2022.

How To Fix

Minimum fixed version

13:2022-12-01

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

There is no known workaround for this vulnerability. It is recommended to apply the official fix by updating the affected package to a secure version.

Conclusion

The android.hardware.audio.effect@7.0-impl package is vulnerable to an integer overflow issue in the getCurrentConfigImpl function. This vulnerability can be exploited to achieve local privilege escalation, allowing an attacker to execute arbitrary code with system-level privileges. It is crucial to update the affected package to version 13 or later to mitigate the risk of exploitation.

See every vulnerability recorded for platform/hardware/interfaces →

Share this vulnerability

FAQ

This vulnerability can allow an attacker to escalate privileges locally, potentially leading to unauthorized access to sensitive resources and the execution of arbitrary code with system-level privileges.

No, user interaction is not needed for exploitation of this vulnerability.

Versions 13 of the android.hardware.audio.effect@7.0-impl package are affected by this vulnerability.

Yes, the vulnerability has been fixed in version 13 of the package released on December 1, 2022.

More information about the fix can be found in the source code commit: [link to commit].

Related vulnerabilities

Recent vulnerabilities recorded for platform/hardware/interfaces.

How To Fix

Minimum fixed version

13:2022-12-01

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