dbcve.org
Wind AnalysisApplication · Digital Canal Structural

CVE-2017-7910

HIGH · 7.5 CVSS v3.0 Published 2017-06-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
A Stack-Based Buffer Overflow issue was discovered in Digital Canal Structural Wind Analysis versions 9.1 and prior. An attacker may be able to run arbitrary code by remotely exploiting an executable to perform a denial-of-service 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 confidence

A stack-based buffer overflow vulnerability in Digital Canal Structural Wind Analysis versions 9.1 and prior allows remote attackers to overwrite stack memory boundaries, potentially executing arbitrary code or causing a denial of service by sending specially crafted input to the affected executable.

MitigationApply vendor-supplied patches if available; if no patch exists, implement network segmentation to limit exposure, disable unnecessary network-facing features, and consider input validation/filtering at network perimeter devices.

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
Wind AnalysisApplication
Affected:= 9.1

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
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Confirm Digital Canal Structural Wind Analysis is installed
    Locate the application in your system by checking Program Files, Program Files (x86), or the application's default installation directory for folders named 'Digital Canal' or 'Structural Wind Analysis'. On Windows, you can also search the registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Digital Canal' or 'Wind Analysis'.
    Affected if The application is found installed on the system
  2. Determine the installed version
    Right-click the main executable (commonly named wind.exe, StructuralWindAnalysis.exe, or similar) and select Properties, then check the Details tab for the File Version. Alternatively, check the About or Help menu within the application itself for the version number.
    Affected if The installed version is 9.1 or any version prior to 9.1
  3. Verify the application exposes network services
    Check if the application is configured to listen on network ports. Review any configuration files in the application directory for network settings, port configurations, or server mode options. On Windows, run 'netstat -an' to identify if the application process has established listening ports.
    Affected if The application is configured to accept remote network connections on any port
  4. Review network exposure
    Check firewall rules and router configurations to determine if the host running Digital Canal Structural Wind Analysis is accessible from external networks. Verify whether the application ports are exposed to untrusted networks or the internet.
    Affected if The application is reachable from untrusted or external network segments

You are affected if Digital Canal Structural Wind Analysis version 9.1 or earlier is installed and the application is configured to accept remote network input.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches if available; if no patch exists, implement network segmentation to limit exposure, disable unnecessary network-facing features, and consider input validation/filtering at network perimeter devices.

Fix this in Wind Analysis Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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