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
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 3.1% (FIRST EPSS); higher than 87.8% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 13, 2019
- Updated
- Jun 16, 2026
- EPSS
- 3.1% · 87th percentile
- CWE
- CWE-22
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| codesys | control for beaglebone | cpe:2.3:a:codesys:control_for_beaglebone |
| codesys | control for empc-a\/imx6 | cpe:2.3:a:codesys:control_for_empc-a\/imx6 |
| codesys | control for iot2000 | cpe:2.3:a:codesys:control_for_iot2000 |
| codesys | control for linux | cpe:2.3:a:codesys:control_for_linux |
| codesys | control for pfc100 | cpe:2.3:a:codesys:control_for_pfc100 |
| codesys | control for pfc200 | cpe:2.3:a:codesys:control_for_pfc200 |
| codesys | control for raspberry pi | cpe:2.3:a:codesys:control_for_raspberry_pi |
| codesys | control rte | cpe:2.3:a:codesys:control_rte |
| codesys | control runtime system toolkit | cpe:2.3:a:codesys:control_runtime_system_toolkit |
| codesys | control win | cpe:2.3:a:codesys:control_win |
| codesys | embedded target visu toolkit | cpe:2.3:a:codesys:embedded_target_visu_toolkit |
| codesys | hmi | cpe:2.3:a:codesys:hmi |
and 1 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- codesys control for beaglebonebefore 3.5.14.10
- codesys control for empc-a/imx6before 3.5.14.10
- codesys control for iot2000before 3.5.14.10
- codesys control for linuxbefore 3.5.14.10
- codesys control for pfc100before 3.5.14.10
- codesys control for pfc200before 3.5.14.10
- codesys control for raspberry pibefore 3.5.14.10
- codesys control rte3.5.8.60 and later · before 3.5.12.80
- codesys control rte3.5.13.0 and later · before 3.5.14.10
- codesys control runtime system toolkit3.0 and later · before 3.5.12.80
- codesys control win3.5.9.80 and later · up to 3.5.12.80 inclusive
- codesys control win3.5.13.0 and later · before 3.5.14.10
- codesys embedded target visu toolkit3.0 and later · before 3.5.12.80
- codesys hmi3.5.10.0 and later · before 3.5.12.80
- codesys hmi3.5.13.0 and later · before 3.5.14.10
- codesys remote target visu toolkit3.0 and later · before 3.5.12.80
Versions reported by the vendor
Affected version ranges reported by the assigning authority (icscert). Independent of NVD's CPE analysis and usually ahead of it.
n/a CODESYS V3 web server
- all versions prior to 3.5.14.10affected
Same product
codesys: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-13548CODESYS V3 web server, all versions prior to 3.5.14.10, allows an attacker to send specially crafted http or https requests which could caus41Plan
- CVE-2020-10245CODESYS V3 web server before 3.5.15.40, as used in CODESYS Control runtime systems, has a buffer overflow.40Plan
- CVE-2019-18858CODESYS 3 web server before 3.5.15.20, as distributed with CODESYS Control runtime systems, has a Buffer Overflow.40Plan
Published before and after this one in the same product
- Later →CVE-2019-9008Sep 17, 2019 · An issue was discovered in 3S-Smart CODESYS V3 through 3.5.12.30.36Monitor
- Later →CVE-2019-9009Sep 17, 2019 · An issue was discovered in 3S-Smart CODESYS before 3.5.15.0 .31Monitor
- Later →CVE-2019-13542Sep 17, 2019 · 3S-Smart Software Solutions GmbH CODESYS V3 OPC UA Server, all versions 3.5.11.0 to 3.5.15.0, allows an attacker to send crafted requests fr26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-19-146 · Sep 12, 2019(CODESYS Endüstriyel Ürünler Zafiyeti)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Root cause
A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.
The bug in code
The whole CWE-22 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);
res.sendFile(file);Fixed
const file = path.resolve(ROOT, req.query.name);
if (!file.startsWith(ROOT + path.sep)) {
return res.sendStatus(400);
}
res.sendFile(file);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.