dbcve.org
Codesys Gateway ServerApplication · 3s Software

CVE-2012-4704

HIGH · 10.0 CVSS v2.0 Published 2013-02-24
Fix available
A fix is available. Upgrade to after 2.3.9.20 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Array index error in 3S CODESYS Gateway-Server before 2.3.9.27 allows remote attackers to execute arbitrary code via a crafted packet.

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

An array index error in 3S CODESYS Gateway-Server versions prior to 2.3.9.27 allows remote attackers to execute arbitrary code via a crafted packet. This is a memory corruption vulnerability in the gateway component of the CODESYS industrial automation software stack, exploitable without authentication.

MitigationUpdate CODESYS Gateway-Server to version 2.3.9.27 or later. If immediate patching is not feasible, isolate the gateway from untrusted networks using firewalls or air gaps.

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
Codesys Gateway ServerApplication
Affected:<= 2.3.9.20= 2.3.5.1= 2.3.5.2= 2.3.5.3= 2.3.6.0= 2.3.7.0= 2.3.8.0= 2.3.8.1= 2.3.8.2= 2.3.9= 2.3.9.1= 2.3.9.2

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 CODESYS Gateway-Server installation
    Look for the Gateway-Server service or executable on the system. Common process names include 'CODESYS Gateway Server', 'GatewayServer.exe', or check installed programs list for 3S Software CODESYS components.
    Affected if CODESYS Gateway-Server is present on the system
  2. Determine installed Gateway-Server version
    Access the Gateway-Server through its configuration interface, check the executable file properties, or query the service information using system management tools to retrieve the version number.
    Affected if Version is 2.3.9.20 or lower, or matches any of these: 2.3.5.1, 2.3.5.2, 2.3.5.3, 2.3.6.0, 2.3.7.0, 2.3.8.0, 2.3.8.1, 2.3.8.2, 2.3.9, 2.3.9.1, 2.3.9.2
  3. Verify gateway service is network accessible
    Check if the Gateway-Server is listening on network ports (default TCP ports 1217, 1743, or 1744). Use netstat or similar network inspection tools to confirm the service is exposed to the network.
    Affected if The gateway service is running and accepting remote connections, especially on accessible network interfaces

The environment is affected if CODESYS Gateway-Server is installed with a version matching any of the listed vulnerable versions and the gateway service is 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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.3.9.20
Interim mitigation

Update CODESYS Gateway-Server to version 2.3.9.27 or later. If immediate patching is not feasible, isolate the gateway from untrusted networks using firewalls or air gaps.

Recommended fix Moderate confidence

Codesys Gateway Server 2.3.9.27 or later

  1. 1. Backup the current Codesys Gateway Server configuration and all related project files
  2. 2. Download the updated Codesys Gateway Server version 2.3.9.27 or later from the official 3S-Smart Software Solutions website
  3. 3. Stop the Codesys Gateway Server service on the affected system
  4. 4. Uninstall the current version of Codesys Gateway Server
  5. 5. Install the new version (2.3.9.27 or later) using the downloaded installer
  6. 6. Restore the backed-up configuration files
  7. 7. Start the Codesys Gateway Server service
  8. 8. Verify the service is running correctly and test connectivity
Caveat Review release notes for version 2.3.9.27 to check for any configuration or compatibility changes that may affect existing projects

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Codesys Gateway Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,960
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-4704 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2012-4704 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