# SUSE-SU-2022:4639-1: Security update for polkit-default-privs

> This update addresses issues in polkit-default-privs by backporting USBGuard actions, requiring system administrators to apply the patch.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 30 Dec 2022

## What is SUSE-SU-2022:4639-1?

SUSE-SU-2022:4639-1 is a vulnerability in polkit-default-privs, published on 30 Dec 2022. 

### Official description

This update for polkit-default-privs fixes the following issues:

Update to version 13.2+20221216.a0c29e6:

- backport usbguard actions (bsc#1206414).

## Which versions are affected by SUSE-SU-2022:4639-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `polkit-default-privs` | SUSE:Linux Enterprise Module for Basesystem 15 SP4 | All versions | 13.2+20221216.a0c29e6-150400.3.3.1 |
| `polkit-default-privs` | openSUSE:Leap 15.4 | All versions | 13.2+20221216.a0c29e6-150400.3.3.1 |

## How do I fix SUSE-SU-2022:4639-1?

Apply the vendor's patch.

## Is SUSE-SU-2022:4639-1 being exploited?

There is no known exploitation of SUSE-SU-2022:4639-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for SUSE-SU-2022:4639-1 and fix it if it is affected.

What it is: SUSE-SU-2022:4639-1 is a vulnerability in polkit-default-privs, published on 30 Dec 2022. 
Exploitation: There is no known exploitation of SUSE-SU-2022:4639-1 in the wild and no public exploit code.

Affected product: polkit-default-privs. 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/SUSE-SU-2022-4639-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2022-4639-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2022:4639-1

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