Skip to content
Fencer Intel
medium 5.5

CVE-2021-36411 json

An issue has been found in libde265 v1.0.8 due to incorrect access control.

published 4y ago modified 4mo ago also EUVD-2021-23014

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 69%
public exploits
0
none known

Summary

An issue has been found in libde265 v1.0.8 due to incorrect access control. A SEGV caused by a READ memory access in function derive_boundaryStrength of deblock.cc has occurred. The vulnerability causes a segmentation fault and application crash, which leads to remote denial of service.

Patch / fix

  • libde265 Debian 14, Debian 13, Debian 12 1.0.8-1.1

debian advisories DEBIAN-CVE-2021-36411

  • libde265 Ubuntu 20.04 LTS 1.0.4-1ubuntu0.2
  • libde265 Ubuntu 22.04 LTS 1.0.8-1ubuntu0.1
  • libde265 Ubuntu Pro 16.04 LTS 1.0.2-2ubuntu0.16.04.1~esm2
  • libde265 Ubuntu Pro 18.04 LTS 1.0.2-2ubuntu0.18.04.1~esm2

ubuntu advisories UBUNTU-CVE-2021-36411

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • libde265 Alpine 3.24, Alpine 3.23, Alpine 3.22 +8 more 1.0.8-r2

alpine advisories ALPINE-CVE-2021-36411

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2021-36411 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.24% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/strukturag/libde265/issues/302 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.