dbcve.org
Data SynchronizerApplication · Novell

CVE-2011-3014

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
The Mobility Pack before 1.2 in Novell Data Synchronizer 1.x through 1.1.2 build 428 does not properly restrict caching of HTTPS responses, which makes it easier for remote attackers to obtain sensitive information by leveraging an unattended workstation.

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

The Mobility Pack in Novell Data Synchronizer 1.x through 1.1.2 build 428 does not properly restrict caching of HTTPS responses. Sensitive data (authentication tokens, session data, or other confidential information) transmitted over HTTPS is being cached by the browser or proxy, persisting beyond the user's session. An attacker with physical access to an unattended workstation can retrieve this cached sensitive information.

MitigationConfigure the web server or application to set proper HTTP cache-control headers (Cache-Control: no-store, no-cache, must-revalidate and Pragma: no-cache) for all HTTPS responses containing sensitive data to prevent browser caching of confidential information.

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. Identify installed Data Synchronizer or Mobility Pack version
    Check the installed package version using the system package manager, or look in the application installation directory for version information. Common locations include /opt/novell/datasync or the program's About/Version dialog.
    Affected if The installed version matches 1.0.0, 1.1.0, 1.1.1, or 1.1.2 (or any 1.x through 1.1.2 build 428)
  2. Inspect HTTPS response headers for sensitive endpoints
    Use a browser developer tool or HTTP proxy (such as Burp Suite or Fiddler) to capture HTTPS responses from the Data Synchronizer / Mobility Pack web interface during authentication and session use. Examine the HTTP response headers for Cache-Control and Pragma directives.
    Affected if HTTPS responses containing authentication tokens, session data, or other sensitive information lack the headers Cache-Control: no-store, no-cache, must-revalidate AND Pragma: no-cache
  3. Review web server configuration for caching directives
    Examine the web server configuration files (such as Apache httpd.conf, nginx.conf, or the application-specific config) that serve the Data Synchronizer / Mobility Pack HTTPS endpoints. Look for cache-control settings applied to sensitive resources.
    Affected if The configuration does not enforce no-store/no-cache headers for HTTPS responses carrying sensitive user data
  4. Check browser cache for persisted sensitive data
    On a test workstation, log into the Mobility Pack interface, then examine the browser cache directory directly or use browser developer tools to view cached HTTPS resources. Search for cached files containing authentication tokens, session identifiers, or user-specific data.
    Affected if Sensitive authentication or session data from HTTPS responses is found cached on disk

You are affected if the installed version is 1.0.0 through 1.1.2 AND HTTPS responses with sensitive data are being cached due to missing or improper cache-control headers.

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

Configure the web server or application to set proper HTTP cache-control headers (Cache-Control: no-store, no-cache, must-revalidate and Pragma: no-cache) for all HTTPS responses containing sensitive data to prevent browser caching of confidential information.

Fix this in Data Synchronizer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-3014 — 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-3014 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