Security readout for executives and security teams
Plain-English summary
CVE-2020-22552 is a denial-of-service issue in the Snap7 server component version 1.4.1. A specially formed protocol packet can crash the server. The available sources do not provide a CVSS score, affected product metadata beyond Snap7 1.4.1, or confirmed fix details.
Executive priority
Prioritize exposure discovery and network restriction over emergency response. The issue can disrupt affected Snap7 server availability, but the bundle lacks severity scoring, remediation detail, and active exploitation evidence.
Technical view
The CVE describes a crash in Snap7 server 1.4.1 triggered by crafted COTP/S7 traffic involving a last-data-unit flag set to No and an S7 write-var function. Public metadata does not list CWE, CVSS, CPEs, or vendor remediation details.
Likely exposure
Exposure is most relevant for environments running the Snap7 server component version 1.4.1, especially where that service is reachable by untrusted or loosely controlled network segments. The source bundle does not identify other affected versions or products.
Exploitation context
The sources describe attacker-supplied crafted network traffic causing a server crash. The CVE is not listed as KEV in the bundle, and no cited source confirms active exploitation. Treat exploit status as unconfirmed.
Researcher notes
Evidence is limited to the CVE description and SourceForge references. The core behavior is a crash condition from crafted protocol handling in Snap7 server 1.4.1. Avoid assuming broader version impact, exploit maturity, or patch availability without vendor confirmation.
Mitigation direction
- Inventory Snap7 server deployments and identify any version 1.4.1 instances.
- Check Snap7 project guidance and release notes for fixed versions or workarounds.
- Restrict network access to Snap7 server services to trusted systems only.
- Disable the Snap7 server component where it is not operationally required.
- Monitor affected services for unexpected crashes or restart loops.
Validation and detection
- Confirm whether Snap7 server component version 1.4.1 is deployed.
- Map which hosts and network segments can reach the Snap7 server service.
- Review service logs for unexplained crashes during S7-related traffic.
- Verify firewall or segmentation controls block untrusted access.
- Track vendor or project updates for remediation status.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2020-22552 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://sourceforge.net/p/snap7/discussion/bugfix/thread/456d76fdde/CVE reference, mitre
- https://sourceforge.net/projects/snap7/CVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.