Security readout for executives and security teams
Plain-English summary
A specially crafted BPG image can crash software using libbpg 0.9.7 during HEVC-backed image processing. Business impact is most likely service disruption in applications that accept or process BPG files. Public sources do not provide CVSS, a confirmed patch, or active exploitation evidence.
Executive priority
Prioritize where BPG processing is internet-facing or business-critical. The known impact is denial of service, but the lack of severity scoring and patch detail means teams should first verify real product exposure.
Technical view
The issue is in hevc_write_frame in libbpg.c, related to FFmpeg libavcodec paths hls_pcm_sample in hevc.c and put_pcm_var in hevcdsp_template.c. The reported result is out-of-bounds read and application crash, with unspecified other impact only noted as possible.
Likely exposure
Exposure is limited to systems or services using libbpg 0.9.7 to process BPG files, especially where files come from users, partners, or automated ingestion pipelines.
Exploitation context
The source describes remote attackers using a crafted BPG file. The bundle does not cite CISA KEV listing or any confirmed in-the-wild exploitation.
Researcher notes
The public record is sparse: no CVSS, CWE, CPE, or confirmed fix is included in the supplied bundle. Treat unspecified other impact as unproven unless additional vendor or maintainer evidence is found.
Mitigation direction
- Inventory applications and services that use libbpg, especially version 0.9.7.
- Check upstream libbpg and downstream vendor guidance for fixed versions or advisories.
- Restrict or disable untrusted BPG file processing where business impact is acceptable.
- Run image-processing workloads with isolation and crash recovery controls.
Validation and detection
- Confirm whether libbpg 0.9.7 exists in deployed packages, containers, or embedded dependencies.
- Identify public upload, email, API, or batch workflows that accept BPG files.
- Review crash logs for image-processing failures tied to BPG handling.
- Verify vendor or maintainer guidance before declaring remediation complete.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CVE-2017-14795 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/leonzhao7/vulnerability/blob/master/An%20Out-of-Bounds%20Read%20%28DoS%29%20Vulnerability%20in%20hevc.c%20of%20libbpg.mdCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.