CVE-2005-3132
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 · uneditedMERAK Mail Server 8.2.4r with Icewarp Web Mail 5.5.1, and possibly earlier versions, allows remote attackers to obtain sensitive information via a direct request to bwlist_inc.html, which reveals the path in an error message.
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 confidenceMERAK Mail Server 8.2.4r with Icewarp Web Mail 5.5.1 exposes the full server file path in an error message when a remote attacker directly requests the bwlist_inc.html file. This information disclosure can aid attackers in reconnaissance and path mapping for further exploitation.
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= 5.5.1= 8.2.4rCVSS 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 Icewarp Web Mail or Merak Mail Server installationCheck for Icewarp or Merak web services running on the server, typically on ports 80/443 or the Icewarp default port 32000Affected if Either Icewarp Web Mail or Merak Mail Server with webmail is installed
-
Check installed version of Icewarp Web MailInspect the Icewarp installation directory or check the webmail login page source for version information, typically found in 'about' or 'info' pagesAffected if Version is exactly 5.5.1
-
Check installed version of Merak Mail ServerCheck Merak Mail Server installation or admin interface for version details, often visible in service info or registryAffected if Version is exactly 8.2.4r
-
Locate bwlist_inc.html in web-accessible directoriesSearch web server document root directories (htdocs, html, webmail) for the file bwlist_inc.htmlAffected if The file exists in a web-accessible directory
-
Test for path disclosure vulnerabilitySend an HTTP GET request directly to bwlist_inc.html (e.g., http://target/bwlist_inc.html) and examine the error responseAffected if The error message or response reveals the full server file system path
You are affected if you run Icewarp Web Mail 5.5.1 or Merak Mail Server 8.2.4r AND the bwlist_inc.html file is accessible via HTTP and exposes the server file path when requested.
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 dataRemove or rename the bwlist_inc.html file from the web accessible directory, or configure the web server to return generic error pages instead of verbose path information.
- 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-2005-3132 — 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-2005-3132 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