CVE-2022-25622
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 · uneditedThe PROFINET (PNIO) stack, when integrated with the Interniche IP stack, improperly handles internal resources for TCP segments where the minimum TCP-Header length is less than defined. This could allow an attacker to create a denial of service condition for TCP services on affected devices by sending specially crafted TCP segments.
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 confidenceThe PROFINET (PNIO) stack improperly handles internal resources when processing TCP segments with malformed or undersized TCP headers when integrated with the Interniche IP stack. An attacker can send specially crafted TCP segments with insufficient header length to trigger the improper resource handling, causing a denial of service for TCP services on affected devices.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versions< 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 device modelLocate the Siemens Simatic device and confirm the exact model number (CFU DIQ, CFU PA, S7-300 CPU, S7-400H V6, S7-400 Pn/dp V7, S7-410 V8, S7-410 V10, or S7-1500 CPU) from the device label or management interface.Affected if The device model is any of the affected products listed in the CVE.
-
Check S7-1500 firmware versionFor S7-1500 CPU only: access the device via TIA Portal or web server and locate the firmware version information under Device Properties or Overview. Compare the version number against the affected range.Affected if The device is an S7-1500 CPU with firmware version prior to 2.0.0.
-
Confirm PROFINET stack is activeCheck the device configuration via TIA Portal or device web interface to verify that PROFINET (PNIO) or TCP/IP communication services are enabled and configured.Affected if PROFINET or TCP services are enabled - the vulnerability only triggers when the PROFINET stack processes incoming TCP segments.
-
Assess network exposure of TCP servicesReview network segmentation and firewall rules to determine if the device TCP ports (commonly port 102 for S7 communication, port 80/443 for web management) are accessible from untrusted or external networks.Affected if TCP services on the device are exposed to untrusted network segments or the internet.
Your environment is affected if you operate any of the listed Siemens Simatic devices (S7-1500 CPU below version 2.0.0, or any firmware version for other listed models) with PROFINET/TCP services enabled and accessible to potential attackers.
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 data2.0.0
Update the PROFINET device firmware to a version that includes the corrected Interniche IP stack with proper TCP header length validation. If no update is available, implement network segmentation and firewall rules to restrict untrusted traffic from reaching affected devices.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25622 — 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-25622 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