CVE-2007-6033
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 · uneditedInvensys Wonderware InTouch 8.0 creates a NetDDE share with insecure permissions (Everyone/Full Control), which allows remote authenticated attackers, and possibly anonymous users, to execute arbitrary programs.
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 confidenceWonderware InTouch 8.0 creates a NetDDE share with insecure permissions, specifically granting Everyone/Full Control access. This misconfiguration allows any authenticated remote attacker (and potentially anonymous users) to execute arbitrary programs on the system by leveraging the overly permissive share.
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= 8.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Wonderware InTouch 8.0 is installedCheck installed programs list or look for Wonderware InTouch 8.0 installation directory. Compare your installed version to the affected range (version 8.0 specifically).Affected if Wonderware InTouch version 8.0 is installed on the system
-
Confirm NetDDE service is runningOpen Services console (services.msc) and check if the NetDDE service exists and is running, or run 'net start' command and look for NetDDE in the list.Affected if NetDDE service is running or enabled on the system
-
Identify NetDDE shareOpen Computer Management > Shared Folders > Shares, or run 'net share' command to list all network shares. Look for any NetDDE-related share (commonly named 'NETDDE' or similar).Affected if A NetDDE share exists on the system
-
Examine NetDDE share permissionsRight-click the NetDDE share in Computer Management, select Properties, then go to the Share Permissions tab. Check which users and groups are listed and their permission levels.Affected if The Everyone group is granted Full Control or excessive permissions on the NetDDE share
-
Verify access from remote clientsFrom a remote system, attempt to access the NetDDE share using 'net use \\hostname\NETDDE' or similar share name discovered in step 3, without providing credentials if possible.Affected if Unauthenticated or low-privilege users can access the NetDDE share
If Wonderware InTouch 8.0 is installed with NetDDE service running and a NetDDE share exists with Everyone/Full Control permissions, the system is affected by this vulnerability.
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 dataRestrict NetDDE share permissions by removing the Everyone group and applying least-privilege access controls; verify that only required service accounts have access to the share.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-6033 — 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-2007-6033 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