Skip to main content

CVE-2020-13671Drupal core Un-restricted Upload of File

Patch nowHigh8.8Exploited, CISA due date 2022-07-18EPSS 36%, higher than 98% of scored CVEs

CVE-2020-13671 is a unrestricted file upload in Drupal core, rated high (8.8 on CVSS 3.1).

Why this priority: Exploited in the wild: listed in CISA's KEV catalog.

Published · Updated · NVD status: Analyzed

What it is

Files of dangerous types can be uploaded, and the server may run or serve them.

How it is reached

An attacker can exploit it over the network, with an ordinary user account, and nobody has to click anything.

What an attacker gains

A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker place a file the server will run or serve to others.

Is it being exploited?

CISA added it to the Known Exploited Vulnerabilities catalog on 2022-01-18: it is being exploited in the wild. EPSS estimates a 36% chance of exploitation activity in the next 30 days, higher than 98% of scored CVEs.

What to do

  1. Treat it as urgent: it is on CISA's KEV list. CISA's deadline for US federal agencies: 2022-07-18.
  2. Upgrade Drupal core to a fixed version for your release line (7.74, 8.8.11, 8.9.9). The patch notes are linked below.
  3. Until it is patched, review who holds accounts that can reach it.
  4. Check exposed instances for signs of compromise, not only for the version.

Description from NVD

Drupal core does not properly sanitize certain filenames on uploaded files, which can lead to files being interpreted as the incorrect extension and served as the wrong MIME type or executed as PHP for certain hosting configurations. This issue affects: Drupal Drupal Core 9.0 versions prior to 9.0.8, 8.9 versions prior to 8.9.9, 8.8 versions prior to 8.8.11, and 7 versions prior to 7.74.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Operating systems on servers, workstations or devices. Everything on the host inherits the flaw.
  • Upload endpoints and the storage behind them. The flaw sits between uploaded content and the servers that store or serve it.

Trust boundaries in play

  • Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
  • Between uploaded content and the servers that store or serve it. An attacker who crosses it can place a file the server will run or serve to others.

Questions to answer about your own systems

  • Where does Drupal core run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.