Embedded Target Visu Toolkit vulnerabilitiesRanked by how likely they are to be used.
Embedded Target Visu Toolkit is made by Codesys. We track 16 published vulnerabilities in it, across 7 versions. None of them is on the list of flaws known to be exploited today. If you run Embedded Target Visu Toolkit, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Embedded Target Visu Toolkit vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Embedded Target Visu Toolkit's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Embedded Target Visu Toolkit flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 5.8%CVE-2019-13548Critical
CODESYS V3 web server, all versions prior to 3.5.14.10, allows an attacker to send specially crafted http or https requests which could cause a stack overflow and create a denial-of-service condition or allow remote...
- 3.2%CVE-2019-13532High
CODESYS V3 web server, all versions prior to 3.5.14.10, allows an attacker to send specially crafted http or https requests which may allow access to files outside the restricted working directory of the controller.
- 2.5%CVE-2020-10245Critical
CODESYS V3 web server before 3.5.15.40, as used in CODESYS Control runtime systems, has a buffer overflow.
- 2.0%CVE-2020-15806High
CODESYS Control runtime system before 3.5.16.10 allows Uncontrolled Memory Allocation.
- 1.9%CVE-2019-18858Critical
CODESYS 3 web server before 3.5.15.20, as distributed with CODESYS Control runtime systems, has a Buffer Overflow.
- 1.5%CVE-2022-22519High
A remote, unauthenticated attacker can send a specific crafted HTTP or HTTPS requests causing a buffer over-read resulting in a crash of the webserver of the CODESYS Control runtime system.
- 1.3%CVE-2022-22517High
An unauthenticated, remote attacker can disrupt existing communication channels between CODESYS products by guessing a valid channel ID and injecting packets.
- 1.1%CVE-2021-33485Critical
CODESYS Control Runtime system before 3.5.17.10 has a Heap-based Buffer Overflow.
- 1.1%CVE-2022-22515High
A remote, authenticated attacker could utilize the control program of the CODESYS Control runtime system to use the vulnerability in order to read and modify the configuration file(s) of the affected products.
- 1.1%CVE-2021-29242High
CODESYS Control Runtime system before 3.5.17.0 has improper input validation.
Running Embedded Target Visu Toolkit? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
CODESYS V3 web server, all versions prior to 3.5.14.10, allows an attacker to send specially crafted http or https requests which could cause a stack overflow and create a denial-of-service condition or allow remote code execution.
- Matched to
- Embedded Target Visu Toolkit on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 16 published vulnerabilities listed under the name Embedded Target Visu Toolkit, across 7 versions.
None of Embedded Target Visu Toolkit's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Embedded Target Visu Toolkit. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.