# ALBA-2022:0887: java-11-openjdk bug fix and enhancement update > This update fixes regressions in HTTP/2 header handling and LDAP authentication behavior in OpenJDK 11. - **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:** 15 Mar 2022 ## What is ALBA-2022:0887? ALBA-2022:0887 is a vulnerability in java-11-openjdk, published on 15 Mar 2022. ### Official description The java-11-openjdk packages provide the OpenJDK 11 Java Runtime Environment and the OpenJDK 11 Java Software Development Kit. Bug Fix(es): * The previous OpenJDK 11 release, 11.0.14, was found to contain a regression introduced by improvements to the HTTP client. It caused both the :authority' and 'Host' header fields to be sent in HTTP/2 requests, which is rejected by some HTTP servers, such as Google's. With this update, the previous behaviour of only setting the ':authority' header is now used. (RH#2053174) * Recent changes to the Lightweight Directory Access Protocol (LDAP) implementation in OpenJDK changed the behaviour when an authentication failure occurred. Instead of aborting immediately, all available LDAP servers would be tried with the same credentials. With this update, the previous behaviour of failure after the first authentication denial is restored. (RH#2055344) ## Which versions are affected by ALBA-2022:0887? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `java-11-openjdk` | AlmaLinux:8 | All versions | 1:11.0.14.1.1-2.el8_5 | | `java-11-openjdk-demo` | AlmaLinux:8 | All versions | 1:11.0.14.1.1-2.el8_5 | | `java-11-openjdk-demo-fastdebug` | AlmaLinux:8 | All versions | 1:11.0.14.1.1-2.el8_5 | | `java-11-openjdk-demo-slowdebug` | AlmaLinux:8 | All versions | 1:11.0.14.1.1-2.el8_5 | | `java-11-openjdk-devel` | AlmaLinux:8 | All versions | 1:11.0.14.1.1-2.el8_5 | | `java-11-openjdk-devel-fastdebug` | AlmaLinux:8 | All versions | 1:11.0.14.1.1-2.el8_5 | | `java-11-openjdk-devel-slowdebug` | AlmaLinux:8 | All versions | 1:11.0.14.1.1-2.el8_5 | | `java-11-openjdk-fastdebug` | AlmaLinux:8 | All versions | 1:11.0.14.1.1-2.el8_5 | | `java-11-openjdk-headless` | AlmaLinux:8 | All versions | 1:11.0.14.1.1-2.el8_5 | | `java-11-openjdk-headless-fastdebug` | AlmaLinux:8 | All versions | 1:11.0.14.1.1-2.el8_5 | | `java-11-openjdk-headless-slowdebug` | AlmaLinux:8 | All versions | 1:11.0.14.1.1-2.el8_5 | | `java-11-openjdk-javadoc` | AlmaLinux:8 | All versions | 1:11.0.14.1.1-2.el8_5 | | `java-11-openjdk-javadoc-zip` | AlmaLinux:8 | All versions | 1:11.0.14.1.1-2.el8_5 | | `java-11-openjdk-jmods` | AlmaLinux:8 | All versions | 1:11.0.14.1.1-2.el8_5 | | `java-11-openjdk-jmods-fastdebug` | AlmaLinux:8 | All versions | 1:11.0.14.1.1-2.el8_5 | | `java-11-openjdk-jmods-slowdebug` | AlmaLinux:8 | All versions | 1:11.0.14.1.1-2.el8_5 | | `java-11-openjdk-slowdebug` | AlmaLinux:8 | All versions | 1:11.0.14.1.1-2.el8_5 | | `java-11-openjdk-src` | AlmaLinux:8 | All versions | 1:11.0.14.1.1-2.el8_5 | | `java-11-openjdk-src-fastdebug` | AlmaLinux:8 | All versions | 1:11.0.14.1.1-2.el8_5 | | `java-11-openjdk-src-slowdebug` | AlmaLinux:8 | All versions | 1:11.0.14.1.1-2.el8_5 | | `java-11-openjdk-static-libs` | AlmaLinux:8 | All versions | 1:11.0.14.1.1-2.el8_5 | | `java-11-openjdk-static-libs-fastdebug` | AlmaLinux:8 | All versions | 1:11.0.14.1.1-2.el8_5 | | `java-11-openjdk-static-libs-slowdebug` | AlmaLinux:8 | All versions | 1:11.0.14.1.1-2.el8_5 | ## How do I fix ALBA-2022:0887? Upgrade to a fixed version. ## Is ALBA-2022:0887 being exploited? There is no known exploitation of ALBA-2022:0887 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for ALBA-2022:0887 and fix it if it is affected. What it is: ALBA-2022:0887 is a vulnerability in java-11-openjdk, published on 15 Mar 2022. Exploitation: There is no known exploitation of ALBA-2022:0887 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/ALBA-2022-0887/ (Markdown: https://insights.sbomify.com/ALBA-2022-0887/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/ALBA-2022:0887 --- From sbomify Insights: https://insights.sbomify.com/ALBA-2022-0887/ Summaries are generated and may contain mistakes; the official description above is the record.