CVE-2012-4706
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 · uneditedInteger signedness error in 3S CODESYS Gateway-Server before 2.3.9.27 allows remote attackers to cause a denial of service via a crafted packet that triggers a heap-based buffer overflow.
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 confidenceInteger signedness error in 3S CODESYS Gateway-Server allows remote attackers to trigger a heap-based buffer overflow via crafted packets, causing denial of service. The vulnerability stems from incorrect handling of integer types when calculating buffer sizes, leading to undersized memory allocations.
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<= 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.2CVSS 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
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/Au:N/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Locate the Codesys Gateway Server installationCheck common installation paths such as C:\Program Files\3S Software\ or C:\Program Files (x86)\3S Software\ for the Gateway Server directory, or look for the service named 'CodesysGatewayServer' in Windows Services.Affected if The Gateway Server software is installed on the system.
-
Determine the installed Gateway Server versionOpen the Gateway Server installation directory and locate the executable file (typically 'GatewayServer.exe' or similar), then right-click and select Properties to view the File Version, or check the software's About/Version information within the CODESYS interface.Affected if The installed version matches one of the affected versions listed: <= 2.3.9.20, or exactly 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, or 2.3.9.2.
-
Verify the Gateway Server service is runningOpen Windows Services (services.msc) and look for 'Codesys Gateway Server' or '3S CODESYS Gateway Server', or run 'netstat -an | findstr 1217' to check if the default gateway port (1217/tcp) is listening.Affected if The Gateway Server service is running and listening on network ports, making it accessible to remote attackers.
-
Assess network exposure of the gateway serviceRun 'netstat -an' or use a network scanner to determine if port 1217 (default CODESYS Gateway port) is bound to an external IP address or is accessible from untrusted network segments.Affected if The gateway port is exposed to untrusted networks or the internet without firewall protection.
You are affected if the Codesys Gateway Server is installed with a version matching <= 2.3.9.20 or any of the specific versions 2.3.5.1 through 2.3.9.2, and the service is running and accessible over the network.
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.
From vendor dataUpgrade CODESYS Gateway-Server to version 2.3.9.27 or later. Apply network segmentation to isolate the gateway server from untrusted networks and implement ingress filtering on affected ports.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-4706 — 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-2012-4706 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