dbcve.org
Data SynchronizerApplication · Novell

CVE-2011-3013

MEDIUM · 5.0 CVSS v2.0 Published 2011-08-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
WebAdmin in the Mobility Pack before 1.2 in Novell Data Synchronizer 1.x through 1.1.2 build 428 supports weak SSL ciphers, which makes it easier for remote attackers to obtain access via a brute-force attack.

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 confidence

WebAdmin interface in Novell Data Synchronizer (versions 1.x through 1.1.2 build 428) is configured to support weak SSL cipher suites, enabling remote attackers to perform brute-force attacks against encrypted sessions to potentially recover credentials or plaintext data.

MitigationDisable weak SSL ciphers (e.g., export-grade, NULL, single-DES, RC4) in the WebAdmin SSL configuration and enable only strong cipher suites (AES, 3DES, TLS 1.0+) or upgrade Mobility Pack to version 1.2 or later.

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
Data SynchronizerApplication
Affected:= 1.0.0= 1.1.0= 1.1.1= 1.1.2
Mobility PackApplication
Affected:= 1.0= 1.1= 1.1.1= 1.1.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify if Novell Data Synchronizer or Mobility Pack is installed
    Locate the installed product on the system - look for Data Synchronizer or Mobility Pack installation directories or check system inventory for Novell software packages.
    Affected if Either Novell Data Synchronizer or Novell Mobility Pack is present on the system.
  2. Determine the installed version of the product
    Check the installed version of Novell Data Synchronizer or Mobility Pack - typical locations include the application itself, installed programs list, or version files in the installation directory.
    Affected if The installed version is 1.0.0, 1.1.0, 1.1.1, or 1.1.2 for either product.
  3. Locate the WebAdmin SSL configuration file
    Find the SSL configuration file used by the WebAdmin interface - this is typically in the Data Synchronizer or Mobility Pack configuration directory, often named ssl.conf, webadmin.conf, or similar.
    Affected if A WebAdmin SSL configuration file exists and is accessible for inspection.
  4. Inspect SSL cipher configuration for weak suites
    Open the WebAdmin SSL configuration file and examine the configured cipher suites - look for settings that include export-grade ciphers (EXP*), NULL encryption (NULL*), single-DES (DES*), or RC4 algorithms (RC4*).
    Affected if The SSL configuration contains weak cipher suites such as export-grade, NULL, single-DES, or RC4.
  5. Verify if WebAdmin interface is network accessible
    Check if the WebAdmin interface port (commonly 443 or 8443) is listening and accessible from the network or if it has been restricted to localhost only.
    Affected if The WebAdmin interface is network-accessible without IP restriction.

You are affected if either Novell Data Synchronizer (versions 1.0.0 to 1.1.2) or Novell Mobility Pack (versions 1.0 to 1.1.2) is installed AND the WebAdmin SSL configuration contains weak cipher suites that are network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable weak SSL ciphers (e.g., export-grade, NULL, single-DES, RC4) in the WebAdmin SSL configuration and enable only strong cipher suites (AES, 3DES, TLS 1.0+) or upgrade Mobility Pack to version 1.2 or later.

Fix this in Data Synchronizer Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-3013 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2011-3013 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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