LiveActive security incident?Get immediate response
CVE Record

CVE-2018-21238: An issue was discovered in Foxit PhantomPDF before 8.3.7.

An issue was discovered in Foxit PhantomPDF before 8.3.7. It allows memory consumption via an ArrayBuffer(0xfffffffe) call.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

Foxit PhantomPDF versions before 8.3.7 had a memory consumption issue. The available source says a crafted ArrayBuffer call could consume memory, which points to denial-of-service risk rather than confirmed data theft or system takeover.

Executive priority

Treat this as a targeted cleanup item unless vulnerable Foxit PhantomPDF is widely deployed. Business urgency rises if legacy PDF tooling is common on user workstations or unsupported versions cannot be centrally upgraded.

Technical view

CVE-2018-21238 describes memory consumption in Foxit PhantomPDF before 8.3.7 via ArrayBuffer(0xfffffffe). The public bundle provides no CVSS score, CWE, detailed attack vector, patch note, or proof of active exploitation.

Likely exposure

Organizations are likely exposed only where Foxit PhantomPDF versions earlier than 8.3.7 remain installed. The source bundle does not identify affected CPEs, platforms, deployment modes, or whether later Foxit-branded products are affected.

Exploitation context

The vulnerability is not listed as KEV in the provided bundle, and no cited source claims active exploitation. The available evidence does not establish whether exploitation is remote, local, document-triggered, or browser/plugin-triggered.

Researcher notes

Evidence is sparse. The record identifies a memory consumption condition and affected version boundary, but lacks CVSS, CWE, platform detail, attack preconditions, and confirmed remediation text beyond the before-8.3.7 boundary.

Mitigation direction

  • Inventory Foxit PhantomPDF installations and identify versions earlier than 8.3.7.
  • Move affected installations off versions earlier than 8.3.7.
  • Check Foxit security bulletins for the supported upgrade path.
  • Retire unsupported PhantomPDF installations where upgrades are unavailable.

Validation and detection

  • Confirm installed Foxit PhantomPDF version numbers on managed endpoints.
  • Compare detected versions against the before-8.3.7 affected range.
  • Review Foxit bulletin history for the relevant PhantomPDF advisory.
  • Monitor endpoint telemetry for repeated Foxit memory exhaustion or crashes.
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-2018-21238 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.