# ALBA-2020:5502: icedtea-web bug fix update

> The ALBA-2020 fix changed icedtea-web to use an alt-java binary instead of plain java, affecting AlmaLinux users.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** Yes
- **Published:** 15 Dec 2020

## What is ALBA-2020:5502?

ALBA-2020:5502 is an other vulnerability in icedtea-web, published on 15 Dec 2020. 

### Official description

Migrate icedtea-web to use alt-java special binary in our JDK8 packages instead of plain java.

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

An affected version is exposed as installed. No special setting or call is needed.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `icedtea-web` | AlmaLinux:8 | All versions | 1.7.1-18.el8_3 |

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

Upgrade to a fixed version.

## Is ALBA-2020:5502 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALBA-2020:5502 is an other vulnerability in icedtea-web, published on 15 Dec 2020. 
Exploitation: There is no known exploitation of ALBA-2020:5502 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: icedtea-web. 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-5502/ (Markdown: https://insights.sbomify.com/ALBA-2020-5502/index.md)
```

## Sources

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

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