CVE-2013-0332
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 · uneditedMultiple directory traversal vulnerabilities in ZoneMinder 1.24.x before 1.24.4 allow remote attackers to read arbitrary files via a .. (dot dot) in the (1) view, (2) request, or (3) action parameter.
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 confidenceZoneMinder 1.24.x before 1.24.4 contains multiple directory traversal vulnerabilities allowing remote attackers to read arbitrary files via '..' sequences in the view, request, or action parameters. This is a classic path traversal flaw where user-supplied input is not properly sanitized before being used in file path operations.
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= 1.24.0= 1.24.1= 1.24.2= 1.24.3CVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 installed ZoneMinder versionRun 'zmversion' command or check /usr/share/zoneminder/VERSION file, or query the web interface for version infoAffected if Version is 1.24.0, 1.24.1, 1.24.2, or 1.24.3 (versions before 1.24.4)
-
Confirm ZoneMinder web service is runningCheck if Apache/Nginx is serving ZoneMinder (look for port 80/443 listeners, or check process list for httpd/apache2/nginx)Affected if Web interface is exposed and running on any port
-
Verify the vulnerable parameters are accessibleTest accessing a known ZoneMinder PHP script (e.g., /index.php?view=..) to confirm the web application processes these parametersAffected if The view, request, or action parameters accept input without rejection of '..' sequences
-
Check for input validation in PHP sourceInspect ZoneMinder PHP files in /usr/share/zoneminder or /var/www/html for sanitization of view/request/action parameters (look for code that handles these GET/POST params)Affected if No validation exists to strip or reject '..' sequences from user-supplied parameters
You are affected if ZoneMinder version 1.24.0-1.24.3 is installed AND the web interface is accessible, as the path traversal flaw requires user-controlled input in view/request/action parameters to reach the vulnerable code.
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 dataUpgrade to ZoneMinder 1.24.4 or later to obtain the patched version. As an interim measure, implement strict input validation rejecting '..' sequences and consider restricting web server access through network-level controls.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2013-0332 — 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-0332 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