CVE-2008-3395
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 · uneditedCalacode @Mail 5.41 on Linux uses weak world-readable permissions for (1) webmail/libs/Atmail/Config.php and (2) webmail/webadmin/.htpasswd, which allows local users to obtain sensitive information by reading these files. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.
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 · moderate confidenceCalacode @Mail 5.41 on Linux stores sensitive files with weak world-readable permissions. The configuration file webmail/libs/Atmail/Config.php likely contains database credentials or other secrets, and webmail/webadmin/.htpasswd contains HTTP authentication credentials. Any local user on the system can read these files by simply accessing them with standard file read 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= 5.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
- 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.
-
Confirm Atmail 5.41 installationLocate the Atmail installation by searching for the webmail directory structure. Common paths include /var/www/html/, /var/www/, or the document root of your web server. Verify the presence of webmail/libs/Atmail/Config.phpAffected if The file webmail/libs/Atmail/Config.php exists on the system, indicating Atmail is installed
-
Check Config.php permissionsRun: ls -la webmail/libs/Atmail/Config.php (adjust path if your installation is in a different location). Examine the permission string (e.g., -rw-r--r--)Affected if The permission bits allow read access for 'others' (the third r in rw-r--r-- or similar, indicating o+r). For example, 644 or 644+ allows any local user to read the file.
-
Check .htpasswd permissionsRun: ls -la webmail/webadmin/.htpasswd (adjust path if your installation is in a different location). Examine the permission stringAffected if The permission bits allow read access for 'others' (o+r). Any permission ending in 'r' for the final triplet means world-readable.
The system is affected if Calacode Atmail 5.41 is installed AND either webmail/libs/Atmail/Config.php or webmail/webadmin/.htpasswd has world-readable permissions (o+r).
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 dataChange file permissions to restrictive settings (e.g., chmod 600 or 640) on both webmail/libs/Atmail/Config.php and webmail/webadmin/.htpasswd to ensure only the web server process owner and authorized administrators can read them.
- Consultation1.0 h
- Implementation1.0 h
- Testing0.5 h
- Review / QA0.5 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-2008-3395 — 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-2008-3395 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