# ALBA-2022:0351: tigervnc bug fix and enhancement update

> TigerVNC vncviewer has an endianness issue fixed in this update, affecting remote desktop display accuracy.

- **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:** 1 Feb 2022

## What is ALBA-2022:0351?

ALBA-2022:0351 is a vulnerability in tigervnc, published on 1 Feb 2022. 

### Official description

Virtual Network Computing (VNC) is a remote display system which allows
users to view a computing desktop environment not only on the machine where
it is running, but from anywhere on the Internet and from a wide variety of
machine architectures. TigerVNC is a suite of VNC servers and clients.

Bug Fix(es) and Enhancement(s):

* AlmaLinux8.5 Request to backport fix for endianness issue in TigerVNC
vncviewer (BZ#2029319)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tigervnc` | AlmaLinux:8 | All versions | 1.11.0-10.el8_5 |
| `tigervnc-icons` | AlmaLinux:8 | All versions | 1.11.0-10.el8_5 |
| `tigervnc-license` | AlmaLinux:8 | All versions | 1.11.0-10.el8_5 |
| `tigervnc-selinux` | AlmaLinux:8 | All versions | 1.11.0-10.el8_5 |
| `tigervnc-server` | AlmaLinux:8 | All versions | 1.11.0-10.el8_5 |
| `tigervnc-server-minimal` | AlmaLinux:8 | All versions | 1.11.0-10.el8_5 |
| `tigervnc-server-module` | AlmaLinux:8 | All versions | 1.11.0-10.el8_5 |

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

Apply the vendor's patch.

## Is ALBA-2022:0351 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALBA-2022:0351 is a vulnerability in tigervnc, published on 1 Feb 2022. 
Exploitation: There is no known exploitation of ALBA-2022:0351 in the wild and no public exploit code.

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

## Sources

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

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