Control for Plcnext vulnerabilitiesRanked by how likely they are to be used.
Control for Plcnext is made by Codesys. We track 8 published vulnerabilities listed under that exact name, across 5 versions. None of them is on the list of flaws known to be exploited today. Codesys lists newer releases under their own names, such as Control for Plcnext Sl, so check those pages too.
We keep watching the known-exploited list.
Is Control for Plcnext listed under other names? Yes.
Codesys also lists Control for Plcnext under more specific names, such as Control for Plcnext Sl. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which Control for Plcnext vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Control for Plcnext's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Control for Plcnext 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.
- 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.9%CVE-2020-7052Medium
CODESYS Control V3, Gateway V3, and HMI V3 before 3.5.15.30 allow uncontrolled memory allocation which can result in a remote denial of service condition.
- 0.9%CVE-2020-12068Medium
An issue was discovered in CODESYS Development System before 3.5.16.0.
- 0.9%CVE-2022-30791High
In CmpBlkDrvTcp of CODESYS V3 in multiple versions an uncontrolled ressource consumption allows an unauthorized attacker to block new TCP connections.
- 0.9%CVE-2022-30792High
In CmpChannelServer of CODESYS V3 in multiple versions an uncontrolled ressource consumption allows an unauthorized attacker to block new communication channel connections.
- 0.2%CVE-2020-12069High
In CODESYS V3 products in all versions prior V3.5.16.0 containing the CmpUserMgr, the CODESYS Control runtime system stores the online communication passwords using a weak hashing algorithm.
Running Control for Plcnext? 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 before 3.5.15.40, as used in CODESYS Control runtime systems, has a buffer overflow.
- Matched to
- Control for Plcnext 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 8 published vulnerabilities listed under the name Control for Plcnext, across 5 versions.
None of Control for Plcnext's vulnerabilities is on the list of flaws known to be exploited today.
Codesys also lists Control for Plcnext under more specific names, such as Control for Plcnext Sl. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track Control for Plcnext. 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.