CVE-2023-3670
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn CODESYS Development System 3.5.9.0 to 3.5.17.0 and CODESYS Scripting 4.0.0.0 to 4.1.0.0 unsafe directory permissions would allow an attacker with local access to the workstation to place potentially harmful and disguised scripts that could be executed by legitimate users.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCODESYS Development System and Scripting tools have unsafe directory permissions that allow local attackers to place malicious scripts in directories that are accessed by legitimate users. When users execute these disguised scripts, the attacker achieves code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 3.5.9.0, < 3.5.17.0>= 4.0.0.0, < 4.1.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check CODESYS Development System versionOpen CODESYS Development System, go to Help > About, or check the installed program version in Windows Programs and FeaturesAffected if Version is >= 3.5.9.0 and < 3.5.17.0
-
Check CODESYS Scripting versionRun 'CODESYSScripting.exe --version' from command line, or check the installed package version via pip if using the Python scripting moduleAffected if Version is >= 4.0.0.0 and < 4.1.0.0
-
Inspect CODESYS user script directoriesLocate directories where CODESYS stores or loads user scripts - typically found in the CODESYS installation folder under 'Projects', 'Scripts', or the user's AppData folder. Right-click each directory, go to Properties > Security tab, and review Write permissions for users and groupsAffected if Users other than administrators or trusted accounts have Write permission to directories where CODESYS loads and executes scripts
-
Verify script execution path securityExamine directories in the CODESYS search path for scripts (check Tools > Options > Scripting or similar in the IDE). Confirm that standard users cannot create or modify files in these locationsAffected if Standard users have write access to any directory that CODESYS includes in its script load/execute path
You are affected if you have either CODESYS Development System version 3.5.9.0 through 3.5.17.0 or CODESYS Scripting version 4.0.0.0 through 4.1.0.0 installed, AND standard users have write access to directories where CODESYS loads or executes scripts.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.5.17.04.1.0.0
Restrict write permissions on directories used by CODESYS to trusted accounts only, and implement script signing/validation to prevent execution of unauthorized scripts.
CODESYS Development System >= 3.5.17.0; CODESYS Scripting >= 4.1.0.0
- Identify the installed CODESYS product (Development System or Scripting) and current version using the About dialog or installer
- Download the fixed version from the official CODESYS download page or your vendor portal
- For Development System: Upgrade to version 3.5.17.0 or later
- For Scripting: Upgrade to version 4.1.0.0 or later
- After upgrade, verify the version using the About dialog to confirm the patch was applied
- Review release notes for any additional security notes or configuration changes needed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3670 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-3670 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data