LiveActive security incident?Get immediate response
CVE Record

CVE-2019-19887: bitstr_tell at bitstr.c in ffjpeg through 2019-08-21 has a NULL pointer dereference related to jfif_encode.

bitstr_tell at bitstr.c in ffjpeg through 2019-08-21 has a NULL pointer dereference related to jfif_encode.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE describes a NULL pointer dereference in ffjpeg, a JPEG-related library, through 2019-08-21. In practical terms, software using the vulnerable encode path may crash if the flaw is reached. Public sources do not provide severity scoring, affected package identifiers, a confirmed patch, or evidence of active exploitation.

Executive priority

Treat this as a targeted exposure-verification item, not an emergency, unless ffjpeg is used in production paths that process untrusted images. The main documented concern is reliability impact, and public evidence is too sparse to justify higher urgency without local reachability.

Technical view

The CVE record identifies bitstr_tell in bitstr.c in ffjpeg through 2019-08-21 as having a NULL pointer dereference related to jfif_encode. The public bundle lacks CVSS, CWE, CPE, fixed-version, exploit, and remediation details, so exposure must be confirmed from dependency and code-path evidence.

Likely exposure

Exposure is likely limited to applications or services that embed ffjpeg and invoke the affected jfif_encode-related path. Internet exposure depends on whether untrusted image data can reach that functionality. The source bundle does not identify distributions, packages, or downstream products.

Exploitation context

The CVE is not listed as CISA KEV in the provided bundle, and no cited source states active exploitation. The public reference is a GitHub issue. Available evidence supports a potential crash condition, but not remote code execution or weaponized exploitation.

Researcher notes

Key gaps are severity, CWE mapping, affected package identifiers, exploitability details, and fixed-version evidence. Prioritize reachability analysis around bitstr_tell, bitstr.c, and jfif_encode, then map any dependency evidence to the 2019-08-21 cutoff stated in the CVE description.

Mitigation direction

  • Inventory applications, containers, and source trees for ffjpeg usage.
  • Check upstream ffjpeg guidance and issue history for an official fix or safe revision.
  • Restrict untrusted input from reaching ffjpeg encode functionality where feasible.
  • Isolate image-processing services to limit availability impact from crashes.
  • Consider replacing ffjpeg if no maintained fix is available.

Validation and detection

  • Confirm whether deployed software includes ffjpeg through 2019-08-21.
  • Review whether jfif_encode is reachable in production workflows.
  • Check crash logs for NULL dereference symptoms in bitstr.c or image encoding paths.
  • Verify whether any upstream or vendor patch is documented before claiming remediation.
  • Document unknowns where package identity, versioning, or reachability cannot be proven.
Prepared
Confidence
medium
Sources
3

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-19887 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.