# CVE-2022-4964: Security feature bypass in Ubuntu pipewire-pulse

> Attackers can access the microphone via pipewire-pulse snap even when audio recording permissions are disabled, bypassing security controls.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Jan 2024
- **Updated:** 20 Jun 2025
- **Also known as:** DEBIAN-CVE-2022-4964, GHSA-p626-3xpc-x4f6, UBUNTU-CVE-2022-4964

## What is CVE-2022-4964?

CVE-2022-4964 is a medium-severity vulnerability in Canonical Ltd. Ubuntu pipewire-pulse, published on 24 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Ubuntu's pipewire-pulse in snap grants microphone access even when the snap interface for audio-record is not set.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2022-4964?

It affects 1 product.


Products: Canonical Ubuntu Pipewire-Pulse.

## How do I fix CVE-2022-4964?

Apply the vendor's patch.

## Is CVE-2022-4964 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4964 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-4964 and fix it if it is affected.

What it is: CVE-2022-4964 is a medium-severity vulnerability in Canonical Ltd. Ubuntu pipewire-pulse, published on 24 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4964 exists.

Affected product: Canonical Ltd. Ubuntu pipewire-pulse. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-4964/ (Markdown: https://insights.sbomify.com/CVE-2022-4964/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-4964
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-4964
- OSV: https://osv.dev/vulnerability/CVE-2022-4964

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-4964/
Summaries are generated and may contain mistakes; the official description above is the record.