dbcve.org
HTTP ServerWeb server / proxy · Apache

CVE-2017-15715

HIGH · 8.1 CVSS v3.0 Published 2018-03-26
Fix available
A fix is available. Upgrade to after 2.4.29 or later.
See remediation →
90/100
Remediation priority · Urgent
High EPSS 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
In Apache httpd 2.4.0 to 2.4.29, the expression specified in <FilesMatch> could match '$' to a newline character in a malicious filename, rather than matching only the end of the filename. This could be exploited in environments where uploads of some files are are externally blocked, but only by matching the trailing portion of the filename.

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

In Apache httpd 2.4.0-2.4.29, the '$' anchor in <FilesMatch> regex patterns incorrectly matches a newline character in filenames rather than only matching the end of the filename. This allows attackers to bypass file upload restrictions that rely on filename matching by embedding newline characters in malicious filenames.

MitigationUpgrade Apache httpd to version 2.4.30 or later, which contains the fix for this regex matching flaw.

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
HTTP ServerWeb server / proxy
Affected:>= 2.4.0, <= 2.4.29
Debian LinuxOperating system
Affected:= 8.0= 9.0
Ubuntu LinuxOperating system
Affected:= 14.04= 16.04= 17.10= 18.04
Enterprise LinuxOperating system
Affected:= 6.0= 7.0= 7.4= 7.5= 7.6
Santricity Cloud ConnectorApplication
Affected:all versions
Storage Automation StoreApplication
Affected:all versions
StoragegridApplication
Affected:all versions
Clustered Data OntapOperating system
Affected:all versions

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:H/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. Check Apache httpd version
    Run 'httpd -v' or 'apache2 -v' to retrieve the server version. On some systems, check '/usr/sbin/httpd -v' or '/usr/sbin/apache2 -v'. If these paths do not exist, locate the httpd or apache2 binary using 'which httpd' or 'which apache2'.
    Affected if The installed version is 2.4.0 through 2.4.29 inclusive. Versions below 2.4.0 or at 2.4.30 and later are not affected.
  2. Identify FilesMatch directives with regex patterns
    Search Apache configuration files (httpd.conf, apache2.conf, included .conf files in sites-enabled or conf.d directories) for 'FilesMatch' directives containing '$' in the regex pattern. Use 'grep -r "FilesMatch"' across config directories.
    Affected if A <FilesMatch> directive uses a pattern with '$' as an anchor (for example, '\.php$') to restrict filename extensions, and this configuration is used for access control or file upload filtering.
  3. Verify file upload functionality exists
    Review the web application or configuration to determine if there is a file upload mechanism that relies on filename matching via <FilesMatch> to restrict allowed file types.
    Affected if File upload functionality is present and depends on <FilesMatch> regex patterns with '$' anchors to enforce filename restrictions.

A server is affected if it runs Apache httpd version 2.4.0 through 2.4.29 and uses <FilesMatch> directives with '$' anchors in regex patterns to restrict filenames, particularly for file upload controls.

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.

From vendor data
Upgrade available Upgrade to a release after 2.4.29
Interim mitigation

Upgrade Apache httpd to version 2.4.30 or later, which contains the fix for this regex matching flaw.

Fix this in HTTP Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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