Codesys Vulnerabilities

Timeline

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Type

The moderation team is working with the threat intelligence team to categorize software that is affected by security vulnerabilities. This helps to illustrate the assignment of these categories to determine the most affected software types.

Product

CODESYS Control34
CODESYS Development System18
CODESYS Products11
CODESYS Control Runtime System6
CODESYS V34

Grouping vulnerabilities by products helps to get an overview. This makes it possible to determine an homogeneous landscape or the most important hotspots in heterogeneous landscapes.

Remediation

Official Fix53
Temporary Fix0
Workaround0
Unavailable0
Not Defined49

Vendors and researchers are eager to find countermeasures to mitigate security vulnerabilities. These can be distinguished between multiple forms and levels of remediation which influence risks differently.

Exploitability

High0
Functional0
Proof-of-Concept0
Unproven0
Not Defined102

Researcher and attacker which are looking for security vulnerabilities try to exploit them for academic purposes or personal gain. The level and quality of exploitability can be distinguished to determine simplicity and strength of attacks.

Access Vector

Not Defined0
Physical1
Local5
Adjacent13
Network83

The approach a vulnerability it becomes important to use the expected access vector. This is typically via the network, local, or physically even.

Authentication

Not Defined0
High0
Low67
None35

To exploit a vulnerability a certail level of authentication might be required. Vulnerabilities without such a requirement are much more popular.

User Interaction

Not Defined0
Required9
None93

Some attack scenarios require some user interaction by a victim. This is typical for phishing, social engineering and cross site scripting attacks.

C3BM Index

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

CVSSv3 Base

≤10
≤20
≤31
≤44
≤52
≤619
≤738
≤815
≤921
≤102

The Common Vulnerability Scoring System (CVSS) is an industry standard to define the characteristics and impacts of security vulnerabilities. The base score represents the intrinsic aspects that are constant over time and across user environments. Our unique meta score merges all available scores from different sources to aggregate to the most reliable result.

CVSSv3 Temp

≤10
≤20
≤31
≤44
≤52
≤619
≤739
≤815
≤920
≤102

The Common Vulnerability Scoring System (CVSS) uses temp scores to reflect the characteristics of a vulnerability that may change over time but not across user environments. This includes reporting confidence, exploitability and remediation levels. We do also provide our unique meta score for temp scores, even though other sources rarely publish them.

VulDB

≤10
≤20
≤31
≤46
≤55
≤625
≤730
≤813
≤920
≤102

The moderation team is always defining the base vector and base score for an entry. These and all other available scores are used to generate the meta score.

NVD

≤10
≤20
≤30
≤40
≤50
≤61
≤72
≤85
≤91
≤102

The National Vulnerability Database (NVD) is also defining CVSS vectors and scores. These are usually not complete and might differ from VulDB scores.

CNA

≤10
≤20
≤30
≤40
≤51
≤66
≤724
≤821
≤923
≤103

A CVE Numbering Authority (CNA) is responsible for assigning new CVE entries. They might also include a CVSS score. These are usually not complete and might differ from VulDB scores.

Vendor

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

Some vendors are willing to publish their own CVSS vectors and scores for vulnerabilities in their products. The coverage varies from vendor to vendor.

Research

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

There are sometimes also security researcher which provide their own CVSS vectors and scores for vulnerabilities they have found and published.

Exploit 0-day

<1k18
<2k44
<5k40
<10k0
<25k0
<50k0
<100k0
≥100k0

The moderation team is working with the threat intelligence team to determine prices for exploits. Our unique algorithm is used to identify the 0-day prices for an exploit, before it got distributed or became public. Calculated prices are aligned to prices disclosed by vulnerability broker and compared to prices we see on exploit markets.

Exploit Today

<1k92
<2k8
<5k2
<10k0
<25k0
<50k0
<100k0
≥100k0

The 0-day prices do not consider time-relevant factors. The today price does reflect price impacts like disclosure of vulnerability details, alternative exploits, availability of countermeasures. These dynamic aspects might decrease the exploit prices over time. Under certain circumstances this happens very fast.

Exploit Market Volume

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

🔴 CTI Activities

Our unique Cyber Threat Intelligence aims to determine the ongoing research of actors to anticipiate their acitivities. Observing exploit markets on the Darknet, discussions of vulnerabilities on mailinglists, and exchanges on social media makes it possible to identify planned attacks. Monitored actors and activities are classified whether they are offensive or defensive. They are also weighted as some actors are well-known for certain products and technologies. And some of their disclosures might contain more or less details about technical aspects and personal context. The world map highlights active actors in real-time.

