CVE-2022-22513
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 · uneditedAn authenticated remote attacker can cause a null pointer dereference in the CmpSettings component of the affected CODESYS products which leads to a crash.
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 null pointer dereference vulnerability exists in the CmpSettings component of CODESYS products. An authenticated remote attacker can exploit this to cause a crash, resulting in denial of service. The attack requires valid credentials, reducing the attack surface but not eliminating the risk.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 product installedCheck the system or CODESYS installation for the specific product name (e.g., Codesys Control For Beaglebone Sl, Codesys Control For Linux Sl, etc.)Affected if The product is one of the eight affected products listed in the CVE
-
Determine the installed version of the CODESYS Control productAccess the CODESYS runtime or control panel on the affected device and locate the version information for the installed CODESYS Control productAffected if The installed version is less than 4.5.0.0 (any version before 4.5.0.0)
-
Verify the CmpSettings component is presentCheck the CODESYS installation or runtime modules for the presence of the CmpSettings componentAffected if CmpSettings component is loaded or active in the CODESYS runtime
-
Confirm remote access is enabledCheck the CODESYS runtime configuration or network settings to determine if remote connections are allowedAffected if Remote network access to the CODESYS runtime is enabled
You are affected if you are running any of the eight listed CODESYS Control products with a version lower than 4.5.0.0 and the CmpSettings component is in use with remote access enabled.
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 vendor-supplied patches for affected CODESYS products when available. Until patches are applied, restrict network access to affected systems and enforce strict authentication controls to limit exposure to authenticated attackers.
CODESYS Control products version 4.5.0.0 or later
- Identify all deployed CODESYS Control products in the environment and verify their current versions
- For each affected product (Control for Beaglebone, Beckhoff Cx9020, Empc A/imx6, Iot2000, Linux, Pfc100, Pfc200, Plcnext), confirm the version is below 4.5.0.0
- Obtain the CODESYS software update from the official vendor source (customers.codesys.com or official CODESYS distribution channels)
- Upgrade each affected CODESYS Control product installation to version 4.5.0.0 or later
- After upgrading, verify the CmpSettings component is updated and the null pointer dereference vulnerability is resolved
- Test the updated control applications to ensure normal operation after the upgrade
- Document the upgrade for audit and compliance purposes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22513 — 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-22513 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