CVE-2019-16265
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 · uneditedCODESYS V2.3 ENI server up to V3.2.2.24 has a 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 · moderate confidenceA buffer overflow vulnerability exists in the CODESYS V2.3 ENI (Equipment Norman Interface) server component affecting versions up to V3.2.2.24. The ENI server handles configuration and communication for CODESYS-based industrial automation systems. This memory corruption vulnerability with critical severity (CVSS 9.8) likely allows remote attackers to execute arbitrary code or cause denial of service.
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< 3.2.2.25>= 2.3, < 2.3.9.61CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if CODESYS ENI Server is installedCheck the system for CODESYS ENI Server software. Look for ENI Server executables or services in typical CODESYS installation directories, or query installed programs list.Affected if ENI Server component is present on the system
-
Determine ENI Server versionLocate the ENI Server executable (commonly eni.exe or similar) and check its file version properties, or use the CODESYS product information dialog if available.Affected if Version is less than 3.2.2.25 (or if the installed version cannot be determined but the component exists)
-
Check CODESYS runtime version if ENI Server version cannot be determinedIf the standalone ENI Server version is not accessible, check the main CODESYS installation version using the CODESYS development environment or installed program information.Affected if CODESYS version is 2.3 or higher but lower than 2.3.9.61
-
Verify if ENI Server service is running and exposedCheck Windows services or running processes for ENI Server, and review network configuration to determine if the ENI server listens on network ports (typical ENI communication ports).Affected if ENI Server service is actively running and accessible over the network
-
Confirm ENI functionality is enabled in the project configurationReview CODESYS project files or ENI configuration settings to determine if the ENI server component is configured and enabled for automation projects.Affected if ENI server is configured and actively handling communications for automation controllers
The environment is affected if CODESYS ENI Server or CODESYS with ENI component is installed and the installed version falls below 3.2.2.25 (for ENI Server) or below 2.3.9.61 (for CODESYS), with the ENI service running and network-accessible.
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 · scoped2.3.9.613.2.2.25
Update CODESYS ENI server to a version beyond V3.2.2.24 that contains the security patch. If patching is not immediately feasible, network isolate the ENI server and implement strict access controls to reduce attack surface.
Eni Server: >= 3.2.2.25 | Codesys: >= 2.3.9.61
- 1. Identify the installed CODESYS V2.3 ENI server and/or CODESYS V2.3 product version in your environment
- 2. For Eni Server: If version is less than 3.2.2.25, upgrade to version 3.2.2.25 or later
- 3. For Codesys: If version is 2.3.x and less than 2.3.9.61, upgrade to version 2.3.9.61 or later
- 4. Verify the upgrade was successful by checking the installed version after patching
- 5. Test the application to ensure normal operation after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16265 — 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-2019-16265 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