LiveActive security incident?Get immediate response
CVE Record

CVE-2018-4850: A vulnerability has been identified in SIMATIC S7-400 (incl.

A vulnerability has been identified in SIMATIC S7-400 (incl. F) CPU hardware version 4.0 and below (All versions), SIMATIC S7-400 (incl. F) CPU hardware version 5.0 (All firmware versions < V5.2), SIMATIC S7-400H CPU hardware version 4.5 and below (All versions). The affected CPUs improperly validate S7 communication packets which could cause a Denial-of-Service condition of the CPU. The CPU will remain in DEFECT mode until manual restart.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This issue can stop affected Siemens SIMATIC S7-400 CPUs by triggering a denial-of-service condition. The controller remains in DEFECT mode until someone manually restarts it, so the business risk is operational interruption rather than data theft. Likely exposure is limited to environments running the listed SIMATIC S7-400 or S7-400H CPU hardware and firmware versions. Risk is highest where S7 communication is reachable from less-trusted networks, engineering workstations, remote access paths, or shared industrial network segments. Prioritize if these PLCs support production, safety-adjacent operations, or high-availability industrial processes. The issue can create downtime requiring manual recovery, so urgency depends on controller criticality and network reachability. Mitigation focus: Review Siemens SSA-914382 for official remediation guidance.; Update S7-400 hardware version 5.0 firmware to V5.2 or later where applicable.; For all-versions-affected hardware, confirm Siemens-supported replacement or compensating controls..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

cwe · low confidence lookup

CWE-20: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-4850 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Siemens AGSIMATIC S7-400 (incl. F) CPU hardware version 4.0 and below, SIMATIC S7-400 (incl. F) CPU hardware version 5.0, SIMATIC S7-400H CPU hardware version 4.5 and belowSIMATIC S7-400 (incl. F) CPU hardware version 4.0 and below : All versions, SIMATIC S7-400 (incl. F) CPU hardware version 5.0 : All firmware versions < V5.2, SIMATIC S7-400H CPU hardware version 4.5 and below : All versionsListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-20 · source CWE mapping

Improper Input Validation

Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.