CVE-2022-22519
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 · uneditedA remote, unauthenticated attacker can send a specific crafted HTTP or HTTPS requests causing a buffer over-read resulting in a crash of the webserver of the CODESYS Control runtime system.
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 confidenceCVE-2022-22519 is a buffer over-read vulnerability in the webserver component of CODESYS Control runtime systems. A remote, unauthenticated attacker can exploit this by sending specially crafted HTTP or HTTPS requests, causing the webserver to crash due to the buffer over-read.
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< 4.5.0.0< 4.5.0.0< 4.5.0.0< 4.5.0.0< 4.5.0.0< 4.5.0.0< 4.5.0.0< 4.5.0.0CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 the CODESYS Control productDetermine which CODESYS Control runtime variant is installed on the system (e.g., Beaglebone, Beckhoff CX9020, Linux, PFC100, PFC200, PLCnext, IoT2000, or Empc A/imx6). Check the installed software package name or runtime identification.Affected if The installed product is any of the eight listed variants and the version is below 4.5.0.0
-
Check the installed versionLocate the installed version of the CODESYS Control runtime. This is typically found in the runtime package details, system information, or the CODESYS development environment under the target device properties. Compare the version number to the affected threshold of 4.5.0.0.Affected if The installed version is lower than 4.5.0.0
-
Verify the webserver component is enabledCheck if the CODESYS webserver service or component is running and enabled. This is usually configurable in the runtime settings or as a separate service. Look for the webserver process or configuration in the runtime setup.Affected if The webserver component is enabled and accessible on the device
-
Confirm network exposure of HTTP/HTTPS portsInspect the network configuration to determine if the webserver ports (default HTTP port 80, HTTPS port 443, or custom ports) are exposed to the network. Use netstat, ss, or firewall rules to check listening ports and their accessibility.Affected if HTTP or HTTPS ports are open and reachable from network segments beyond localhost
The environment is affected if a CODESYS Control runtime variant is installed with version below 4.5.0.0 and the webserver component is enabled 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.
dbcve · scoped4.5.0.0
Apply the vendor patch from CODESYS when available. In the interim, restrict network access to the webserver port (HTTP/HTTPS) to minimize exposure, and monitor for attempts targeting this vulnerability.
CODESYS Control version 4.5.0.0 or later
- 1. Identify the specific CODESYS Control product variant running on your system
- 2. Obtain the CODESYS Control runtime version 4.5.0.0 or later from the official CODESYS download repository or your vendor
- 3. Back up the current CODESYS Control configuration and project files
- 4. Install version 4.5.0.0 or later of the affected CODESYS Control runtime
- 5. Restore the configuration and verify the webserver starts successfully
- 6. Test that the webserver accepts normal HTTP/HTTPS requests
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing8.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,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22519 — 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-2022-22519 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