USN-5313-2

Vulnerability from osv_ubuntu – Published: 2022-03-29 10:06 – Updated: 2026-02-10 04:42 – Source website
VLAI
Summary
openjdk-lts regression
Details

USN-5313-1 fixed vulnerabilities and added features in OpenJDK. Unfortunately, that update introduced a regression in OpenJDK 11 that could impact interoperability with some popular HTTP/2 servers making it unable to connect to said servers. This update fixes the problem.

We apologize for the inconvenience.

Original advisory details:

It was discovered that OpenJDK incorrectly handled deserialization filters. An attacker could possibly use this issue to insert, delete or obtain sensitive information. (CVE-2022-21248)

It was discovered that OpenJDK incorrectly read uncompressed TIFF files. An attacker could possibly use this issue to cause a denial of service via a specially crafted TIFF file. (CVE-2022-21277)

Jonni Passki discovered that OpenJDK incorrectly verified access restrictions when performing URI resolution. An attacker could possibly use this issue to obtain sensitive information. (CVE-2022-21282)

It was discovered that OpenJDK incorrectly handled certain regular expressions in the Pattern class implementation. An attacker could possibly use this issue to cause a denial of service. (CVE-2022-21283)

It was discovered that OpenJDK incorrectly handled specially crafted Java class files. An attacker could possibly use this issue to cause a denial of service. (CVE-2022-21291)

Markus Loewe discovered that OpenJDK incorrectly validated attributes during object deserialization. An attacker could possibly use this issue to cause a denial of service. (CVE-2022-21293, CVE-2022-21294)

Dan Rabe discovered that OpenJDK incorrectly verified access permissions in the JAXP component. An attacker could possibly use this to specially craft an XML file to obtain sensitive information. (CVE-2022-21296)

It was discovered that OpenJDK incorrectly handled XML entities. An attacker could use this to specially craft an XML file that, when parsed, would possibly cause a denial of service. (CVE-2022-21299)

Zhiqiang Zang discovered that OpenJDK incorrectly handled array indexes. An attacker could possibly use this issue to obtain sensitive information. (CVE-2022-21305)

It was discovered that OpenJDK incorrectly read very long attributes values in JAR file manifests. An attacker could possibly use this to specially craft JAR file to cause a denial of service. (CVE-2022-21340)

It was discovered that OpenJDK incorrectly validated input from serialized streams. An attacker cold possibly use this issue to bypass sandbox restrictions. (CVE-2022-21341)

Fabian Meumertzheim discovered that OpenJDK incorrectly handled certain specially crafted BMP or TIFF files. An attacker could possibly use this to cause a denial of service. (CVE-2022-21360, CVE-2022-21366)

It was discovered that an integer overflow could be triggered in OpenJDK BMPImageReader class implementation. An attacker could possibly use this to specially craft a BMP file to cause a denial of service. (CVE-2022-21365)

Impacted products
Ecosystem Package Version
Ubuntu:18.04:LTS openjdk-lts
pkg:deb/ubuntu/openjdk-lts@11.0.14.1+1-0ubuntu1~18.04?arch=source&distro=bionic
Affected: < 11.0.14.1+1-0ubuntu1~18.04 (ecosystem)
9.0.4+12-2ubuntu49.0.4+12-4ubuntu110~46-4ubuntu110~46-5ubuntu110.0.1+10-1ubuntu210.0.1+10-3ubuntu110.0.2+13-1ubuntu0.18.04.110.0.2+13-1ubuntu0.18.04.210.0.2+13-1ubuntu0.18.04.310.0.2+13-1ubuntu0.18.04.4 and 13 more (see JSON)
Ubuntu:20.04:LTS openjdk-lts
pkg:deb/ubuntu/openjdk-lts@11.0.14.1+1-0ubuntu1~20.04?arch=source&distro=focal
Affected: < 11.0.14.1+1-0ubuntu1~20.04 (ecosystem)
11.0.5+10-0ubuntu111.0.5+10-2ubuntu111.0.6+10-1ubuntu111.0.6+10-2ubuntu211.0.7+9-1ubuntu111.0.7+10-2ubuntu111.0.7+10-3ubuntu111.0.8+10-0ubuntu1~20.0411.0.9+11-0ubuntu1~20.0411.0.9.1+1-0ubuntu1~20.04 and 4 more (see JSON)

