CVE-2012-4705
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 · uneditedDirectory traversal vulnerability in 3S CODESYS Gateway-Server before 2.3.9.27 allows remote attackers to execute arbitrary code via vectors involving a crafted pathname.
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 confidenceDirectory traversal vulnerability in 3S CODESYS Gateway-Server versions prior to 2.3.9.27 allows remote attackers to use specially crafted pathnames to traverse directory structures and execute arbitrary code on the affected system.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if CODESYS Gateway-Server is installedCheck for the CODESYS Gateway-Server service or process on the system. On Windows, this may appear as a service named 'CODESYS Gateway-Server' or a running executable related to the gateway. On Linux, check for gateway-related processes.Affected if The software is present on the system
-
Determine the installed Gateway-Server versionLocate the version information for the CODESYS Gateway-Server installation. This is typically available through the service properties, the executable file properties, or the product's about/information dialog if accessible.Affected if Unable to determine the version (may indicate a vulnerable installation)
-
Compare your version to the affected rangesReview the installed version number against the following affected versions: <= 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.2Affected if The installed version matches any of the listed affected versions or falls at or below 2.3.9.20
You are affected if the CODESYS Gateway-Server is installed and its version is any of the specific versions listed (2.3.5.1 through 2.3.9.2) or falls at or below 2.3.9.20.
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 · scopedUpgrade CODESYS Gateway-Server to version 2.3.9.27 or later to remediate the vulnerability; apply network segmentation and restrict unauthorized access to the gateway service in the interim.
2.3.9.27 or later
- 1. Identify all instances of Codesys Gateway Server in the environment
- 2. Check current version of each installation
- 3. For servers running versions <= 2.3.9.20, 2.3.5.1, 2.3.5.2, or 2.3.5.3, download the fixed version from the vendor
- 4. Schedule maintenance window following change management procedures
- 5. Stop the Codesys Gateway Server service
- 6. Install version 2.3.9.27 or later
- 7. Restart the service and verify proper operation
- 8. Confirm the patch was applied by checking the version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-4705 — 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-4705 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