CVE-2010-5335
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 · uneditedIceWarp Webclient before 10.2.1 has a directory traversal vulnerability. This can result in loss of confidential data of IceWarp Mailserver and the operating system. Input passed via a certain parameter (script to basic/minimizer/index.php) is not properly sanitised and can therefore be exploited to browse the partition where IceWarp is installed (or the whole system) and read arbitrary 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 confidenceIceWarp Webclient before 10.2.1 contains a directory traversal vulnerability in the basic/minimizer/index.php script. The vulnerability allows unauthenticated attackers to manipulate file path parameters using '../' sequences to escape the web root and read arbitrary files from the operating system, potentially exposing sensitive mailserver data and system files.
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>= 10.0, < 10.2.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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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.
-
Verify IceWarp Webclient installationLocate IceWarp Webclient by checking for the webmail application directory, typically found in the web server's document root (e.g., /var/www/html/webmail, /www/webmail, or C:\Inetpub\wwwroot\webmail). Look for IceWarp-specific directories or files such as 'basic/', 'icewarp/', or version information files.Affected if IceWarp Webclient is found on the system and the version is unknown or falls within 10.0 to 10.2.0 range
-
Identify installed IceWarp Webclient versionCheck the version by reviewing files such as version.php, about.php, or README files in the webclient directory. Alternatively, access the web login page and inspect the footer or source for version information.Affected if The installed version is 10.0, 10.1.x, or 10.2.0 (any version >= 10.0 but < 10.2.1)
-
Locate the vulnerable scriptVerify the presence of the file 'basic/minimizer/index.php' within the IceWarp Webclient installation directory. Check if this file exists and is accessible via the web server.Affected if The file basic/minimizer/index.php exists and is web-accessible
-
Confirm vulnerability exposureTest if the directory traversal is exploitable by attempting a controlled request to basic/minimizer/index.php with a path parameter containing '../' sequences (e.g., ../../../../etc/passwd). Note: Perform this only in authorized, non-production environments as this is a live exploitation test.Affected if The server responds with file contents outside the web root, confirming the directory traversal vulnerability is present and exploitable
A system is affected if IceWarp Webclient is installed with version 10.0 through 10.2.0 and the basic/minimizer/index.php script is accessible, allowing unauthenticated directory traversal via path manipulation.
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 data10.2.1
Upgrade IceWarp Webclient to version 10.2.1 or later, which includes proper input sanitization to prevent directory traversal attacks. If immediate patching is not possible, implement web application firewall (WAF) rules to block traversal patterns in request parameters.
- Consultation3.0 h
- Implementation2.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-5335 — 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-2010-5335 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