Creative CloudApplication · Adobe

CVE-2019-7093

HIGH · 7.8 CVSS v3.0 Published 2019-05-24
Fix available
A fix is available. Upgrade to after 4.7.0.400 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
Creative Cloud Desktop Application (installer) versions 4.7.0.400 and earlier have an insecure library loading (dll hijacking) vulnerability. Successful exploitation could lead to privilege escalation.

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 Creative Cloud Desktop Application installer versions 4.7.0.400 and earlier is vulnerable to DLL hijacking, where the application loads malicious DLLs from an insecure location instead of the expected system directories. Successful exploitation allows an attacker to execute arbitrary code with elevated privileges.

MitigationUpdate the Creative Cloud Desktop Application to a version later than 4.7.0.400. In enterprise environments, ensure the installer is run from trusted directories and implement application whitelisting to prevent loading of untrusted DLLs.

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:<= 4.7.0.400

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

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 Creative Cloud Desktop Application version
    Open Windows Control Panel > Programs and Features, locate 'Adobe Creative Cloud' or 'Adobe Creative Cloud Desktop Application', and note the version column. Alternatively, right-click the application's executable in its install directory, select Properties, and check the Details tab for version info.
    Affected if The displayed version is 4.7.0.400 or any version number lower than 4.7.0.400 (for example, 4.6.0.200, 4.5.1.100, etc.).
  2. Verify installer presence
    Search for Creative Cloud installer files on the system. Common locations include the user's Downloads folder, a designated software distribution folder, or within the Creative Cloud install directory (typically C:\Program Files\Adobe\Adobe Creative Cloud\). Look for files named setup.exe, AdobeCreativeCloudInstaller.exe, or similar installer executables.
    Affected if The installer executable exists on the system and is version 4.7.0.400 or earlier, as the vulnerability affects the installer component specifically.
  3. Confirm DLL loading behavior
    Attempt to run the Creative Cloud installer or application while monitoring DLL loads using Process Monitor (from Sysinternals). Filter by process name and look for DLLs loaded from user-writable directories such as the application directory, TEMP folder, or user profile folders rather than only system directories like C:\Windows\System32.
    Affected if The application or installer loads DLLs from locations outside the trusted system directories, which indicates the insecure DLL loading behavior this CVE exploits.

Your environment is affected if the Creative Cloud Desktop Application or its installer version is 4.7.0.400 or earlier, and the application loads DLLs from insecure locations.

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
Upgrade available Upgrade to a release after 4.7.0.400
Interim mitigation

Update the Creative Cloud Desktop Application to a version later than 4.7.0.400. In enterprise environments, ensure the installer is run from trusted directories and implement application whitelisting to prevent loading of untrusted DLLs.

Fix this in Creative Cloud Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-7093 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-7093 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