dbcve.org
Dream ReportApplication · Dreamreport

CVE-2011-4039

HIGH · 9.3 CVSS v2.0 Published 2012-02-10
Fix available
A fix is available. Upgrade to after 3.43 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
Invensys Wonderware HMI Reports 3.42.835.0304 and earlier, as used in Ocean Data Systems Dream Report before 4.0 and other products, allows user-assisted remote attackers to execute arbitrary code via a malformed file that triggers a "write access violation."

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 confidence

A file parsing vulnerability in Invensys Wonderware HMI Reports and Ocean Data Systems Dream Report allows remote code execution through malformed files that trigger a write access violation. The user-assisted attack requires victim interaction (opening a crafted file), and the resulting arbitrary code execution carries severe impact due to the high CVSS score.

MitigationApply vendor patches: upgrade Wonderware HMI Reports beyond version 3.42.835.0304 and Dream Report to version 4.0 or later. Until patched, enforce strict controls on file imports and restrict HMI systems from untrusted network paths.

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
Dream ReportApplication
Affected:<= 3.43= 3.21= 3.41= 3.42
Wonderware Hmi ReportsApplication
Affected:<= 3.42.835.0304

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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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 if Dream Report is installed
    Check for Dream Report installation by looking for the program in Add/Remove Programs (Windows) or searching for Dream Report executable files (typically in Program Files folder)
    Affected if Dream Report is found installed on the system
  2. Check Dream Report version
    Right-click the Dream Report executable or shortcut, select Properties, and check the Version tab; alternatively, open Dream Report and navigate to Help > About to view the version number
    Affected if The installed version is 3.21, 3.41, 3.42, or 3.43 or lower (any version listed as affected)
  3. Identify if Wonderware HMI Reports is installed
    Check for Wonderware HMI Reports in Add/Remove Programs or search for Wonderware HMI Reports related files in the installation directory (typically under Wonderware folder in Program Files)
    Affected if Wonderware HMI Reports is found installed on the system
  4. Check Wonderware HMI Reports version
    Open Wonderware HMI Reports and navigate to Help > About, or check the version property of the main executable file in the installation folder
    Affected if The installed version is 3.42.835.0304 or earlier
  5. Verify file import or report parsing functionality exists
    Check if the installed software has the capability to import, open, or parse report files or templates - this is the attack vector for this vulnerability
    Affected if The file import or report parsing feature is present and accessible to users

A user is affected if either Dream Report version 3.21, 3.41, 3.42, or 3.43 (or any version <= 3.43) or Wonderware HMI Reports version 3.42.835.0304 or earlier is installed and the file parsing/import feature is 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.43
Interim mitigation

Apply vendor patches: upgrade Wonderware HMI Reports beyond version 3.42.835.0304 and Dream Report to version 4.0 or later. Until patched, enforce strict controls on file imports and restrict HMI systems from untrusted network paths.

Recommended fix Moderate confidence

Dream Report 4.0 or later; Wonderware HMI Reports newer than 3.42.835.0304

  1. 1. Identify the current installed version of Dream Report or Wonderware HMI Reports
  2. 2. If running Dream Report version 3.43 or earlier (including 3.21, 3.41, 3.42), upgrade to Dream Report version 4.0 or later
  3. 3. If running Wonderware HMI Reports version 3.42.835.0304 or earlier, upgrade to a version newer than 3.42.835.0304
  4. 4. After upgrade, verify that the application runs correctly and test the malformed file handling
Caveat Verify compatibility with existing reports and integrations after upgrading to version 4.0, as this is a major version change

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

Fix this in Dream Report Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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