CVE-2022-22510
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 Profinet in version V4.2.0.0 is prone to null pointer dereference that allows a denial of service (DoS) attack of an unauthenticated user via SNMP.
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 confidenceCODESYS Profinet V4.2.0.0 contains a null pointer dereference vulnerability that can be triggered by an unauthenticated attacker via SNMP requests, leading to a denial of service condition. The vulnerability exists specifically within the Profinet component handling SNMP protocol processing.
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.2.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 if CODESYS Profinet is installedCheck system for CODESYS Profinet installation. Look for CODESYS runtime components, typically installed in C:\Program Files\CODESYS or similar paths. Use system inventory or program list to confirm presence.Affected if CODESYS Profinet software is present on the system
-
Verify installed Profinet versionCheck the installed version of CODESYS Profinet. This is typically found in the software itself via Help > About, or in the Windows Programs and Features list, or by checking the executable properties if the installation path is known.Affected if The installed version is exactly 4.2.0.0
-
Confirm SNMP is enabled in ProfinetInspect the Profinet configuration settings to determine if SNMP protocol handling is enabled. This is usually configured within the CODESYS Development System or the Profinet device configuration interface. Look for SNMP settings in the Profinet stack or network adapter configuration.Affected if SNMP is enabled and accessible to the Profinet component
-
Check network exposure of SNMP serviceReview firewall rules and network configuration to determine if the SNMP service (typically UDP port 161) is exposed to untrusted networks or accessible from external interfaces. Verify if network segmentation isolates the industrial system.Affected if SNMP is accessible from untrusted network segments or external IP addresses
You are affected if CODESYS Profinet version 4.2.0.0 is installed with SNMP enabled and accessible, as the vulnerability requires the Profinet SNMP processing component to be reachable by an unauthenticated attacker.
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 dataUpdate to a patched version of CODESYS Profinet when available; meanwhile, restrict SNMP access through network segmentation and firewall rules to prevent unauthenticated external access.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22510 — 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-22510 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