HTTP ServerWeb server / proxy · Apache

CVE-2014-3583

MEDIUM · 5.0 CVSS v2.0 Published 2014-12-15

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

59/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

The handle_headers function in mod_proxy_fcgi.c in the mod_proxy_fcgi module in the Apache HTTP Server 2.4.10 allows remote FastCGI servers to cause a denial of service (buffer over-read and daemon crash) via long response headers.

Technical summary

dbcve analysis · moderate confidence

The handle_headers function in mod_proxy_fcgi.c in Apache HTTP Server 2.4.10 contains a buffer over-read vulnerability when processing response headers from remote FastCGI servers. Specifically, when headers exceed expected lengths, the function reads beyond allocated buffer boundaries, causing a denial of service via daemon crash.

MitigationUpgrade Apache HTTP Server to version 2.4.10 or later that contains the patched handle_headers function in mod_proxy_fcgi, or apply the vendor patch if available for the specific version in use.

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

Affected products & versions

NVD · CPE data

HTTP ServerWeb server / proxy

Affected:= 2.4.10

Ubuntu LinuxOperating system

Affected:= 10.04= 12.04= 14.04= 14.10

Mac Os XOperating system

Affected:= 10.9.5= 10.10.0= 10.10.1= 10.10.2= 10.10.3= 10.10.4

Os X ServerOperating system

Affected:= 5.0.3

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Authentication: None
Confidentiality: None
Integrity: None
Availability: Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

Am I affected?

dbcve checks

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

Identify installed Apache HTTP Server version

Run 'apache2 -v' or 'httpd -v' to get the exact version number

Affected if Version is exactly 2.4.10 (only this specific version is affected)
Confirm mod_proxy_fcgi module is loaded

Run 'apache2ctl -M' or 'httpd -M' and search for 'proxy_fcgi_module' in the loaded modules list

Affected if The module is listed as loaded - without this module the vulnerability cannot be triggered
Verify FastCGI proxy configuration exists

Examine Apache configuration files (httpd.conf, apache2.conf, included .conf files) for 'ProxyPass' or 'ProxyPassMatch' directives pointing to 'fcgi://' or 'unix:' backends

Affected if A proxy configuration to FastCGI backends exists - this is required for the vulnerable code path to execute
Check response header handling behavior

If FastCGI proxy is configured, send a request to a FastCGI backend and inspect if response headers are being processed. The vulnerability triggers when headers exceed expected buffer lengths

Affected if Headers from FastCGI responses exceed expected lengths and cause the server to read beyond buffer boundaries, leading to crash

You are affected only if you run Apache HTTP Server version 2.4.10 with mod_proxy_fcgi loaded and a FastCGI proxy configuration in place - the specific version match is critical since only 2.4.10 contains this flaw.

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

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Upgrade Apache HTTP Server to version 2.4.10 or later that contains the patched handle_headers function in mod_proxy_fcgi, or apply the vendor patch if available for the specific version in use.

Fix this in HTTP Server Scoped from the published advisory

Consultation2.0 h
Implementation3.0 h
Testing2.0 h
Review / QA1.0 h

8.0 hours of engineering $1,420

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2014-3583?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 5.0 Medium

Exploit likelihood EPSS, next 30 days 10.8%

Affects: HTTP Server

Remediation

Need this fixed?

Fix this in HTTP Server 8 hrs · Moderate

Typical engagement from $1,420

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2014-3583 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References