dbcve.org
Drupal Docker ImagesApplication · Drupal

CVE-2020-35191

CRITICAL · 9.8 CVSS v3.1 Published 2020-12-17
Fix available
A fix is available. Upgrade to after 8.5.10-fpm-alpine or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The official drupal docker images before 8.5.10-fpm-alpine (Alpine specific) contain a blank password for a root user. System using the drupal docker container deployed by affected versions of the docker image may allow a remote attacker to achieve root access with a blank password.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The official Drupal Docker images (Alpine-based variants) prior to version 8.5.10-fpm-alpine shipped with a blank root password, creating a critical authentication bypass that allows remote attackers to gain root-level access to the container.

MitigationUpgrade to Drupal Docker image version 8.5.10-fpm-alpine or later, or migrate to a non-Alpine variant; verify no exposures exist from container networking or port mappings.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Drupal Docker ImagesApplication
Affected:>= 8.3.1-fpm-alpine, <= 8.5.10-fpm-alpine= 8.3.0-fpm-alpine

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if running Drupal Docker Alpine image
    Run 'docker images' and look for images matching pattern 'drupal:*-fpm-alpine'
    Affected if Image name contains '-fpm-alpine' and is a Drupal Docker image
  2. Check the exact image version tag
    Run 'docker images' and examine the TAG column for versions between 8.3.0 and 8.5.10-fpm-alpine inclusive
    Affected if Version tag is 8.3.0-fpm-alpine OR falls within range 8.3.1-fpm-alpine through 8.5.10-fpm-alpine
  3. Verify root account password status
    Attempt to exec into container as root with 'docker exec -it <container> su -' or inspect /etc/shadow inside the container
    Affected if Root password is empty or blank, allowing login without authentication
  4. Check for exposed SSH or remote access services
    Run 'docker ps --format "{{.Ports}}"' to list port mappings, look for port 22 or other remote access services exposed
    Affected if Port 22 (SSH) or other remote management ports are mapped to host interfaces (0.0.0.0)

A user is affected if they are running a Drupal Docker Alpine FPM image with version 8.3.0 through 8.5.10-fpm-alpine that has a blank root password exposed via network access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 8.5.10-fpm-alpine
Interim mitigation

Upgrade to Drupal Docker image version 8.5.10-fpm-alpine or later, or migrate to a non-Alpine variant; verify no exposures exist from container networking or port mappings.

Recommended fix High confidence

Drupal Docker image 8.5.10-fpm-alpine or later (recommended: latest stable 8.x-fpm-alpine or 9.x-fpm-alpine)

  1. Identify all Docker containers running affected Drupal Alpine images (8.3.0-fpm-alpine through 8.5.10-fpm-alpine)
  2. Stop the affected containers: docker stop <container_id>
  3. Remove the affected containers: docker rm <container_id>
  4. Pull the fixed Drupal Docker image (8.5.10-fpm-alpine or later, preferably latest stable): docker pull drupal:8.9-fpm-alpine (or newer stable version)
  5. Redeploy containers using the fixed image with appropriate configuration
  6. Verify the root user has a secure password set in the container
  7. Ensure container networking restricts remote access to prevent exploitation
Caveat Review Drupal release notes for any configuration or compatibility changes when upgrading between minor versions; test thoroughly in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Drupal Docker Images Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-35191 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-35191 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data