# openSUSE-SU-2021:0269-1: Security update for java-11-openjdk

> Security update for Java 11 OpenJDK addressing January 2021 CPU issues and enabling Sheandoah GC on x86_64.

- **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:** 10 Feb 2021

## What is openSUSE-SU-2021:0269-1?

openSUSE-SU-2021:0269-1 is a vulnerability in java-11-openjdk, published on 10 Feb 2021. 

### Official description

This update for java-11-openjdk fixes the following issues:

java-11-openjdk was upgraded to include January 2021 CPU  (bsc#1181239)
- Enable Sheandoah GC for x86_64 (jsc#ECO-3171)

This update was imported from the SUSE:SLE-15:Update update project.

## Which versions are affected by openSUSE-SU-2021:0269-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `java-11-openjdk` | openSUSE:Leap 15.2 | All versions | 11.0.10.0-lp152.2.9.1 |

## How do I fix openSUSE-SU-2021:0269-1?

Upgrade to a fixed version.

## Is openSUSE-SU-2021:0269-1 being exploited?

There is no known exploitation of openSUSE-SU-2021:0269-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for openSUSE-SU-2021:0269-1 and fix it if it is affected.

What it is: openSUSE-SU-2021:0269-1 is a vulnerability in java-11-openjdk, published on 10 Feb 2021. 
Exploitation: There is no known exploitation of openSUSE-SU-2021:0269-1 in the wild and no public exploit code.

Affected product: java-11-openjdk. 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/openSUSE-SU-2021-0269-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2021-0269-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/openSUSE-SU-2021:0269-1

---
From sbomify Insights: https://insights.sbomify.com/openSUSE-SU-2021-0269-1/
Summaries are generated and may contain mistakes; the official description above is the record.