dbcve.org
Creative CloudApplication · Adobe

CVE-2016-1034

CRITICAL · 9.1 CVSS v3.0 Published 2016-04-12
Fix available
A fix is available. Upgrade to after 3.5.1.209 or later.
See remediation →
100/100
Remediation priority · Urgent
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 Sync Process in the JavaScript API for Creative Cloud Libraries in Adobe Creative Cloud Desktop Application before 3.6.0.244 allows remote attackers to read or write to arbitrary files via unspecified vectors.

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

Arbitrary file read/write vulnerability in the Sync Process of the JavaScript API for Creative Cloud Libraries within Adobe Creative Cloud Desktop Application. Attackers can read or write to arbitrary files on the targeted system due to insufficient validation in the sync functionality.

MitigationUpdate Adobe Creative Cloud Desktop Application to version 3.6.0.244 or later to patch the vulnerability. If immediate patching is not possible, consider network-level restrictions or temporarily disabling the sync feature.

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
Creative CloudApplication
Affected:<= 3.5.1.209

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Check installed Adobe Creative Cloud Desktop Application version
    Open Adobe Creative Cloud Desktop Application, click the account icon (top-right), select 'Preferences', or check 'Help' > 'About Adobe Creative Cloud' to view the version number. Alternatively, locate the application in Programs and Features (Windows) or Applications folder (macOS).
    Affected if The displayed version number is 3.5.1.209 or any version lower than 3.5.1.209 (e.g., 3.5.0.xxx, 3.4.x.x, etc.)
  2. Verify Creative Cloud Libraries sync is enabled
    In Adobe Creative Cloud Desktop Application, navigate to the Libraries panel in any Creative Cloud application (Photoshop, Illustrator, etc.) and check if sync is active. On the Desktop App, go to Preferences > Libraries and look for sync-related settings.
    Affected if The sync feature for Creative Cloud Libraries is turned on or configured to sync automatically.
  3. Confirm JavaScript API for Libraries is accessible
    Attempt to access or invoke Creative Cloud Libraries via the JavaScript API within a Creative Cloud application (such as an extension or script). This may require examining browser extensions or CEP panels that interact with CC Libraries.
    Affected if The JavaScript API for Creative Cloud Libraries is present and functional in the installed Creative Cloud applications.

The system is affected if Adobe Creative Cloud Desktop Application version is 3.5.1.209 or earlier AND the Creative Cloud Libraries sync feature is enabled or 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.

dbcve · scoped
Upgrade available Upgrade to a release after 3.5.1.209
Interim mitigation

Update Adobe Creative Cloud Desktop Application to version 3.6.0.244 or later to patch the vulnerability. If immediate patching is not possible, consider network-level restrictions or temporarily disabling the sync feature.

Recommended fix High confidence

Adobe Creative Cloud Desktop Application 3.6.0.244 or later

  1. Open Adobe Creative Cloud Desktop Application
  2. Navigate to the Help menu or Settings
  3. Check current version (should be <= 3.5.1.209 to be vulnerable)
  4. Initiate update check or manually download Creative Cloud Desktop Application version 3.6.0.244 or later from helpx.adobe.com
  5. Restart the application after update completes
  6. Verify the updated version is 3.6.0.244 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Creative Cloud Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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