CVE-2023-0956
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 · uneditedExternal input could be used on TEL-STER TelWin SCADA WebInterface to construct paths to files and directories without properly neutralizing special elements within the pathname, which could allow an unauthenticated attacker to read files on the system.
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 confidencePath traversal vulnerability in TEL-STER TelWin SCADA WebInterface allows unauthenticated attackers to read arbitrary files on the system by manipulating file paths through external input without proper sanitization of special elements (e.g., '../' sequences).
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>= 3.2, < 6.2>= 7.0, < 7.2= 8.0= 9.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if TelWin SCADA WebInterface is installedCheck for TelWin or TelSter SCADA software installations on the system - look for process named 'TelWin' or 'TelSter' running, or check installed programs list for 'Tel Ster' or 'Telwin' SCADA productsAffected if TelWin SCADA WebInterface software is present on the system
-
Determine the installed versionLocate the version information for the TelWin SCADA installation - check application files, About dialog, or version metadata within the SCADA installation directoryAffected if The installed version falls within 3.2 to <6.2, 7.0 to <7.2, or equals 8.0 or 9.0
-
Verify the web interface component is activeConfirm the WebInterface component of TelWin SCADA is running - check for listening web service ports (common SCADA web interfaces use HTTP ports 80/443 or custom ports) or look for web service processesAffected if The TelWin SCADA WebInterface service is actively running and accepting connections
-
Check network exposure of the web interfaceDetermine if the web interface is accessible from network locations - review firewall rules and binding addresses to see if the interface accepts remote connectionsAffected if The web interface is bound to non-localhost addresses or firewall permits external access to SCADA web ports
-
Test for path traversal vulnerabilityIf authorized and the web interface is accessible, attempt a controlled path traversal request using '../' sequences in a URL parameter that references files - for example, try accessing a known system file through the web interface endpointAffected if The web interface accepts and processes requests with '../' sequences without sanitization, allowing arbitrary file access
A system is affected if it runs a vulnerable TelWin SCADA WebInterface version (3.2 to <6.2, 7.0 to <7.2, 8.0, or 9.0) with the web interface component exposed and accessible.
Generated from the published advisory. Verify against your own configuration.
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 data6.27.2
Implement strict input validation with allowlist approach for file paths, use secure file handling APIs that prevent directory traversal, and apply any available vendor patches. Restrict web server file access permissions as defense-in-depth.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0956 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-0956 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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