# ALBA-2019:3439: new packages: gcc-toolset-9-dwz

> This is an enhancement update adding new packages to the GCC Toolset, not a security vulnerability fix.

- **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:** 5 Nov 2019

## What is ALBA-2019:3439?

ALBA-2019:3439 is a vulnerability in gcc-toolset-9-dwz, published on 5 Nov 2019. 

### Official description

GCC Toolset is a compiler toolset that provides recent versions of development tools. GCC Toolset is an Application Stream packaged as a Software Collection.

This enhancement update adds the gcc-toolset-9-dwz packages to AlmaLinux Eneterprise Linux 8.

For instructions on usage, see Using GCC Toolset linked from the References section. Components and specifics of this version are documented in the GCC Toolset 9 chapter. 

For detailed changes in this release, see the AlmaLinux Release Notes.

## Which versions are affected by ALBA-2019:3439?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gcc-toolset-9-dwz` | AlmaLinux:8 | All versions | 0.12-1.1.el8 |

## How do I fix ALBA-2019:3439?

Upgrade to a fixed version.

## Is ALBA-2019:3439 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALBA-2019:3439 is a vulnerability in gcc-toolset-9-dwz, published on 5 Nov 2019. 
Exploitation: There is no known exploitation of ALBA-2019:3439 in the wild and no public exploit code.

Affected product: gcc-toolset-9-dwz. 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-2019-3439/ (Markdown: https://insights.sbomify.com/ALBA-2019-3439/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/ALBA-2019:3439

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