LiveActive security incident?Get immediate response
CVE Record

CVE-2018-19759: There is a heap-based buffer over-read at stb_image_write.h (function: stbi_write_png_to_mem) in libsixel 1...

There is a heap-based buffer over-read at stb_image_write.h (function: stbi_write_png_to_mem) in libsixel 1.8.2 that will cause a denial of service.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2018-19759 is a memory-read flaw reported in libsixel 1.8.2. The public description says it can cause denial of service. The available bundle does not provide CVSS scoring, confirmed affected product metadata, exploitation evidence, or a vendor fix, so urgency depends on whether libsixel is used in business-critical image or terminal graphics workflows.

Executive priority

Treat as a targeted availability risk, not a confirmed broad emergency. Prioritize remediation if libsixel supports production automation, customer-facing conversion, or high-availability rendering paths. Otherwise, handle through normal vulnerability management once vendor guidance is confirmed.

Technical view

The issue is described as a heap-based buffer over-read in stb_image_write.h, specifically stbi_write_png_to_mem, within libsixel 1.8.2. The stated impact is denial of service. No CWE, CVSS vector, patch version, or detailed affected CPEs are present in the provided sources.

Likely exposure

Exposure is likely limited to environments running libsixel 1.8.2 or software that embeds it. Risk is higher where untrusted image or sixel-related content is processed in automated services, user-facing conversion paths, or batch rendering systems.

Exploitation context

The source bundle does not show CISA KEV listing or cite active exploitation. Public evidence provided supports a denial-of-service risk, but not remote exploitability, privilege escalation, data theft, or exploitation in the wild.

Researcher notes

Evidence is sparse. The CVE description names libsixel 1.8.2 and stbi_write_png_to_mem, but structured affected-product data is empty and no CVSS or CWE is supplied. Avoid assuming exploitability beyond denial of service without reviewing the referenced Red Hat bug or downstream advisories.

Mitigation direction

  • Inventory systems and packages for libsixel 1.8.2 usage.
  • Check vendor or distribution advisories for patched libsixel packages.
  • Prioritize updates where untrusted content reaches libsixel processing paths.
  • Restrict or isolate automated image conversion workflows handling untrusted input.
  • Monitor service crashes around sixel or PNG generation workflows.

Validation and detection

  • Confirm installed libsixel versions through approved asset inventory tooling.
  • Identify applications statically or dynamically linked against libsixel.
  • Review whether affected workflows process untrusted files or terminal graphics content.
  • Check package manager advisories for available fixed builds.
  • Look for crash reports referencing stbi_write_png_to_mem or libsixel.
Prepared
Confidence
medium
Sources
3

Public sources used

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.

cve · low confidence lookup

CVE-2018-19759 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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