USN-5167-1 (UBUNTU-CVE-2020-20445)
Vulnerability from osv_ubuntu – Published: 2022-06-13 16:13 – Updated: 2026-06-25 10:46 – Source websiteIt was discovered that FFmpeg did not properly verify certain input when processing video and audio files. An attacker could possibly use this to send specially crafted input to the application, force a division by zero, and cause a denial of service (application crash). (CVE-2020-20445, CVE-2020-20446, CVE-2020-20453, CVE-2020-20892)
It was discovered that FFmpeg did not properly perform certain bit shift and memory operations. An attacker could possibly use this issue to expose sensitive information. (CVE-2020-20902)
It was discovered that FFmpeg did not properly perform memory management operations in various of its functions. An attacker could possibly use this issue to send specially crafted input to the application and cause a denial of service (application crash) or execute arbitrary code. (CVE-2020-21041, CVE-2020-20451, CVE-2020-21688, CVE-2020-21697, CVE-2020-22020, CVE-2020-22021, CVE-2020-22022, CVE-2020-22025, CVE-2020-22031, CVE-2020-22032, CVE-2020-22037, CVE-2020-22040, CVE-2020-22041, CVE-2020-22042, CVE-2020-22044)
It was discovered that FFmpeg did not properly perform memory management operations in various of its functions. An attacker could possibly use this issue to send specially crafted input to the application and cause a denial of service (application crash) or execute arbitrary code. (CVE-2020-22016, CVE-2020-22046, CVE-2020-22049, CVE-2020-22054)
It was discovered that FFmpeg did not properly perform memory management operations in various of its functions. An attacker could possibly use this issue to send specially crafted input to the application and cause a denial of service (application crash) or execute arbitrary code. (CVE-2020-35965)
It was discovered that FFmpeg did not properly handle data assigned to the tty demuxer. An attacker could possibly use this issue to send specially crafted input to the application and expose sensitive information. (CVE-2021-3566)
It was discovered that FFmpeg did not perform checks on function return values when encoding and formatting input video and audio files. An attacker could possibly use this issue to cause a denial of service (application crash) or execute arbitrary code. (CVE-2021-38114, CVE-2021-38171)
It was discovered that FFmpeg did not properly sanitize function returned data when calculating frame duration values. An attacker could possibly use this issue to cause an assertion failure and then cause a denial of service (application crash). (CVE-2021-38291)
{
"affected": [
{
"database_specific": {
"cves_map": {
"cves": [
{
"id": "CVE-2020-22054",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
]
},
{
"id": "CVE-2020-35965",
"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": "medium",
"type": "Ubuntu"
}
]
},
{
"id": "CVE-2021-3566",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
]
},
{
"id": "CVE-2021-38114",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
]
},
{
"id": "CVE-2021-38171",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
]
},
{
"id": "CVE-2021-38291",
"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": "medium",
"type": "Ubuntu"
}
]
}
],
"ecosystem": "Ubuntu:Pro:16.04:LTS"
}
},
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "ffmpeg",
"binary_version": "7:2.8.17-0ubuntu0.1+esm4"
},
{
"binary_name": "libav-tools",
"binary_version": "7:2.8.17-0ubuntu0.1+esm4"
},
{
"binary_name": "libavcodec-extra",
"binary_version": "7:2.8.17-0ubuntu0.1+esm4"
},
{
"binary_name": "libavcodec-ffmpeg-extra56",
"binary_version": "7:2.8.17-0ubuntu0.1+esm4"
},
{
"binary_name": "libavcodec-ffmpeg56",
"binary_version": "7:2.8.17-0ubuntu0.1+esm4"
},
{
"binary_name": "libavdevice-ffmpeg56",
"binary_version": "7:2.8.17-0ubuntu0.1+esm4"
},
{
"binary_name": "libavfilter-ffmpeg5",
"binary_version": "7:2.8.17-0ubuntu0.1+esm4"
},
{
"binary_name": "libavformat-ffmpeg56",
"binary_version": "7:2.8.17-0ubuntu0.1+esm4"
},
{
"binary_name": "libavresample-ffmpeg2",
"binary_version": "7:2.8.17-0ubuntu0.1+esm4"
},
{
"binary_name": "libavutil-ffmpeg54",
"binary_version": "7:2.8.17-0ubuntu0.1+esm4"
},
{
"binary_name": "libpostproc-ffmpeg53",
"binary_version": "7:2.8.17-0ubuntu0.1+esm4"
},
{
"binary_name": "libswresample-ffmpeg1",
"binary_version": "7:2.8.17-0ubuntu0.1+esm4"
},
{
"binary_name": "libswscale-ffmpeg3",
"binary_version": "7:2.8.17-0ubuntu0.1+esm4"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "ffmpeg",
"purl": "pkg:deb/ubuntu/ffmpeg@7:2.8.17-0ubuntu0.1+esm4?arch=source\u0026distro=esm-apps/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "7:2.8.17-0ubuntu0.1+esm4"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"7:2.7.2-1build1",
"7:2.8.1-1ubuntu1",
"7:2.8.2-1ubuntu1",
"7:2.8.3-1",
"7:2.8.4-1",
"7:2.8.4-1ubuntu1",
"7:2.8.4-1ubuntu2",
"7:2.8.4-1ubuntu3",
"7:2.8.4-1ubuntu4",
"7:2.8.6-1ubuntu1",
"7:2.8.6-1ubuntu2",
"7:2.8.8-0ubuntu0.16.04.1",
"7:2.8.10-0ubuntu0.16.04.1",
"7:2.8.11-0ubuntu0.16.04.1",
"7:2.8.14-0ubuntu0.16.04.1",
"7:2.8.15-0ubuntu0.16.04.1",
"7:2.8.15-0ubuntu0.16.04.1+esm1",
"7:2.8.17-0ubuntu0.1",
"7:2.8.17-0ubuntu0.1+esm1",
"7:2.8.17-0ubuntu0.1+esm2",
"7:2.8.17-0ubuntu0.1+esm3"
]
}
],
"aliases": [],
"details": "It was discovered that FFmpeg did not properly verify certain input when\nprocessing video and audio files. An attacker could possibly use this to send\nspecially crafted input to the application, force a division by zero, and\ncause a denial of service (application crash). (CVE-2020-20445, CVE-2020-20446,\nCVE-2020-20453, CVE-2020-20892)\n\nIt was discovered that FFmpeg did not properly perform certain bit shift and\nmemory operations. An attacker could possibly use this issue to expose\nsensitive information. (CVE-2020-20902)\n\nIt was discovered that FFmpeg did not properly perform memory management\noperations in various of its functions. An attacker could possibly use this\nissue to send specially crafted input to the application and cause a denial of\nservice (application crash) or execute arbitrary code. (CVE-2020-21041,\nCVE-2020-20451, CVE-2020-21688, CVE-2020-21697, CVE-2020-22020,\nCVE-2020-22021, CVE-2020-22022, CVE-2020-22025, CVE-2020-22031,\nCVE-2020-22032, CVE-2020-22037, CVE-2020-22040, CVE-2020-22041,\nCVE-2020-22042, CVE-2020-22044)\n\nIt was discovered that FFmpeg did not properly perform memory management\noperations in various of its functions. An attacker could possibly use this\nissue to send specially crafted input to the application and cause a denial of\nservice (application crash) or execute arbitrary code. (CVE-2020-22016,\nCVE-2020-22046, CVE-2020-22049, CVE-2020-22054)\n\nIt was discovered that FFmpeg did not properly perform memory management\noperations in various of its functions. An attacker could possibly use this\nissue to send specially crafted input to the application and cause a denial of\nservice (application crash) or execute arbitrary code. (CVE-2020-35965)\n\nIt was discovered that FFmpeg did not properly handle data assigned to the tty\ndemuxer. An attacker could possibly use this issue to send specially crafted\ninput to the application and expose sensitive information. (CVE-2021-3566)\n\nIt was discovered that FFmpeg did not perform checks on function return\nvalues when encoding and formatting input video and audio files. An attacker\ncould possibly use this issue to cause a denial of service (application crash)\nor execute arbitrary code. (CVE-2021-38114, CVE-2021-38171)\n\nIt was discovered that FFmpeg did not properly sanitize function returned data\nwhen calculating frame duration values. An attacker could possibly use this\nissue to cause an assertion failure and then cause a denial of service\n(application crash). (CVE-2021-38291)\n",
"id": "USN-5167-1",
"modified": "2026-06-25T10:46:02Z",
"published": "2022-06-13T16:13:57Z",
"references": [
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-5167-1"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2020-20445"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2020-20446"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2020-20451"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2020-20453"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2020-20892"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2020-20902"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2020-21041"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2020-21688"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2020-21697"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2020-22016"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2020-22020"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2020-22021"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2020-22022"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2020-22025"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2020-22031"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2020-22032"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2020-22037"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2020-22040"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2020-22041"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2020-22042"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2020-22044"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2020-22046"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2020-22049"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2020-22054"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2020-35965"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2021-3566"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2021-38114"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2021-38171"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2021-38291"
}
],
"related": [],
"schema_version": "1.7.0",
"summary": "ffmpeg vulnerabilities",
"upstream": [
"UBUNTU-CVE-2020-20445",
"UBUNTU-CVE-2020-20446",
"UBUNTU-CVE-2020-20451",
"UBUNTU-CVE-2020-20453",
"UBUNTU-CVE-2020-20892",
"UBUNTU-CVE-2020-20902",
"UBUNTU-CVE-2020-21041",
"UBUNTU-CVE-2020-21688",
"UBUNTU-CVE-2020-21697",
"UBUNTU-CVE-2020-22016",
"UBUNTU-CVE-2020-22020",
"UBUNTU-CVE-2020-22021",
"UBUNTU-CVE-2020-22022",
"UBUNTU-CVE-2020-22025",
"UBUNTU-CVE-2020-22031",
"UBUNTU-CVE-2020-22032",
"UBUNTU-CVE-2020-22037",
"UBUNTU-CVE-2020-22040",
"UBUNTU-CVE-2020-22041",
"UBUNTU-CVE-2020-22042",
"UBUNTU-CVE-2020-22044",
"UBUNTU-CVE-2020-22046",
"UBUNTU-CVE-2020-22049",
"UBUNTU-CVE-2020-22054",
"UBUNTU-CVE-2020-35965",
"UBUNTU-CVE-2021-3566",
"UBUNTU-CVE-2021-38114",
"UBUNTU-CVE-2021-38171",
"UBUNTU-CVE-2021-38291"
]
}
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.