UBUNTU-CVE-2022-1473 (CVE-2022-1473)
Vulnerability from osv_ubuntu – Published: 2022-05-03 00:00 – Updated: 2026-10-05 15:53 – Source websiteThe OPENSSL_LH_flush() function, which empties a hash table, contains a bug that breaks reuse of the memory occuppied by the removed hash table entries. This function is used when decoding certificates or keys. If a long lived process periodically decodes certificates or keys its memory usage will expand without bounds and the process might be terminated by the operating system causing a denial of service. Also traversing the empty hash table entries will take increasingly more time. Typically such long lived processes might be TLS clients or TLS servers configured to accept client certificate authentication. The function was added in the OpenSSL 3.0 version thus older releases are not affected by the issue. Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2).
{
"affected": [
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "libssl1.0.0",
"binary_version": "1.0.2g-1ubuntu4.20+esm3"
},
{
"binary_name": "openssl",
"binary_version": "1.0.2g-1ubuntu4.20+esm3"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "openssl",
"purl": "pkg:deb/ubuntu/openssl@1.0.2g-1ubuntu4.20+esm3?arch=source\u0026distro=esm-infra/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.0.2g-1ubuntu4.20+esm3"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.0.2d-0ubuntu1",
"1.0.2d-0ubuntu2",
"1.0.2e-1ubuntu1",
"1.0.2f-2ubuntu1",
"1.0.2g-1ubuntu2",
"1.0.2g-1ubuntu3",
"1.0.2g-1ubuntu4",
"1.0.2g-1ubuntu4.1",
"1.0.2g-1ubuntu4.2",
"1.0.2g-1ubuntu4.4",
"1.0.2g-1ubuntu4.5",
"1.0.2g-1ubuntu4.6",
"1.0.2g-1ubuntu4.8",
"1.0.2g-1ubuntu4.9",
"1.0.2g-1ubuntu4.10",
"1.0.2g-1ubuntu4.11",
"1.0.2g-1ubuntu4.12",
"1.0.2g-1ubuntu4.13",
"1.0.2g-1ubuntu4.14",
"1.0.2g-1ubuntu4.15",
"1.0.2g-1ubuntu4.16",
"1.0.2g-1ubuntu4.17",
"1.0.2g-1ubuntu4.18",
"1.0.2g-1ubuntu4.19",
"1.0.2g-1ubuntu4.20",
"1.0.2g-1ubuntu4.20+esm1",
"1.0.2g-1ubuntu4.20+esm2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "ovmf",
"binary_version": "0~20160408.ffea0a2c-2ubuntu0.2+esm4"
},
{
"binary_name": "qemu-efi",
"binary_version": "0~20160408.ffea0a2c-2ubuntu0.2+esm4"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "edk2",
"purl": "pkg:deb/ubuntu/edk2@0~20160408.ffea0a2c-2ubuntu0.2+esm4?arch=source\u0026distro=esm-apps-legacy/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0~20150106.5c2d456b-2",
"0~20160104.c2a892d7-1",
"0~20160408.ffea0a2c-2",
"0~20160408.ffea0a2c-2ubuntu0.1",
"0~20160408.ffea0a2c-2ubuntu0.2",
"0~20160408.ffea0a2c-2ubuntu0.2+esm1",
"0~20160408.ffea0a2c-2ubuntu0.2+esm3",
"0~20160408.ffea0a2c-2ubuntu0.2+esm4"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "libssl1.0.0",
"binary_version": "1.0.2g-1ubuntu4.fips.4.20.3"
},
{
"binary_name": "libssl1.0.0-hmac",
"binary_version": "1.0.2g-1ubuntu4.fips.4.20.3"
},
{
"binary_name": "openssl",
"binary_version": "1.0.2g-1ubuntu4.fips.4.20.3"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:16.04:LTS",
"name": "openssl",
"purl": "pkg:deb/ubuntu/openssl@1.0.2g-1ubuntu4.fips.4.20.3?arch=source\u0026distro=fips-updates/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.0.2g-1ubuntu4.fips.4.20.3"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.0.2g-1ubuntu4.fips.4.9.1",
"1.0.2g-1ubuntu4.fips.4.13.1",
"1.0.2g-1ubuntu4.fips.4.15.1",
"1.0.2g-1ubuntu4.fips.4.16.1",
"1.0.2g-1ubuntu4.fips.4.17.1",
"1.0.2g-1ubuntu4.fips.4.18.1",
"1.0.2g-1ubuntu4.fips.4.19.3",
"1.0.2g-1ubuntu4.fips.4.20.1",
"1.0.2g-1ubuntu4.fips.4.20.2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libssl1.0.0",
"binary_version": "1.0.2g-1ubuntu4.fips.4.6.3"
},
{
"binary_name": "libssl1.0.0-hmac",
"binary_version": "1.0.2g-1ubuntu4.fips.4.6.3"
},
{
"binary_name": "openssl",
"binary_version": "1.0.2g-1ubuntu4.fips.4.6.3"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS:16.04:LTS",
"name": "openssl",
"purl": "pkg:deb/ubuntu/openssl@1.0.2g-1ubuntu4.fips.4.6.3?arch=source\u0026distro=fips/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.0.2g-1ubuntu4.fips.4.6~ppa1",
"1.0.2g-1ubuntu4.fips.4.6~ppa2",
"1.0.2g-1ubuntu4.fips.4.6~ppa3",
"1.0.2g-1ubuntu4.fips.4.6",
"1.0.2g-1ubuntu4.fips.4.6.1",
"1.0.2g-1ubuntu4.fips.4.6.2",
"1.0.2g-1ubuntu4.fips.4.6.3"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "libssl3",
"binary_version": "3.0.2-0ubuntu1.1"
},
{
"binary_name": "openssl",
"binary_version": "3.0.2-0ubuntu1.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "openssl",
"purl": "pkg:deb/ubuntu/openssl@3.0.2-0ubuntu1.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.0.2-0ubuntu1.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.1.1l-1ubuntu1",
"3.0.0-1ubuntu1",
"3.0.1-0ubuntu1",
"3.0.2-0ubuntu1"
]
}
],
"aliases": [],
"details": "The OPENSSL_LH_flush() function, which empties a hash table, contains a bug that breaks reuse of the memory occuppied by the removed hash table entries. This function is used when decoding certificates or keys. If a long lived process periodically decodes certificates or keys its memory usage will expand without bounds and the process might be terminated by the operating system causing a denial of service. Also traversing the empty hash table entries will take increasingly more time. Typically such long lived processes might be TLS clients or TLS servers configured to accept client certificate authentication. The function was added in the OpenSSL 3.0 version thus older releases are not affected by the issue. Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2).",
"id": "UBUNTU-CVE-2022-1473",
"modified": "2026-10-05T15:53:07Z",
"published": "2022-05-03T00:00:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2022-1473"
},
{
"type": "REPORT",
"url": "https://mta.openssl.org/pipermail/openssl-announce/2022-May/000224.html"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-5402-1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-5402-2"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2022-1473"
}
],
"related": [
"USN-5402-1",
"USN-5402-2"
],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
},
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
},
{
"score": "low",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2022-1473"
]
}
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.
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
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.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
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.