Advantech StudioApplication · Advantech

CVE-2013-1627

HIGH · 7.8 CVSS v2.0 Published 2013-03-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/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
Absolute path traversal vulnerability in NTWebServer.exe in Indusoft Studio 7.0 and earlier and Advantech Studio 7.0 and earlier allows remote attackers to read arbitrary files via a full pathname in an argument to the sub_401A90 CreateFileW function.

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

Absolute path traversal vulnerability in NTWebServer.exe allows remote attackers to read arbitrary files by passing full pathnames (e.g., C:\Windows\System32\config\sam) to the sub_401A90 CreateFileW function. The application fails to validate or restrict path inputs, enabling directory traversal beyond intended boundaries.

MitigationUpdate to a patched version of Indusoft Studio/Advantech Studio if available; otherwise disable or restrict access to the NTWebServer.exe service and implement network segmentation to limit exposure.

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
Advantech StudioApplication
Affected:= 6.1
Web StudioApplication
Affected:= 6.1= 7.0= 7.0b2

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

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

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 or Advantech Studio version
    Check the application version through Windows Programs and Features, or locate the installation directory (typically C:\Program Files\Indusoft or C:\Program Files\Advantech) and check version info of the main executable
    Affected if Installed version matches 6.1, 7.0, or 7.0b2 of Indusoft Web Studio or 6.1 of Advantech Studio
  2. Locate NTWebServer.exe in the installation directory
    Search for NTWebServer.exe in the installation folder, commonly found in the bin or root directory of the Studio installation
    Affected if NTWebServer.exe exists in the Indusoft/Advantech Studio installation folder
  3. Check if NTWebServer service is running
    Open Windows Services (services.msc) and look for a service related to NTWebServer, or use command 'sc query' to enumerate running services
    Affected if NTWebServer.exe is running as a Windows service or process
  4. Verify web server component is accessible
    Attempt to access the NTWebServer HTTP port (default port 80 or configured port) on localhost using a browser or curl command
    Affected if The web server interface is accessible and responds to HTTP requests
  5. Test for path traversal vulnerability
    Send a crafted HTTP request to NTWebServer with a full Windows path such as 'GET /../../../../windows/win.ini' or 'GET /C:\Windows\win.ini' and observe if the file contents are returned
    Affected if The server returns contents of files outside the web root directory, confirming the path traversal flaw exists

User is affected if they have Indusoft Web Studio 6.1/7.0/7.0b2 or Advantech Studio 6.1 installed with NTWebServer.exe running and accessible, and the path traversal test successfully reads arbitrary 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of Indusoft Studio/Advantech Studio if available; otherwise disable or restrict access to the NTWebServer.exe service and implement network segmentation to limit exposure.

Fix this in Advantech Studio Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-1627 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-1627 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