dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 6 May 2022.
Web StudioApplication · Indusoft

CVE-2014-0780

CRITICAL · 9.8 CVSS v3.1 Published 2014-04-25
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

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
Directory traversal vulnerability in NTWebServer in InduSoft Web Studio 7.1 before SP2 Patch 4 allows remote attackers to read administrative passwords in APP files, and consequently execute arbitrary code, via unspecified web requests.

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

Directory traversal vulnerability in NTWebServer component of InduSoft Web Studio 7.1 allows remote attackers to read administrative passwords stored in APP configuration files via specially crafted web requests, enabling subsequent arbitrary code execution.

MitigationApply InduSoft Web Studio 7.1 SP2 Patch 4 or later. If immediate patching is not feasible, restrict network access to the NTWebServer service and disable remote administrative interfaces.

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
Web StudioApplication
Affected:= 7.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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify InduSoft Web Studio 7.1 installation
    Check the Windows registry under HKLM\SOFTWARE\InduSoft\Web Studio or look for the installation directory (commonly C:\Program Files\InduSoft\Web Studio 7.1).
    Affected if InduSoft Web Studio 7.1 is installed on the system.
  2. Confirm the installed version
    Locate the version information in the About dialog or check the file version of the main executable (Studio.exe) in the installation directory.
    Affected if The installed version is 7.1 but does not have SP2 Patch 4 applied (version would show as 7.1.0.0 through 7.1.0.3 or similar pre-patch build numbers).
  3. Check if NTWebServer component is enabled
    Open Windows Services and look for a service named NTWebServer, or check if the web server is listening on port 80/443 via netstat -an | findstr LISTENING.
    Affected if NTWebServer is running and the web server port is in a listening state, exposing the service to network requests.
  4. Verify remote accessibility of the web server
    From an external system or using a browser, attempt to access the NTWebServer interface at the system's IP address (http://<IP>/).
    Affected if The NTWebServer interface is reachable from the network without authentication.
  5. Inspect APP configuration files for exposure
    Check the application data folders (typically in the project or config directories) for any APP files that may have been accessed or modified. Review log files in the NTWebServer directory for suspicious traversal requests (e.g., ../../../).
    Affected if APP configuration files exist and contain administrative credentials that could have been accessed via directory traversal, or web server logs show traversal attempts.

The system is affected if InduSoft Web Studio 7.1 is installed without SP2 Patch 4 and the NTWebServer component is accessible over the network, allowing unauthenticated remote attackers to read credential-containing APP files.

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
Patch available Apply the vendor patch
Vendor patch ics-cert.us-cert.gov →
Interim mitigation

Apply InduSoft Web Studio 7.1 SP2 Patch 4 or later. If immediate patching is not feasible, restrict network access to the NTWebServer service and disable remote administrative interfaces.

Recommended fix High confidence

InduSoft Web Studio 7.1 SP2 Patch 4

  1. Obtain InduSoft Web Studio 7.1 SP2 Patch 4 from the official InduSoft download center (download.indusoft.com) or authorized support channels
  2. Backup the current InduSoft Web Studio installation and all project files
  3. Apply SP2 Patch 4 to the existing installation by running the patch executable with administrative privileges
  4. Follow any specific vendor installation instructions provided with the patch
  5. Restart the NTWebServer service after patch application
  6. Verify the patch was successfully applied by checking the version information in Web Studio

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

Fix this in Web Studio Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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