CVE-2002-1083
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 · uneditedDirectory traversal vulnerabilities in ezContents 1.41 and earlier allow remote attackers to cause ezContents to (1) create directories using the Maintain Images:Add New:Create Subdirectory item, or (2) list directories using the Maintain Images file listing, via .. (dot dot) sequences.
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 confidenceezContents 1.41 and earlier contains directory traversal vulnerabilities in its image management functionality. Attackers can use '..' (dot-dot) sequences in the Maintain Images module to (1) create directories outside the intended path via the Create Subdirectory feature, and (2) list directories outside the intended path via the file listing feature. This allows unauthorized filesystem manipulation.
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.41CVSS 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
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/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 if ezContents is installedCheck your web server for the presence of ezContents by looking for directories or files containing 'ezcontents', 'ezcontents', or 'ezcontents' in the web root. Common paths include /ezcontents, /admin/ezcontents, or directories containing 'ezcontents.php'.Affected if ezContents software is found on the system
-
Determine the installed ezContents versionLocate the main ezContents PHP files (commonly index.php, version.php, or about.php) and look for a version string. Search within the file contents for 'version', '1.41', or similar version indicators. Alternatively, check for a CHANGELOG, README, or INSTALL file that may document the version.Affected if The version is 1.41 or earlier, or if no version can be determined but ezContents is present
-
Verify the Maintain Images module is accessibleLook for the image management functionality in the admin interface. Common paths include /admin/images.php, /maintain_images.php, or similar URLs containing 'image', 'maintain', or 'manage' in the ezContents admin directory. Attempt to access these URLs if the admin section is reachable.Affected if The Maintain Images or image management module exists and is accessible
-
Check if directory creation functionality existsExamine the image management files for functions that handle directory creation, such as 'mkdir', 'createdir', or 'subdirectory'. Look for form fields or parameters named 'directory', 'folder', 'path', or similar that accept user input for creating directories.Affected if The Create Subdirectory feature is present in the image management module
-
Verify the file listing feature is presentExamine the image management files for functions that read or list directories, such as 'readdir', 'scandir', or file listing loops. Look for parameters that control which directory to list, as these would be the vectors for the traversal.Affected if The file listing feature accepts path parameters that could be manipulated with '..' sequences
A system is affected if ezContents version 1.41 or earlier is installed and the image management (Maintain Images) module with directory creation and listing features is accessible.
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 dataImplement strict input validation to reject path traversal sequences ('..') and use basename() or canonical path functions to ensure all file operations remain within the intended directory. Consider adding access controls to these administrative functions.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-1083 — 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-2002-1083 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