{
  "affected": [
    {
      "database_specific": {
        "cves_map": {
          "cves": [],
          "ecosystem": "Ubuntu:18.04:LTS"
        }
      },
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "openjdk-11-demo",
            "binary_version": "11.0.14.1+1-0ubuntu1~18.04"
          },
          {
            "binary_name": "openjdk-11-jdk",
            "binary_version": "11.0.14.1+1-0ubuntu1~18.04"
          },
          {
            "binary_name": "openjdk-11-jdk-headless",
            "binary_version": "11.0.14.1+1-0ubuntu1~18.04"
          },
          {
            "binary_name": "openjdk-11-jre",
            "binary_version": "11.0.14.1+1-0ubuntu1~18.04"
          },
          {
            "binary_name": "openjdk-11-jre-headless",
            "binary_version": "11.0.14.1+1-0ubuntu1~18.04"
          },
          {
            "binary_name": "openjdk-11-jre-zero",
            "binary_version": "11.0.14.1+1-0ubuntu1~18.04"
          },
          {
            "binary_name": "openjdk-11-source",
            "binary_version": "11.0.14.1+1-0ubuntu1~18.04"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:18.04:LTS",
        "name": "openjdk-lts",
        "purl": "pkg:deb/ubuntu/openjdk-lts@11.0.14.1+1-0ubuntu1~18.04?arch=source\u0026distro=bionic"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "11.0.14.1+1-0ubuntu1~18.04"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "9.0.4+12-2ubuntu4",
        "9.0.4+12-4ubuntu1",
        "10~46-4ubuntu1",
        "10~46-5ubuntu1",
        "10.0.1+10-1ubuntu2",
        "10.0.1+10-3ubuntu1",
        "10.0.2+13-1ubuntu0.18.04.1",
        "10.0.2+13-1ubuntu0.18.04.2",
        "10.0.2+13-1ubuntu0.18.04.3",
        "10.0.2+13-1ubuntu0.18.04.4",
        "11.0.2+9-3ubuntu1~18.04.3",
        "11.0.3+7-1ubuntu2~18.04.1",
        "11.0.4+11-1ubuntu2~18.04.3",
        "11.0.5+10-0ubuntu1.1~18.04",
        "11.0.6+10-1ubuntu1~18.04.1",
        "11.0.7+10-2ubuntu2~18.04",
        "11.0.8+10-0ubuntu1~18.04.1",
        "11.0.9+11-0ubuntu1~18.04.1",
        "11.0.9.1+1-0ubuntu1~18.04",
        "11.0.10+9-0ubuntu1~18.04",
        "11.0.11+9-0ubuntu2~18.04",
        "11.0.13+8-0ubuntu1~18.04",
        "11.0.14+9-0ubuntu2~18.04"
      ]
    },
    {
      "database_specific": {
        "cves_map": {
          "cves": [],
          "ecosystem": "Ubuntu:20.04:LTS"
        }
      },
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "openjdk-11-demo",
            "binary_version": "11.0.14.1+1-0ubuntu1~20.04"
          },
          {
            "binary_name": "openjdk-11-jdk",
            "binary_version": "11.0.14.1+1-0ubuntu1~20.04"
          },
          {
            "binary_name": "openjdk-11-jdk-headless",
            "binary_version": "11.0.14.1+1-0ubuntu1~20.04"
          },
          {
            "binary_name": "openjdk-11-jre",
            "binary_version": "11.0.14.1+1-0ubuntu1~20.04"
          },
          {
            "binary_name": "openjdk-11-jre-headless",
            "binary_version": "11.0.14.1+1-0ubuntu1~20.04"
          },
          {
            "binary_name": "openjdk-11-jre-zero",
            "binary_version": "11.0.14.1+1-0ubuntu1~20.04"
          },
          {
            "binary_name": "openjdk-11-source",
            "binary_version": "11.0.14.1+1-0ubuntu1~20.04"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "openjdk-lts",
        "purl": "pkg:deb/ubuntu/openjdk-lts@11.0.14.1+1-0ubuntu1~20.04?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "11.0.14.1+1-0ubuntu1~20.04"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "11.0.5+10-0ubuntu1",
        "11.0.5+10-2ubuntu1",
        "11.0.6+10-1ubuntu1",
        "11.0.6+10-2ubuntu2",
        "11.0.7+9-1ubuntu1",
        "11.0.7+10-2ubuntu1",
        "11.0.7+10-3ubuntu1",
        "11.0.8+10-0ubuntu1~20.04",
        "11.0.9+11-0ubuntu1~20.04",
        "11.0.9.1+1-0ubuntu1~20.04",
        "11.0.10+9-0ubuntu1~20.04",
        "11.0.11+9-0ubuntu2~20.04",
        "11.0.13+8-0ubuntu1~20.04",
        "11.0.14+9-0ubuntu2~20.04"
      ]
    }
  ],
  "aliases": [],
  "details": "USN-5313-1 fixed vulnerabilities and added features in OpenJDK.\nUnfortunately, that update introduced a regression in OpenJDK 11 that\ncould impact interoperability with some popular HTTP/2 servers making\nit unable to connect to said servers. This update fixes the problem.\n\nWe apologize for the inconvenience.\n\nOriginal advisory details:\n\n It was discovered that OpenJDK incorrectly handled deserialization filters.\n An attacker could possibly use this issue to insert, delete or obtain\n sensitive information. (CVE-2022-21248)\n\n It was discovered that OpenJDK incorrectly read uncompressed TIFF files.\n An attacker could possibly use this issue to cause a denial of service via\n a specially crafted TIFF file. (CVE-2022-21277)\n\n Jonni Passki discovered that OpenJDK incorrectly verified access\n restrictions when performing URI resolution. An attacker could possibly\n use this issue to obtain sensitive information. (CVE-2022-21282)\n\n It was discovered that OpenJDK incorrectly handled certain regular\n expressions in the Pattern class implementation. An attacker could\n possibly use this issue to cause a denial of service. (CVE-2022-21283)\n\n It was discovered that OpenJDK incorrectly handled specially crafted Java\n class files. An attacker could possibly use this issue to cause a denial\n of service. (CVE-2022-21291)\n\n Markus Loewe discovered that OpenJDK incorrectly validated attributes\n during object deserialization. An attacker could possibly use this issue\n to cause a denial of service. (CVE-2022-21293, CVE-2022-21294)\n\n Dan Rabe discovered that OpenJDK incorrectly verified access permissions\n in the JAXP component. An attacker could possibly use this to specially\n craft an XML file to obtain sensitive information. (CVE-2022-21296)\n\n It was discovered that OpenJDK incorrectly handled XML entities. An\n attacker could use this to specially craft an XML file that, when parsed,\n would possibly cause a denial of service. (CVE-2022-21299)\n\n Zhiqiang Zang discovered that OpenJDK incorrectly handled array indexes.\n An attacker could possibly use this issue to obtain sensitive information.\n (CVE-2022-21305)\n\n It was discovered that OpenJDK incorrectly read very long attributes\n values in JAR file manifests. An attacker could possibly use this to\n specially craft JAR file to cause a denial of service. (CVE-2022-21340)\n\n It was discovered that OpenJDK incorrectly validated input from serialized\n streams. An attacker cold possibly use this issue to bypass sandbox\n restrictions. (CVE-2022-21341)\n\n Fabian Meumertzheim discovered that OpenJDK incorrectly handled certain\n specially crafted BMP or TIFF files. An attacker could possibly use this\n to cause a denial of service. (CVE-2022-21360, CVE-2022-21366)\n\n It was discovered that an integer overflow could be triggered in OpenJDK\n BMPImageReader class implementation. An attacker could possibly use this\n to specially craft a BMP file to cause a denial of service.\n (CVE-2022-21365)\n",
  "id": "USN-5313-2",
  "modified": "2026-02-10T04:42:30Z",
  "published": "2022-03-29T10:06:48Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-5313-2"
    },
    {
      "type": "REPORT",
      "url": "https://launchpad.net/bugs/1966338"
    }
  ],
  "related": [],
  "schema_version": "1.7.0",
  "summary": "openjdk-lts regression",
  "upstream": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.