CVE-2023-3663
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 versions from 3.5.11.20 and before 3.5.19.20 a missing integrity check might allow an unauthenticated remote attacker to manipulate the content of notifications received via HTTP by the CODESYS notification server.
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 confidenceIn CODESYS Development System versions 3.5.11.20 through 3.5.19.20, the notification server lacks integrity validation for HTTP notifications, allowing unauthenticated remote attackers to modify notification content during transit.
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.11.20, < 3.5.19.20CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify CODESYS Development System versionOpen CODESYS Development System and navigate to Help > About, or right-click the executable in the installation directory and view Properties > Details to find the product versionAffected if The installed version is 3.5.11.20 or higher but lower than 3.5.19.20
-
Confirm notification server configurationExamine the CODESYS project settings or the notification server configuration panel to determine if HTTP notifications are enabledAffected if The HTTP notification server feature is enabled and configured to send notifications
-
Check for integrity validation in transitInspect network traffic or logs related to the notification server to see if any integrity validation mechanism such as HMAC or digital signatures is presentAffected if No integrity validation (such as signatures or checksums) is applied to HTTP notification messages
The environment is affected if CODESYS Development System version is 3.5.11.20 or higher but lower than 3.5.19.20 and the HTTP notification server is actively being used.
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.19.20
Upgrade CODESYS Development System to version 3.5.19.20 or later to obtain the integrity check fix, and implement network segmentation to protect the notification server from unauthorized access.
3.5.19.20 or later
- 1. Check current CODESYS Development System version (Help > About CODESYS)
- 2. Download CODESYS Development System version 3.5.19.20 or later from the official CODESYS download page or your customer portal
- 3. Close all running CODESYS instances
- 4. Run the installer and follow the prompts to upgrade
- 5. After installation, verify the installed version (Help > About CODESYS) confirms version >= 3.5.19.20
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,624.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3663 — 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-3663 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