Linux · Ubuntu · Package update · November 2, 2022

libde265-examples 1.0.8-1ubuntu0.1: libde265-examples 1.0.8-1ubuntu0.1 for Ubuntu 22.04.1 LTS (jammy)

libde265-examples 1.0.8-1ubuntu0.1, released November 2, 2022, fixes 18 CVEs in libde265-examples. None of them is reported as exploited. Patch Radar priority: Urgent.

Urgent
CVEs closed
18
1 rated Critical
Exploited
0
None reported
Highest CVSS
9.8
Base score, 0 to 10
Highest EPSS
0.0205
81st percentile

Priority of the 18 CVEs

Patch now 0 Urgent 1 High 1 Routine 16

Fixed package versions

ProductReleaseFixed in
libde265-examplesUbuntu 22.04.1 LTS (jammy)1.0.8-1ubuntu0.1

CVEs this fix closes

PriorityCVETitleCVSSEPSSExploitation
Urgent CVE-2022-1253 libde265: Heap-based Buffer Overflow in GitHub repository strukturag/libde265 prior to and including 1.0.89.8 0.0205 None reported
High CVE-2021-36409 libde265: There is an Assertion `scaling_list_pred_matrix_id_delta==1' failed at sps.cc:925 in libde265 v1.0.8 when decoding fi...7.8 0.0097 None reported
Routine CVE-2021-35452 libde265: An Incorrect Access Control vulnerability exists in libde265 v1.0.8 due to a SEGV in slice.cc.6.5 0.0142 None reported
Routine CVE-2021-36411 libde265: An issue has been found in libde265 v1.0.8 due to incorrect access control5.5 0.0124 None reported
Routine CVE-2022-43236 libde265: Libde265 v1.0.8 was discovered to contain a stack-buffer-overflow vulnerability via put_qpel_fallback<unsigned short>...6.5 0.0116 None reported
Routine CVE-2022-43237 libde265: Libde265 v1.0.8 was discovered to contain a stack-buffer-overflow vulnerability via void put_epel_hv_fallback<unsigne...6.5 0.0116 None reported
Routine CVE-2022-43238 libde265: Libde265 v1.0.8 was discovered to contain an unknown crash via ff_hevc_put_hevc_qpel_h_3_v_3_sse in sse-motion.cc6.5 0.0116 None reported
Routine CVE-2022-43242 libde265: Libde265 v1.0.8 was discovered to contain a heap-buffer-overflow vulnerability via mc_luma<unsigned char> in motion.cc6.5 0.0116 None reported
Routine CVE-2022-43239 libde265: Libde265 v1.0.8 was discovered to contain a heap-buffer-overflow vulnerability via mc_chroma<unsigned short> in motio...6.5 0.0114 None reported
Routine CVE-2022-43240 libde265: Libde265 v1.0.8 was discovered to contain a heap-buffer-overflow vulnerability via ff_hevc_put_hevc_qpel_h_2_v_1_sse...6.5 0.0114 None reported
Routine CVE-2022-43241 libde265: Libde265 v1.0.8 was discovered to contain an unknown crash via ff_hevc_put_hevc_qpel_v_3_8_sse in sse-motion.cc6.5 0.0114 None reported
Routine CVE-2022-43243 libde265: Libde265 v1.0.8 was discovered to contain a heap-buffer-overflow vulnerability via ff_hevc_put_weighted_pred_avg_8_ss...6.5 0.0114 None reported
Routine CVE-2022-43248 libde265: Libde265 v1.0.8 was discovered to contain a heap-buffer-overflow vulnerability via put_weighted_pred_avg_16_fallback...6.5 0.0114 None reported
Routine CVE-2022-43252 libde265-0: Libde265 v1.0.8 was discovered to contain a heap-buffer-overflow vulnerability via put_epel_16_fallback in fallback-m...6.5 0.0114 None reported
Routine CVE-2022-43253 libde265: Libde265 v1.0.8 was discovered to contain a heap-buffer-overflow vulnerability via put_unweighted_pred_16_fallback in...6.5 0.0114 None reported
Routine CVE-2022-43235 libde265-examples: Libde265 v1.0.8 was discovered to contain a heap-buffer-overflow vulnerability via ff_hevc_put_hevc_epel_pixels_8_sse...6.5 0.0112 None reported
Routine CVE-2021-36410 libde265: A stack-buffer-overflow exists in libde265 v1.0.8 via fallback-motion.cc in function put_epel_hv_fallback when runnin...5.5 0.0092 None reported
Routine CVE-2021-36408 libde265: An issue was discovered in libde265 v1.0.8.There is a Heap-use-after-free in intrapred.h when decoding file using dec...5.5 0.0090 None reported
Showing 1 to 18 of 18 1

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.