vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2019-9013

HIGH
8.8
CVSS Score
Published: August 15, 2019 at 04:08 PM UTC
Updated: June 17, 2026 at 02:42 AM UTC
12 products affected across 1 vendorControl for emPC-A/iMX6 SLControl for BeagleBone SLControl for PFC100 SL

Using N/A by N/A?

Get instant alerts when new vulnerabilities affect N/A - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Start FreeSign In
Severity
HIGH8.8
Exploit prediction
EPSS 0.3%

Description

An issue was discovered in 3S-Smart CODESYS V3 products. The application may utilize non-TLS based encryption, which results in user credentials being insufficiently protected during transport. All variants of the following CODESYS V3 products in all versions containing the CmpUserMgr component are affected regardless of the CPU type or operating system: CODESYS Control for BeagleBone, CODESYS Control for emPC-A/iMX6, CODESYS Control for IOT2000, CODESYS Control for Linux, CODESYS Control for PFC100, CODESYS Control for PFC200, CODESYS Control for Raspberry Pi, CODESYS Control RTE V3, CODESYS Control RTE V3 (for Beckhoff CX), CODESYS Control Win V3 (also part of the CODESYS Development System setup), CODESYS V3 Simulation Runtime (part of the CODESYS Development System), CODESYS Control V3 Runtime System Toolkit, CODESYS HMI V3.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Control for BeagleBone SL· Codesys
95%
3.0 ≤ v < 3.5.16.0
Affected range stops below 3.5.16.0, so it looks safe — our inference, not a vendor statement
Control for emPC-A/iMX6 SL· Codesys
95%
3.0 ≤ v < 3.5.16.0
Affected range stops below 3.5.16.0, so it looks safe — our inference, not a vendor statement
Control for IOT2000 SL· Codesys
95%
3.0 ≤ v < 3.5.16.0
Affected range stops below 3.5.16.0, so it looks safe — our inference, not a vendor statement
Control for Linux SL· Codesys
95%
3.0 ≤ v < 3.5.16.0
Affected range stops below 3.5.16.0, so it looks safe — our inference, not a vendor statement
Control for PFC100 SL· Codesys
95%
3.0 ≤ v < 3.5.16.0
Affected range stops below 3.5.16.0, so it looks safe — our inference, not a vendor statement
Control for PFC200 SL· Codesys
95%
3.0 ≤ v < 3.5.16.0
Affected range stops below 3.5.16.0, so it looks safe — our inference, not a vendor statement
Control RTE (SL)· Codesys
95%
3.0 ≤ v < 3.5.16.0
Affected range stops below 3.5.16.0, so it looks safe — our inference, not a vendor statement
Control Win (SL)· Codesys
95%
3.0 ≤ v < 3.5.16.0
Affected range stops below 3.5.16.0, so it looks safe — our inference, not a vendor statement
Development System· Codesys
95%
3.0 ≤ v < 3.5.16.0
Affected range stops below 3.5.16.0, so it looks safe — our inference, not a vendor statement
HMI (SL)· Codesys
95%
3.0 ≤ v < 3.5.16.0
Affected range stops below 3.5.16.0, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (2)

x_refsource_CONFIRMVendor Advisory
Source: [email protected]
https://customers.codesys.com/index.php?eID=dumpFile&t=f&f=12943&token=d097958a67ba382de688916f77e3013c0802fade&download=
x_refsource_MISCThird Party AdvisoryUS Government Resource
Source: [email protected]
https://www.us-cert.gov/ics/advisories/icsa-19-213-04

CVSS

8.8HIGH[email protected]
Attack Vector
ADJACENT_NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-327

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create accountSign in
Free plan, no card