# ALEA-2020:3054: new module: eclipse:rhel8


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 21 Jul 2020

## What is ALEA-2020:3054?

ALEA-2020:3054 is a vulnerability in glassfish-annotation-api, published on 21 Jul 2020. 

### Official description

Eclipse is an integrated development environment (IDE).

This enhancement update adds the eclipse:rhel8 module to AlmaLinux The eclipse:rhel8 module provides Eclipse version 4.15, which is based on the Eclipse Foundation's 2020-03 release train. (BZ#1786637)

For detailed information on changes in this release, see the AlmaLinux Release Notes linked from the References section.

For instructions on how to use the Eclipse module, see Using Eclipse linked from the References section.

## Which versions are affected by ALEA-2020:3054?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `glassfish-annotation-api` | AlmaLinux:8 | All versions | 1.3.2-3.module_el8.3.0+2043+807b4491 |
| `icu4j` | AlmaLinux:8 | All versions | 1:65.1-3.module_el8.3.0+2043+807b4491 |

## How do I fix ALEA-2020:3054?

Upgrade to a fixed version.

## Is ALEA-2020:3054 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALEA-2020:3054 is a vulnerability in glassfish-annotation-api, published on 21 Jul 2020. 
Exploitation: There is no known exploitation of ALEA-2020:3054 in the wild and no public exploit code.

Affected product: glassfish-annotation-api. 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/ALEA-2020-3054/ (Markdown: https://insights.sbomify.com/ALEA-2020-3054/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/ALEA-2020:3054

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