NginxWeb server / proxy · F5
CVE-2014-0133
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 · uneditedHeap-based buffer overflow in the SPDY implementation in nginx 1.3.15 before 1.4.7 and 1.5.x before 1.5.12 allows remote attackers to execute arbitrary code via a crafted request.
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 confidenceHeap-based buffer overflow in nginx's SPDY protocol implementation allows remote attackers to potentially execute arbitrary code via specially crafted SPDY requests. The vulnerability exists in nginx versions 1.3.15 through 1.4.6 and 1.5.x through 1.5.11.
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
NginxWeb server / proxy
>= 1.3.15, < 1.4.7>= 1.5.0, <= 1.5.11= 13.1CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Check nginx versionRun 'nginx -v' or 'nginx -V' to display the installed version, or check the package manager (rpm -q nginx, dpkg -l nginx, etc.)Affected if Version is 1.3.15 through 1.4.6, or 1.5.0 through 1.5.11
-
Verify SPDY module is loadedRun 'nginx -V 2>&1 | grep -i spdy' to see if the SPDY module was compiled in, or check for 'ngx_http_spdy_module' in the outputAffected if SPDY module appears in the compiled modules list
-
Check configuration for active SPDY usageInspect nginx configuration files (typically in /etc/nginx/) for 'listen ... spdy' directives in server blocks, or search using 'grep -r spdy /etc/nginx/'Affected if Any 'listen' directive includes the 'spdy' parameter, indicating SPDY is enabled for that virtual host
-
Confirm runtime SPDY module loadingCheck if nginx is running and inspect loaded modules via 'ps aux | grep nginx' then check for SPDY-related configuration in active running config using 'nginx -T' if availableAffected if SPDY is configured and nginx is running with SPDY enabled
The environment is affected if nginx version falls within 1.3.15-1.4.6 or 1.5.0-1.5.11 AND the SPDY module is both compiled in and actively configured via 'spdy' parameter in listen directives.
Generated from the published advisory. Verify against your own configuration.
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 data1.4.7
Upgrade nginx to version 1.4.7 or later (or 1.5.12 or later). If immediate upgrade is not feasible, disable the SPDY module as a temporary workaround until patching can be completed.
Fix this in Nginx
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0133 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-0133 in production — separate from our analysis above.
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.
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.
- 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