CVE-2019-7097
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 · uneditedAdobe Dreamweaver versions 19.0 and earlier have an insecure protocol implementation vulnerability. Successful exploitation could lead to sensitive data disclosure if smb request is subject to a relay 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 · moderate confidenceAdobe Dreamweaver versions 19.0 and earlier contain an insecure SMB protocol implementation that fails to properly protect SMB authentication requests from relay attacks. When Dreamweaver makes SMB requests, the lack of appropriate protections (such as SMB signing or channel binding) allows an attacker to intercept and relay authentication credentials to access sensitive data.
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<= 19.0CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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.
-
Confirm Dreamweaver installationCheck if Adobe Dreamweaver is installed on the system. On Windows, look in Program Files or check the registry under HKLM\Software\Adobe\Dreamweaver. On macOS, check /Applications/ for Dreamweaver.app.Affected if Dreamweaver is not installed - not affected.
-
Determine installed Dreamweaver versionOpen Dreamweaver and go to Help > About Adobe Dreamweaver, or check the version in the application metadata. Compare the version number to the affected range of 19.0 and earlier.Affected if Version is 19.0 or earlier - potentially affected.
-
Identify SMB usage in DreamweaverReview Dreamweaver site definitions and server connections. Check if any defined servers use SMB/CIFS protocol (often indicated by UNC paths like \\server\share or smb:// prefixes in site settings).Affected if SMB-based remote server connections are configured in Dreamweaver - vulnerable to relay attacks.
-
Verify SMB client protection statusSince the vulnerability is in Dreamweaver's SMB client implementation lacking SMB signing and channel binding, inspect any network traffic when Dreamweaver connects to SMB servers to confirm whether authentication is being signed.Affected if SMB connections from Dreamweaver do not use signing or channel binding - actively vulnerable.
A user is affected if Dreamweaver version 19.0 or earlier is installed AND SMB functionality (remote file access via SMB) is used, allowing credentials to be relayable due to missing SMB signing protections in Dreamweaver's client.
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 dataImplement SMB signing enforcement and extended protection for NTLM authentication in Dreamweaver's SMB client implementation to prevent relay attacks. Organizations should also enable SMB signing on their network infrastructure to protect against credential relay.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7097 — 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-2019-7097 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