LiveActive security incident?Get immediate response
CVE Record

CVE-2023-38745: Pandoc before 3.1.6 allows arbitrary file write: this can be triggered by providing a crafted image element...

Pandoc before 3.1.6 allows arbitrary file write: this can be triggered by providing a crafted image element in the input when generating files via the --extract-media option or outputting to PDF format. This allows an attacker to create or overwrite arbitrary files, depending on the privileges of the process running Pandoc. It only affects systems that pass untrusted user input to Pandoc and allow Pandoc to be used to produce a PDF or with the --extract-media option. NOTE: this issue exists because of an incomplete fix for CVE-2023-35936 (failure to properly account for double encoded path names).

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

Security readout for executives and security teams

Plain-English summary

Pandoc before 3.1.6 can be tricked into writing or overwriting files when processing malicious input in specific conversion modes. Business risk is highest for services that let users upload documents and convert them to PDF or extract embedded media automatically.

Executive priority

Prioritize remediation for internet-facing or customer-facing document conversion systems. Internal-only usage with trusted documents is lower urgency, but still should be patched because arbitrary file overwrite can become serious under elevated service privileges.

Technical view

The flaw is an arbitrary file write in Pandoc triggered by crafted image elements during PDF output or when using --extract-media. It only applies when untrusted input reaches those workflows. The CVE notes this was an incomplete fix for CVE-2023-35936 involving double-encoded path names.

Likely exposure

Exposure is likely limited to document conversion services, CI jobs, CMS workflows, or backend utilities that run Pandoc on attacker-controlled content with PDF generation or --extract-media enabled.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Exploitation depends on controlling Pandoc input and having a vulnerable conversion path that permits file creation or overwrite with the Pandoc process privileges.

Researcher notes

Focus assessment on trust boundaries and output modes, not just package presence. The key question is whether attacker-controlled input reaches Pandoc before 3.1.6 with PDF or media extraction enabled. The sources do not provide CVSS, CWE, or exploitation telemetry.

Mitigation direction

  • Upgrade Pandoc to 3.1.6 or later.
  • Apply Debian or Fedora security updates where using packaged Pandoc.
  • Disable PDF conversion for untrusted input until patched.
  • Disable --extract-media for untrusted input until patched.
  • Run conversion workers with minimal filesystem privileges.
  • Check vendor guidance for platform-specific package status.

Validation and detection

  • Inventory Pandoc versions across servers, build systems, and containers.
  • Identify workflows that pass user-controlled content to Pandoc.
  • Confirm whether PDF output or --extract-media is enabled.
  • Verify patched packages from Debian, Fedora, or upstream Pandoc.
  • Review service accounts for unnecessary write permissions.
Prepared
Confidence
high
Sources
8

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.

description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-38745 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
9Source 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.