Security readout for executives and security teams
Plain-English summary
CVE-2022-31801 is a critical Phoenix Contact issue affecting MULTIPROG, ProConOS, and ProConOS eCLR. The source says an unauthenticated remote attacker could upload malicious logic and gain full device control. For OT environments, this is high business urgency because compromised control logic can affect safety, operations, and availability.
Executive priority
Prioritize this as an OT critical-risk item. The issue combines remote unauthenticated access with potential full device control. Leadership should require immediate asset confirmation, network restriction, and vendor-guidance review before accepting residual risk.
Technical view
The vulnerability is CWE-345, insufficient verification of data. It affects all listed versions of MULTIPROG, ProConOS, and ProConOS eCLR. CVSS 3.1 is 9.8, network exploitable, low complexity, no privileges, and no user interaction, with high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely where devices based on ProConOS or ProConOS eCLR, or MULTIPROG engineering workflows, are reachable from untrusted networks. The bundle does not provide port, protocol, or deployment-specific exposure details.
Exploitation context
The bundle states remote unauthenticated malicious logic upload is possible. It does not cite CISA KEV listing or any public active exploitation evidence. Treat internet-reachable or broadly reachable OT control assets as urgent until vendor guidance and asset validation are complete.
Researcher notes
The public bundle is strong on severity and affected product families but thin on exploit mechanics, patch status, and mitigations. Avoid assuming affected protocols or fixes from the CVE text alone. Validate exposure through asset inventory, network paths, and vendor advisory details.
Mitigation direction
- Inventory MULTIPROG, ProConOS, and ProConOS eCLR deployments immediately.
- Restrict access to affected engineering and runtime interfaces to trusted OT management networks.
- Check Phoenix Contact or VDE guidance for product-specific fixes or mitigations.
- Review controller logic against known-good approved versions.
- Increase monitoring for unauthorized logic uploads or engineering changes.
Validation and detection
- Confirm whether any listed Phoenix Contact products are present in the environment.
- Identify devices based on ProConOS or ProConOS eCLR.
- Determine whether affected systems are reachable from IT, remote-access, or internet paths.
- Review recent engineering changes and uploaded logic for unauthorized modifications.
- Document compensating controls where no vendor fix is confirmed.
Public sources used
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.
CWE-345: 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 lookupCVE-2022-31801 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
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CERTVDEVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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://cert.vde.com/en/advisories/VDE-2022-026/CVE reference, CERTVDE · x_refsource_CONFIRM
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.
Insufficient Verification of Data Authenticity
Insufficient Verification of Data Authenticity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.