LiveActive security incident?Get immediate response
CVE Record

CVE-2022-43239: Libde265 v1.0.8 was discovered to contain a heap-buffer-overflow vulnerability via mc_chroma<unsigned short...

Libde265 v1.0.8 was discovered to contain a heap-buffer-overflow vulnerability via mc_chroma<unsigned short> in motion.cc. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted video file.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-43239 is a denial-of-service flaw in libde265 v1.0.8, a library for decoding H.265/HEVC video. A malicious video file can trigger a heap buffer overflow and crash software that processes it. The cited sources do not show data theft, code execution, or confirmed active exploitation.

Executive priority

Prioritize remediation for internet-facing upload workflows and automated media-processing systems. For general endpoints, handle through normal patch management unless they routinely process untrusted video. Business risk is service interruption, not proven compromise, based on the provided sources.

Technical view

The CVE describes a CWE-787 heap-buffer-overflow in mc_chroma<unsigned short> in motion.cc. CVSS 3.1 is 6.5: network reachable, low complexity, no privileges, user interaction required, availability impact high, confidentiality and integrity unaffected.

Likely exposure

Exposure is most likely where libde265 is used to decode untrusted or externally supplied H.265/HEVC video files, including media services, file-processing pipelines, desktop viewers, and Linux systems carrying vulnerable packages. The bundle does not provide complete affected product or version ranges beyond libde265 v1.0.8.

Exploitation context

The required trigger is processing a crafted video file. KEV is false, and the provided sources do not cite in-the-wild exploitation. Treat this as a reliability and service-availability risk, especially for automated video ingestion or preview generation.

Researcher notes

Evidence supports a heap overflow DoS in libde265 v1.0.8 with function and file context. Public metadata lacks precise upstream fixed version, affected CPEs, and exploit status beyond no KEV listing. Debian published security updates, so downstream package tracking is important.

Mitigation direction

  • Inventory systems and applications that include libde265 or process H.265/HEVC files.
  • Apply vendor or distribution security updates, including relevant Debian libde265 advisories where applicable.
  • Restrict automated processing of untrusted video until affected components are updated.
  • Run media decoding workloads with isolation and resource limits where feasible.
  • Monitor vendor guidance for exact fixed versions and downstream package status.

Validation and detection

  • Confirm installed libde265 package or bundled library versions against vendor advisories.
  • Identify services that automatically decode uploaded, emailed, or downloaded video files.
  • Review crash logs for libde265 decoding failures after handling external media.
  • Verify patched systems no longer report vulnerable libde265 package versions.
  • Check dependency manifests for statically bundled libde265 copies.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-787: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-43239 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2022-43239Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.