CVE-2006-0790
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 · uneditedRockliffe MailSite 7.0 and earlier allows remote attackers to cause a denial of service by sending crafted LDAP packets to port 389/TCP, as demonstrated by the ProtoVer LDAP testsuite.
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 confidenceRockliffe MailSite 7.0 and earlier versions suffer from a denial-of-service vulnerability where remote attackers can crash the service by sending specially crafted LDAP packets to port 389/TCP. The ProtoVer LDAP testsuite demonstrated this vulnerability.
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= 4.2.10= 5= 5.3.4= 6.1.22= 7.0.31CVSS 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
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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 Rockliffe MailSite is installedCheck for MailSite installation directory (commonly in C:\Program Files\Rockliffe or C:\Rockliffe), or look for MailSite service in Windows Services (search for 'MailSite' in services.msc). On Linux/Unix, check /opt/rocksite or similar paths.Affected if Rockliffe MailSite software is found installed on the system
-
Determine installed MailSite versionCheck the version from the installation directory (often in a version.txt file, or check Add/Remove Programs in Windows). Look at the MailSite service properties or check the executable version info.Affected if Installed version matches or is older than 7.0.31, including versions 4.2.10, 5.x, 5.3.4, 6.1.22, or 7.0.x series
-
Verify LDAP service is running on port 389Run command: netstat -an | findstr :389 or use PowerShell: Get-NetTCPConnection -LocalPort 389. Also check if LDAP service is enabled in MailSite configuration.Affected if LDAP listener is active on TCP port 389 and MailSite version is vulnerable
-
Check network exposure of port 389Review firewall rules: run 'netsh firewall show all' on Windows or check iptables rules on Linux. Verify if port 389 is accessible from external/untrusted network interfaces.Affected if Port 389 is reachable from untrusted network sources (Internet or DMZ) and MailSite is vulnerable
If Rockliffe MailSite versions up to and including 7.0.31 is installed with LDAP service enabled and port 389 exposed to untrusted networks, the environment is affected by this CVE.
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 dataApply vendor patch if available, or implement network filtering/firewall rules to restrict access to port 389 from untrusted sources. Consider upgrading from this end-of-life (2006) product.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-0790 — 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-2006-0790 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