LiveActive security incident?Get immediate response
CVE Record

CVE-2022-43250: Libde265 v1.0.8 was discovered to contain a heap-buffer-overflow vulnerability via put_qpel_0_0_fallback_16...

Libde265 v1.0.8 was discovered to contain a heap-buffer-overflow vulnerability via put_qpel_0_0_fallback_16 in fallback-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-43250 is a memory-safety flaw in libde265 v1.0.8, a library for decoding HEVC/H.265 video. A specially crafted video file can crash software using the library, creating a denial-of-service risk. The provided sources do not indicate data theft, code execution, or confirmed active exploitation.

Executive priority

Handle as a moderate availability issue. It matters most for organizations that process external video content, where crashes can disrupt services or workflows. It is less urgent for systems without libde265 or without untrusted video decoding, but vendor patch status should still be verified.

Technical view

The flaw is a heap buffer overflow, CWE-787, in put_qpel_0_0_fallback_16 within fallback-motion.cc. CVSS 3.1 is 6.5 with network attack vector, low complexity, no privileges, user interaction required, and high availability impact. Debian published security updates through DSA-5346 and DLA-3280-1.

Likely exposure

Exposure is most likely where libde265 v1.0.8, or affected distro packages, process untrusted HEVC/H.265 video files. Risk is higher for media services, upload pipelines, desktop previewers, and applications that automatically decode user-supplied video. The CVE affected-product metadata is incomplete.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. Practical exploitation requires getting a vulnerable decoder to process a crafted video file. The documented impact is denial of service, not confidentiality or integrity compromise.

Researcher notes

The CVE record names libde265 v1.0.8 and the vulnerable function, but its structured affected-product data is sparse. Debian advisories confirm downstream security updates. Avoid assuming broader products or exploitability beyond denial of service unless additional vendor evidence supports it.

Mitigation direction

  • Apply Debian security updates referenced in DSA-5346 or DLA-3280-1 where applicable.
  • Check upstream libde265 and OS vendor guidance for fixed versions outside Debian.
  • Prioritize systems that process uploaded, emailed, or externally supplied video files.
  • Limit automatic decoding of untrusted HEVC/H.265 media until patched.
  • Reduce exposure of public media-processing services that depend on libde265.

Validation and detection

  • Inventory applications and packages that include or link libde265.
  • Identify any libde265 v1.0.8 deployments or affected distro package versions.
  • Confirm patched package status against Debian DSA-5346 or local vendor advisories.
  • Review media-processing paths for untrusted HEVC/H.265 input handling.
  • Check crash telemetry for decoder failures tied to HEVC/H.265 files.
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-43250 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-43250Attack 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.