Back to bug 2189944
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla | 2023-07-07 08:35:42 UTC | Assignee | security-response-team | nobody |
| Paige Jung | 2023-08-10 18:21:06 UTC | Doc Text | Libde265 v1.0.11 was discovered to contain a segmentation violation via the function decoder_context::process_slice_segment_header at decctx.cc. Reference: https://github.com/strukturag/libde265/issues/393 Fixed on master. | |
| Doc Text | Libde265 v1.0.11 was discovered to contain a segmentation violation via the function decoder_context::process_slice_segment_header at decctx.cc. Reference: https://github.com/strukturag/libde265/issues/393 Fixed on master. | Libde265 v1.0.11 was discovered to contain a segmentation violation via the function decoder_context::process_slice_segment_header at decctx.cc. Reference: https://github.com/strukturag/libde265/issues/393 Libde265 v1.0.11 was discovered to contain a | ||
| Doc Text | heap buffer overflow via the function derive_collocated_motion_vectors at motion.cc. Reference: https://github.com/strukturag/libde265/issues/394 Fixed on master. | |||
| Doc Text | Libde265 v1.0.11 was discovered to contain a segmentation violation via the function decoder_context::process_slice_segment_header at decctx.cc. Reference: https://github.com/strukturag/libde265/issues/393 Libde265 v1.0.11 was discovered to contain a heap buffer overflow via the function derive_collocated_motion_vectors at motion.cc. Reference: https://github.com/strukturag/libde265/issues/394 Fixed on master. | A flaw was found in Libde265 v1.0.11, which contains a segmentation violation via the function decoder_context::process_slice_segment_header at decctx.cc. This issue can cause a denial of service. See https://github.com/strukturag/libde265/issues/393 for more information. Libde265 v1.0.11 also contains a heap buffer overflow via the function derive_collocated_motion_vectors at motion.cc that may lead to a denial of service and remote code execution. See https://github.com/strukturag/libde265/issues/394 for more information. |
Back to bug 2189944