CVE-2011-2223
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 · uneditedThe Mobility Pack before 1.2 in Novell Data Synchronizer 1.x through 1.1.2 build 428 sends the Admin LDAP password in cleartext, which allows remote attackers to obtain sensitive information by sniffing the network.
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 confidenceThe Mobility Pack component (versions 1.x through 1.1.2 build 428) of Novell Data Synchronizer transmits the Admin LDAP password in cleartext over the network. An attacker with the ability to sniff network traffic can intercept and read the plaintext LDAP administrative credentials.
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.0.0= 1.1.0= 1.1.1= 1.1.2= 1.0= 1.1= 1.1.1= 1.1.2CVSS 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 installed Mobility Pack or Data Synchronizer versionCheck the installed package version using the system's package manager or look for version information in the product's about or version dialog. For command-line, try: rpm -q datasync or dpkg -l | grep -i datasync, or look in /opt/novell/datasync/ for version files.Affected if The installed version matches 1.0.0, 1.1.0, 1.1.1, 1.1.2 for Data Synchronizer or 1.0, 1.1, 1.1.1, 1.1.2 for Mobility Pack.
-
Verify LDAP communication configurationExamine the LDAP configuration for the Mobility Pack or Data Synchronizer service. Check configuration files in /opt/novell/datasync/ or /etc/datasync/ for LDAP connection settings. Look for parameters controlling encryption such as 'use_tls', 'use_ssl', or 'ldap://' vs 'ldaps://'.Affected if LDAP connections are configured without TLS or SSL encryption (plain LDAP on port 389 instead of LDAPS on port 636 or TLS).
-
Confirm Admin LDAP credentials are in useVerify that the Mobility Pack is configured to use an LDAP bind with administrative credentials. Check the LDAP configuration file for a bindDN or adminDN setting that specifies an administrator-level LDAP account.Affected if The product is configured to authenticate to LDAP using an administrative bind account.
You are affected if your installed Mobility Pack or Data Synchronizer version is one of the listed affected versions AND LDAP communication is not encrypted with TLS/SSL, allowing network sniffers to capture the admin password in plaintext.
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 dataUpgrade Mobility Pack to version 1.2 or later which implements encrypted password transmission, or ensure all LDAP communication is tunneled through TLS/SSL to prevent credential exposure.
- 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-2011-2223 — 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-2011-2223 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