# ALBA-2022:0363: gnome-control-center bug fix update

> A bug in the WiFi settings panel causes the GNOME control center to hang, resulting in a local denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 1 Feb 2022

## What is ALBA-2022:0363?

ALBA-2022:0363 is a denial of service vulnerability in gnome-control-center, published on 1 Feb 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The gnome-control-center package contains configuration utilities for the GNOME desktop, which allow to configure accessibility options, desktop fonts, keyboard and mouse properties, sound setup, desktop theme and background, user interface properties, screen resolution, and other settings.

Bug Fix:

* Wifi settings panel causes gnome-control-panel to hang (BZ#2024707)

## Which versions are affected by ALBA-2022:0363?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gnome-control-center` | AlmaLinux:8 | All versions | 3.28.2-29.el8_5 |
| `gnome-control-center-filesystem` | AlmaLinux:8 | All versions | 3.28.2-29.el8_5 |

## How do I fix ALBA-2022:0363?

Apply the vendor's patch.

## Is ALBA-2022:0363 being exploited?

There is no known exploitation of ALBA-2022:0363 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for ALBA-2022:0363 and fix it if it is affected.

What it is: ALBA-2022:0363 is a denial of service vulnerability in gnome-control-center, published on 1 Feb 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of ALBA-2022:0363 in the wild and no public exploit code.

Affected product: gnome-control-center. 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/ALBA-2022-0363/ (Markdown: https://insights.sbomify.com/ALBA-2022-0363/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/ALBA-2022:0363

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