dbcve.org
Codesys Gateway ServerApplication · 3s Software

CVE-2012-4708

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
Stack-based buffer overflow 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

A stack-based buffer overflow vulnerability exists in the 3S CODESYS Gateway-Server component, affecting versions prior to 2.3.9.27. The vulnerability is triggered by sending a specially crafted network packet to the Gateway-Server, which can lead to arbitrary code execution with elevated privileges.

MitigationUpdate the CODESYS Gateway-Server to version 2.3.9.27 or later. Additionally, apply network segmentation and firewall rules to restrict unauthorized access to the Gateway-Server port (typically TCP 1217), limiting the attack surface to trusted PLC engineering workstations only.

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. Locate the CODESYS Gateway-Server installation
    Check the Windows services list (services.msc) or look in typical installation directories such as C:\Program Files\3S Software\ or C:\Program Files (x86)\3S Software\ for a Gateway-Server executable
    Affected if The Gateway-Server service or executable is found on the system
  2. Identify the installed version of Gateway-Server
    Right-click the Gateway-Server executable, select Properties, and view the File Version under the Details tab. Alternatively, check the version through the Windows service properties
    Affected if The version shown is 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, or any version 2.3.9.20 or lower
  3. Verify the Gateway-Server service is running
    Open Services, locate the CODESYS Gateway-Server service, and confirm the Status shows Running
    Affected if The service is running and actively listening for network connections
  4. Confirm the service is listening on TCP port 1217
    Open Command Prompt and run netstat -an | findstr 1217, or use PowerShell Get-NetTCPConnection -LocalPort 1217
    Affected if The Gateway-Server is bound to TCP port 1217 on any IP address (0.0.0.0 or ::) indicating it accepts remote connections

The system is affected if the CODESYS Gateway-Server is installed with any version from 2.3.5.1 through 2.3.9.2 or version 2.3.9.20 and below, and the service is running and listening on the network.

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 the CODESYS Gateway-Server to version 2.3.9.27 or later. Additionally, apply network segmentation and firewall rules to restrict unauthorized access to the Gateway-Server port (typically TCP 1217), limiting the attack surface to trusted PLC engineering workstations only.

Recommended fix Moderate confidence

Codesys Gateway Server 2.3.9.27 or later

  1. Backup current Gateway Server configuration and any associated project files
  2. Stop the Codesys Gateway Server service before upgrading
  3. Download Codesys Gateway Server version 2.3.9.27 or later from the official 3S-Smart Software Solutions website
  4. Install the upgraded Gateway Server package following vendor installation documentation
  5. Restart the Gateway Server service after installation
  6. Verify the service is running and functioning correctly
  7. Test that legitimate client connections work properly after the upgrade

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

Fix this in Codesys Gateway Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-4708 — 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-4708 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