dbcve.org
Web StudioApplication · Indusoft

CVE-2011-1900

HIGH · 10.0 CVSS v2.0 Published 2011-05-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Directory traversal vulnerability in NTWebServer in InduSoft Web Studio 6.1 and 7.x before 7.0+Patch 1 allows remote attackers to execute arbitrary code via an invalid request.

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 allows remote attackers to traverse filesystem paths via malformed requests, enabling execution of arbitrary code. The vulnerability affects versions 6.1 and 7.x prior to 7.0+Patch 1.

MitigationApply vendor patch (7.0+Patch 1 or later) to upgrade InduSoft Web Studio, and review NTWebServer configuration to restrict filesystem access permissions.

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:= 6.1= 7.0

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

AV:N/AC:L/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 installed InduSoft Web Studio version
    Check the program version through Windows Programs and Features, or look for version info in the InduSoft installation directory (typically in the main executable or About dialog)
    Affected if Version is 6.1 or 7.0 (versions prior to 7.0+Patch 1)
  2. Confirm NTWebServer component is present
    Check for NTWebServer.exe in the InduSoft installation directory (commonly in Bin or Server subfolder) or verify NTWebServer service is listed in Windows Services
    Affected if NTWebServer.exe exists or the NTWebServer service is registered
  3. Verify NTWebServer is running or enabled
    Open Windows Services console (services.msc) and check if NTWebServer service status is Running, or check if the NTWebServer port is listening (default web ports 80/443)
    Affected if NTWebServer service is running or the web server port is actively listening
  4. Check NTWebServer configuration files
    Locate NTWebServer configuration files in the installation directory (typically .ini or .cfg files in Config or Settings subfolder) and inspect for security-related settings such as path restrictions or allowed directories
    Affected if No path restriction settings are defined or traversal is explicitly allowed in configuration
  5. Test for directory traversal exposure
    If NTWebServer is accessible, send a crafted HTTP request with traversal sequences (such as ../../../windows/system32) to the web server endpoint and observe if the response differs from a standard error or if file content is returned
    Affected if The web server returns file content or directory listings outside the intended web root directory

The environment is affected if InduSoft Web Studio version 6.1 or 7.0 is installed AND the NTWebServer component is enabled/running, allowing unauthenticated directory traversal access.

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

Apply vendor patch (7.0+Patch 1 or later) to upgrade InduSoft Web Studio, and review NTWebServer configuration to restrict filesystem access permissions.

Recommended fix Moderate confidence

InduSoft Web Studio 7.0 with Patch 1

  1. Identify the current installed version of InduSoft Web Studio
  2. Contact InduSoft technical support or visit the official support portal to obtain Patch 1 for version 7.0
  3. Apply the patch according to the vendor's installation instructions, typically by running the patch installer with administrative privileges
  4. Verify the patch was applied successfully by checking the version information
  5. Restart the NTWebServer service if required by the patch

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

Fix this in Web Studio Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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