CVE-2017-6043 json
A Resource Consumption issue was discovered in Trihedral VTScada Versions prior to 11.2.26.
published 9y ago modified 4mo ago also EUVD-2017-15111
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
A Resource Consumption issue was discovered in Trihedral VTScada Versions prior to 11.2.26. The client does not properly validate the input or limit the amount of resources that are utilized by an attacker, which can be used to consume more resources than are available.
Patch / fix
Is CVE-2017-6043 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-17-164-01 updated cvss 7.5
Trihedral Engineering Limited VTScada
-
Trihedral Engineering Limited VTScada < 11.2.26affected: vendor fix trihedral.com
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
Exploit prediction
1.69% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 7.8 | AV:N/AC:L/Au:N/C:N/I:N/A:C |
Affected products
- n/a Trihedral VTScada
Classification
- Weakness
-
- CWE-400 Uncontrolled Resource Consumption
References
-
ics-cert.us-cert.gov
/advisories/ICSA-17-164-01
mitigation, patch, third-party-advisory, us-government-resource
-
securityfocus.com
/bid/99066
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-6043
- NVD CVE-2017-6043
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.