GatewayApplication · Codesys

CVE-2021-36764

HIGH · 7.5 CVSS v3.1 Published 2021-08-04
Fix available
A fix is available. Upgrade to 3.5.17.10 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
In CODESYS Gateway V3 before 3.5.17.10, there is a NULL Pointer Dereference. Crafted communication requests may cause a Null pointer dereference in the affected CODESYS products and may result in a denial-of-service condition.

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 confidence

CODESYS Gateway V3 versions before 3.5.17.10 are vulnerable to a NULL Pointer Dereference when processing specially crafted communication requests. An unauthenticated remote attacker can send malicious packets to trigger the dereference, causing the gateway service to crash and resulting in a denial-of-service condition.

MitigationUpdate CODESYS Gateway V3 to version 3.5.17.10 or later to patch the NULL pointer dereference vulnerability. Apply the update during a planned maintenance window and verify gateway functionality after deployment.

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
GatewayApplication
Affected:>= 3.0, < 3.5.17.10

CVSS 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
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if CODESYS Gateway V3 is installed
    Check system services or installed programs for 'CODESYS Gateway V3' or 'Gateway' service. On Windows, review services list or check installation directories. On Linux, look for CODESYS-related processes or services.
    Affected if CODESYS Gateway V3 software is present on the system
  2. Locate the installed version
    Check the CODESYS Gateway V3 version. This is typically found in the software properties, about dialog, or version file within the CODESYS installation directory. Common locations include the main Gateway folder or registry entries on Windows systems.
    Affected if The installed version cannot be determined or is below 3.5.17.10
  3. Compare version against vulnerable range
    Review the identified version against the affected range: versions 3.0 through 3.5.17.9 (any version < 3.5.17.10). Ensure exact version number is captured for accuracy.
    Affected if Installed version is 3.0 or higher but lower than 3.5.17.10
  4. Check gateway service exposure
    Verify if the CODESYS Gateway service is running and listening on network ports. The gateway typically uses TCP ports for communication. Review firewall rules and network configuration to determine if the service is exposed to network access.
    Affected if The gateway service is running and accessible from the network, increasing attack surface
  5. Review recent service availability
    Check system logs, event logs, or gateway logs for any unexpected crashes, restarts, or denial-of-service indicators that may correlate with exploitation attempts.
    Affected if Gateway service has experienced unexplained crashes or outages

The environment is affected if CODESYS Gateway V3 is installed with a version between 3.0 and 3.5.17.9 inclusive, and the gateway service is running and network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Upgrade available Upgrade to 3.5.17.10 or later
Fixed in 3.5.17.10
Interim mitigation

Update CODESYS Gateway V3 to version 3.5.17.10 or later to patch the NULL pointer dereference vulnerability. Apply the update during a planned maintenance window and verify gateway functionality after deployment.

Fix this in Gateway Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-36764 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-36764 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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