# ALBA-2020:1713: gcc-toolset-9-binutils bug fix and enhancement update

> An assembler workaround mitigates Intel JCC bug performance loss, requiring recompilation with specific flags to avoid incorrect instruction execution.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Apr 2020

## What is ALBA-2020:1713?

ALBA-2020:1713 is a vulnerability in gcc-toolset-9-binutils, published on 28 Apr 2020. 

### 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.

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.

Bug Fix(es):

* Certain Intel CPUs are affected by the Jump Conditional Code (JCC) bug causing machine instructions to be executed incorrectly. Consequently, the affected CPUs might not execute programs properly. The full fix involves updating the microcode of vulnerable CPUs, which can cause a performance degradation. This update enables a workaround in the assembler that helps to mitigate the performance loss. The workaround is not enabled by default.

To apply the workaround, recompile a program using GCC with the "-Wa,-mbranches-within-32B-boundaries" command-line option. A program recompiled with this command-line option will not be affected by JCC flaw, but the microcode update is still necessary in order to fully protect a system. 

Note that applying the workaround will increase the size of the program and there can still be a slight performance decrease, although it should be less than it would have been without the recompilation. (BZ#1779417)

## Which versions are affected by ALBA-2020:1713?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gcc-toolset-9-binutils` | AlmaLinux:8 | All versions | 2.32-17.el8_1 |
| `gcc-toolset-9-binutils-devel` | AlmaLinux:8 | All versions | 2.32-17.el8_1 |

## How do I fix ALBA-2020:1713?

Apply the vendor's patch.

## Is ALBA-2020:1713 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALBA-2020:1713 is a vulnerability in gcc-toolset-9-binutils, published on 28 Apr 2020. 
Exploitation: There is no known exploitation of ALBA-2020:1713 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/ALBA-2020:1713

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