NginxWeb server / proxy · F5
CVE-2013-0337
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 · uneditedThe default configuration of nginx, possibly 1.3.13 and earlier, uses world-readable permissions for the (1) access.log and (2) error.log files, which allows local users to obtain sensitive information by reading the files.
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 confidenceThe default nginx configuration (versions 1.3.13 and earlier) creates access.log and error.log files with world-readable permissions (typically 0644), allowing any local user on the system to read sensitive information such as client IP addresses, requested URLs, potential authentication credentials in query strings, and server-side error details.
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.13= 1.0.0= 1.0.1= 1.0.2= 1.0.3= 1.0.4= 1.0.5= 1.0.6= 1.0.7= 1.0.8= 1.0.9= 1.0.10CVSS 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.
-
Identify nginx versionRun 'nginx -v' or check the package version with 'rpm -q nginx' or 'dpkg -l nginx' depending on your systemAffected if The version is 1.3.13 or earlier, or matches 1.0.0 through 1.0.10
-
Locate nginx log filesCheck the nginx configuration for log file paths using 'grep -r 'log ' /etc/nginx/' or look at the default error_log and access_log directivesAffected if Log files are found at default locations without custom permission settings
-
Check access.log file permissionsRun 'ls -la /var/log/nginx/access.log' or the actual path from your configurationAffected if The file permissions are 0644 (world-readable) or more permissive
-
Check error.log file permissionsRun 'ls -la /var/log/nginx/error.log' or the actual path from your configurationAffected if The file permissions are 0644 (world-readable) or more permissive
-
Check nginx log directory permissionsRun 'ls -la /var/log/nginx/' to inspect directory permissionsAffected if The directory has world-readable permissions that allow any local user to list or access log files
You are affected if nginx version is 1.3.13 or earlier (or 1.0.x between 1.0.0 and 1.0.10) AND log files or their directory have world-readable permissions (0644 or wider).
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 dataRestrict log file permissions to owner-only (0600 or 0640) and ensure the nginx process user owns the log directory; also update logrotate configuration to maintain restrictive permissions on rotated logs.
Fix this in Nginx
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0337 — 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-2013-0337 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