LiveActive security incident?Get immediate response
CVE Record

CVE-2019-20022: An invalid memory address dereference was discovered in load_pnm in frompnm.c in libsixel before 1.8.3.

An invalid memory address dereference was discovered in load_pnm in frompnm.c in libsixel before 1.8.3.

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

Security readout for executives and security teams

Plain-English summary

This CVE concerns libsixel image-processing code. The reported bug is an invalid memory address dereference while loading PNM images in versions before 1.8.3. The public bundle does not provide a CVSS score, affected product list, or confirmed business impact, so urgency depends on whether untrusted PNM files reach libsixel in your environment.

Executive priority

Prioritize as dependency hygiene unless untrusted image processing is internet-facing or business-critical. Without CVSS, KEV, or exploit evidence, this is not proven urgent, but exposed file-parsing paths should be reviewed promptly.

Technical view

CVE-2019-20022 identifies an invalid memory address dereference in load_pnm in frompnm.c in libsixel before 1.8.3. The supplied sources do not describe exploit primitives, authentication requirements, or a confirmed impact beyond the memory dereference. Treat likely impact as process instability until vendor details confirm more.

Likely exposure

Exposure is most likely where applications, services, terminals, converters, or packaged tools include libsixel before 1.8.3 and process PNM input from users or external sources. The structured affected-product data in the bundle is incomplete.

Exploitation context

No active exploitation is cited, and the CVE is not marked KEV. The provided sources do not include exploit maturity, public exploit confirmation, or practical attack conditions. Risk rises if untrusted image files are automatically parsed by affected libsixel code.

Researcher notes

The evidence is sparse: CVE text names the function, file, and version boundary, but omits CWE, CVSS, exploitability, and detailed affected products. Further analysis should focus on dependency reachability and upstream issue details, not assumed exploitability.

Mitigation direction

  • Inventory systems and packages that include libsixel or link against it.
  • Check whether any workflow accepts or converts PNM files from untrusted sources.
  • Upgrade libsixel to 1.8.3 or later where vendor guidance confirms applicability.
  • Restrict or disable untrusted PNM processing until affected components are remediated.
  • Monitor the upstream GitHub issue and CVE record for clarifications.

Validation and detection

  • Confirm installed libsixel versions through package manifests or build dependency records.
  • Trace image-processing paths to see whether load_pnm can be reached.
  • Review application logs for crashes during PNM or image conversion handling.
  • Verify patched deployments use libsixel 1.8.3 or later where applicable.
  • Document any compensating controls around untrusted file intake.
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-2019-20022 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.