Affected Products (45): Automation Server (1), Control (34), Control RTE (1), Control RTE SL (1), Control Runtime System (6), Control V3 (2), Control Win SL (2), Control for BeagleBone SL (2), Control for IOT2000 SL (2), Control for Linux ARM SL (2), Control for Linux SL (2), Control for PFC100 SL (2), Control for PFC200 SL (2), Control for PLCnext SL (2), Control for Raspberry Pi SL (2), Control for WAGO Touch Panels 600 SL (2), Control for emPC-A (1), Control for emPC-A iMX6 SL (1), Development System (18), Development System V3 (1), Edge Gateway for Windows (1), EtherNetIP (1), Gateway (2), Gateway Server (3), Gateway for Windows (1), Git (1), HMI SL (2), HMI V3 (1), OPC DA Server (1), PLCWinNT (3), PLCWinNT and Runtime Toolkit 32 (1), Products (11), Profinet (1), Runtime System (1), Runtime Toolkit (1), Runtime Toolkit for Linux or QNX (1), Runtime Toolkit for VxWorks (1), Scripting (1), Solidigm SSD (1), V2 Runtime Toolkit (3), V2 Web Server (4), V3 (4), Visualization (1), Web Server (2), iMX6 SL (1)

PublishedBaseTempVulnerabilityProdExpRemEPSSCTICVE
06/04/20247.87.6CODESYS Control Win SL exposure of resourceSCADA SoftwareNot DefinedOfficial Fix0.000430.09CVE-2023-5751
06/04/20247.57.3CODESYS Control for BeagleBone SL Request buffer sizeSCADA SoftwareNot DefinedOfficial Fix0.000430.05CVE-2024-5000
05/06/20246.05.9CODESYS Development System Project File use after freeUnknownNot DefinedOfficial Fix0.000440.04CVE-2023-49676
05/06/20248.38.1CODESYS Development System Project File out-of-bounds writeUnknownNot DefinedOfficial Fix0.000530.04CVE-2023-49675
12/05/20238.88.6CODESYS Control for BeagleBone SL File System Library os command injectionOperating SystemNot DefinedOfficial Fix0.000970.03CVE-2023-6357
08/03/20232.52.4CODESYS Development System excessive authenticationUnknownNot DefinedOfficial Fix0.000420.00CVE-2023-3669
08/03/20236.56.4CODESYS Control CmpAppBP denial of serviceUnknownNot DefinedNot Defined0.000440.05CVE-2023-37556
08/03/20236.56.4CODESYS Control CmpAppBP denial of serviceUnknownNot DefinedNot Defined0.000440.00CVE-2023-37555
08/03/20236.56.4CODESYS Control CmpAppBP denial of serviceUnknownNot DefinedNot Defined0.000440.00CVE-2023-37554
08/03/20236.56.4CODESYS Control CmpAppBP denial of serviceUnknownNot DefinedNot Defined0.000440.00CVE-2023-37553
08/03/20236.56.4CODESYS Control CmpAppBP denial of serviceUnknownNot DefinedNot Defined0.000440.00CVE-2023-37552
08/03/20236.46.3CODESYS Control CmpApp improper authenticationUnknownNot DefinedNot Defined0.000460.00CVE-2023-37551
08/03/20236.56.4CODESYS Control CmpApp denial of serviceUnknownNot DefinedNot Defined0.000440.00CVE-2023-37550
08/03/20236.56.4CODESYS Control CmpApp denial of serviceUnknownNot DefinedNot Defined0.000440.00CVE-2023-37549
08/03/20236.56.4CODESYS Control CmpApp denial of serviceUnknownNot DefinedNot Defined0.000440.00CVE-2023-37548
08/03/20236.56.4CODESYS Control CmpApp denial of serviceUnknownNot DefinedNot Defined0.000440.00CVE-2023-37547
08/03/20236.56.4CODESYS Control CmpApp denial of serviceUnknownNot DefinedNot Defined0.000440.00CVE-2023-37546
08/03/20236.56.4CODESYS Control CmpAppForce denial of serviceUnknownNot DefinedNot Defined0.000440.00CVE-2023-37559
08/03/20236.56.4CODESYS Control CmpAppForce denial of serviceUnknownNot DefinedNot Defined0.000440.00CVE-2023-37558
08/03/20236.56.4CODESYS Control CmpAppBP out-of-bounds writeUnknownNot DefinedNot Defined0.000440.00CVE-2023-37557
08/03/20238.88.6CODESYS Control memory corruptionUnknownNot DefinedNot Defined0.001100.00CVE-2022-4046
08/03/20237.37.1CODESYS Development System uncontrolled search pathUnknownNot DefinedOfficial Fix0.000420.00CVE-2023-3662
08/03/20235.45.3CODESYS Control CmpApp denial of serviceUnknownNot DefinedNot Defined0.000440.00CVE-2023-37545
08/03/20237.57.4CODESYS Development System Notification Server data authenticityUnknownNot DefinedOfficial Fix0.001390.00CVE-2023-3663
07/28/20237.37.3CODESYS Development System/Scripting exposure of resourceUnknownNot DefinedNot Defined0.000520.00CVE-2023-3670

77 more entries are not shown

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!