dbcve.org
Storage ApiApplication · Drupal

CVE-2014-5170

CRITICAL · 9.8 CVSS v3.0 Published 2018-03-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Storage API module 7.x before 7.x-1.6 for Drupal might allow remote attackers to execute arbitrary code by leveraging failure to update .htaccess file contents after SA-CORE-2013-003.

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 Storage API module for Drupal 7.x versions before 7.x-1.6 fails to properly update .htaccess file contents in accordance with Drupal security advisory SA-CORE-2013-003. This missing .htaccess hardening creates a path for remote attackers to execute arbitrary code via the affected module's directories.

MitigationUpdate the Storage API module to version 7.x-1.6 or later, which includes the corrected .htaccess file handling consistent with Drupal's security hardening requirements.

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
Storage ApiApplication
Affected:= 7.x-1.0= 7.x-1.1= 7.x-1.2= 7.x-1.3= 7.x-1.4= 7.x-1.5= 7.x-1.x-dev

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.0/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 Storage API module installation
    Locate the storage_api module directory in your Drupal installation (typically in sites/all/modules/ or sites/all/modules/contrib/)
    Affected if The storage_api directory exists in the modules folder
  2. Check Storage API module version
    Open the storage_api.info file and look for the version field, or check the module's main .info file for version information
    Affected if Version is 7.x-1.0, 7.x-1.1, 7.x-1.2, 7.x-1.3, 7.x-1.4, 7.x-1.5, or 7.x-1.x-dev (any version before 7.x-1.6)
  3. Inspect .htaccess files in storage directories
    Find .htaccess files within the storage_api module directory and its created storage directories (look in files/, private/, or similar storage paths the module creates)
    Affected if The .htaccess file is missing or does not contain the Drupal SA-CORE-2013-003 security directives (deny from all, Options -Indexes, etc.)
  4. Verify module storage directories are web-accessible
    Check if the storage directories created by storage_api are accessible via HTTP from the web
    Affected if Storage directories are accessible and contain vulnerable .htaccess configuration (or no .htaccess at all)

You are affected if the Storage API module version is 7.x-1.5 or earlier and the .htaccess files in module directories lack proper Drupal security hardening.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Storage API module to version 7.x-1.6 or later, which includes the corrected .htaccess file handling consistent with Drupal's security hardening requirements.

Recommended fix High confidence

7.x-1.6

  1. 1. Back up your Drupal site database and files, including the sites/all/modules/storage_api directory
  2. 2. Download Storage API version 7.x-1.6 from the official Drupal repository at www.drupal.org/project/storage_api
  3. 3. Disable the storage_api module via the Drupal admin interface or using drush dis storage_api
  4. 4. Replace the existing storage_api module files in sites/all/modules/ with the new 7.x-1.6 version
  5. 5. Re-enable the storage_api module via the Drupal admin interface or using drush en storage_api
  6. 6. Run the Drupal update.php script at yoursite.com/update.php to apply any database schema changes
  7. 7. Clear all Drupal caches via the admin interface or using drush cc all
  8. 8. Verify the .htaccess file in the storage directory has been properly updated with secure directives
Caveat Review the module's release notes for any configuration or API changes between your current version and 7.x-1.6 before upgrading in production

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

Fix this in Storage Api Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-5170 — 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-2014-5170 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