Home/CVE/An unauthenticated, remote attacker could upload malicious logic to devices based on ProConOS/ProConOS eCLR in order to
CVE
CVE-2022-318002
An unauthenticated, remote attacker could upload malicious logic to devices based on ProConOS/ProConOS eCLR in order to
An unauthenticated, remote attacker could upload malicious logic to devices based on ProConOS/ProConOS eCLR in order to gain full control over the device.
CRITICAL · CVSS 9.8
EPSS 0.01455
EPSS exploitation odds1.46% · top 29%
Act now
- Public exploit or PoC is available
- SSVC automatable: yes - attacks can be scripted at scale
- CVSS base score ≥ 7.0
No Sigma yet — build one →
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2022-31800, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
⚠
Exploitation evidence
1 of 7 sources
Corroboration score 8/100 ·
emerging.
This counts how many independent sources have exploitation evidence, and separates two different things:
confirmed in-the-wild use (CISA KEV, Microsoft MSRC, ransomware activity) from
exploit / PoC availability (Metasploit, ExploitDB, Nuclei, public PoCs). A template or PoC existing means
an attack is possible and easy - it is not, on its own, proof the CVE is being exploited in the wild.
Exploit / PoC available
public PoC
↗
Exploitation momentum
1098 days of EPSSdormant
Flat and low - no real exploitation pressure. This reads the direction and speed of EPSS over time, which can move before EPSS itself peaks or before CISA lists it.
EPSS exploitation probability
1.46%
Top 29%odds of exploitation in the next 30 days
CVSS metric silhouette
shape grows toward worst-case
SSVC triage · cisa-vulnrichment
Exploitation
none
Automatable
yes
Tech impact
total
CVSS vector breakdown
Exploitability - how they get in
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Impact - what breaks
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
VECTOR
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HLifecycle
- 21 Jun 2022Published to NVD
- 17 Jun 2026Last modified
Every entry is a recorded date - NVD publish/modify, CISA KEV add, public exploit disclosure. No inferred events.
Attack path
Full kill chain
⚠
Public Exploits & PoCs
2These PoC and exploit links come from public sources and are not verified to be safe or functional. Review the code before running anything, and treat unverified entries as untrusted. Signed-in users mark whether it works, rate 1-10, and can report malware with a required reason that becomes a public comment.
Source
Works?
no reports yet
Rating
Works?
no reports yet
Rating
◆
ATT&CK techniques
1Techniques this CVE enables. Pills with a solid outline are high confidence - named directly in ATT&CK or Nuclei, or human-curated by CTID; the rest are inferred from the weakness type using MITRE's CVE Mapping Methodology and the CWE → CAPEC chain. Broad, generic-weakness guesses are filtered out. A small N× marks a technique that N independent sources agree on.
▤ Build a SIEM detection for these techniques▤
CAPEC attack patterns
12Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.
CAPEC-CAPEC-111 · JSON Hijacking (aka JavaScript Hijacking) CAPEC-CAPEC-141 · Cache Poisoning CAPEC-CAPEC-142 · DNS Cache Poisoning CAPEC-CAPEC-148 · Content Spoofing CAPEC-CAPEC-218 · Spoofing of UDDI/ebXML Messages CAPEC-CAPEC-384 · Application API Message Manipulation via Man-in-the-Middle CAPEC-CAPEC-385 · Transaction or Event Tampering via Application API Manipulation CAPEC-CAPEC-386 · Application API Navigation Remapping CAPEC-CAPEC-387 · Navigation Remapping To Propagate Malicious Content CAPEC-CAPEC-388 · Application API Button Hijacking CAPEC-CAPEC-665 · Exploitation of Thunderbolt Protection Flaws CAPEC-CAPEC-701 · Browser in the Middle (BiTM)
⬡
Weakness Classification
▤
Affected Products & Versions
17phoenixcontact axc 1050 firmwareall versions
phoenixcontact axc 1050 xc firmwareall versions
phoenixcontact axc 3050 firmwareall versions
phoenixcontact fc 350 pci eth firmwareall versions
phoenixcontact ilc1x0 firmwareall versions
phoenixcontact ilc1x1 firmwareall versions
phoenixcontact ilc 1x1 gsm\/gprs firmwareall versions
phoenixcontact ilc 3xx firmwareall versions
phoenixcontact pc worx rt basic firmwareall versions
phoenixcontact pc worx srt firmwareall versions
phoenixcontact rfc 430 eth-ib firmwareall versions
phoenixcontact rfc 450 eth-ib firmwareall versions
phoenixcontact rfc 460r pn 3tx firmwareall versions
phoenixcontact rfc 460r pn 3tx-s firmwareall versions
phoenixcontact rfc 470 pn 3tx firmwareall versions
phoenixcontact rfc 470s pn 3tx firmwareall versions
phoenixcontact rfc 480s pn 4tx firmwareall versions
▤
Related CVEs
8CVEs linked to this one by a shared weakness (CWE) or affected product - joins on data already in the engine, with the reason shown per row.
CVE-2013-7397
Async Http Client (aka AHC or async-http-client) before 1.9.0 skips X.509 certif...
same CWE-345
CVE-2013-7398
main/java/com/ning/http/client/AsyncHttpClientConfig.java in Async Http Client (...
same CWE-345
CVE-2013-2167
python-keystoneclient version 0.2.3 to 0.2.5 has middleware memcache signing byp...
same CWE-345
CRITICAL
CVE-2014-0364
The ParseRoster component in the Ignite Realtime Smack XMPP API before 4.0.0-rc1...
same CWE-345
CVE-2019-9201
Multiple Phoenix Contact devices allow remote attackers to establish TCP session...
same product
CRITICAL
CVE-2023-46141
Incorrect Permission Assignment for Critical Resource vulnerability in multiple ...
same product
CRITICAL
CVE-2023-46143
Download of Code Without Integrity Check vulnerability in PHOENIX CONTACT classi...
same product
HIGH
CVE-2021-33541
Phoenix Contact Classic Line Controllers ILC1x0 and ILC1x1 in all versions/varia...
same product
HIGH
⚑
Vendor Advisories
1cisa-csafcisa-csaf-csaf_files-OT-white-2022-icsa-22-172-03