CVE-2022-31800: Insufficient Verification of Data Vulnerability in PHOENIX CONTACT classic line industrial controllers
Noroxi assessment
Priority: Monitor (action score 39/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.5% (FIRST EPSS); higher than 76% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- According to the record, no fixed version is available yet.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An unauthenticated, remote attacker could upload malicious logic to devices based on ProConOS/ProConOS eCLR in order to gain full control over the device.
- Published
- Jun 21, 2022
- Updated
- Jun 17, 2026
- EPSS
- 1.5% · 76th percentile
- CWE
- CWE-345
Report tools
Action score
39
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · CERTVDE
- 9.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| phoenixcontact | axc 1050 firmware | cpe:2.3:o:phoenixcontact:axc_1050_firmware |
| phoenixcontact | axc 1050 | cpe:2.3:h:phoenixcontact:axc_1050 |
| phoenixcontact | axc 1050 xc firmware | cpe:2.3:o:phoenixcontact:axc_1050_xc_firmware |
| phoenixcontact | axc 1050 xc | cpe:2.3:h:phoenixcontact:axc_1050_xc |
| phoenixcontact | axc 3050 firmware | cpe:2.3:o:phoenixcontact:axc_3050_firmware |
| phoenixcontact | axc 3050 | cpe:2.3:h:phoenixcontact:axc_3050 |
| phoenixcontact | fc 350 pci eth firmware | cpe:2.3:o:phoenixcontact:fc_350_pci_eth_firmware |
| phoenixcontact | fc 350 pci eth | cpe:2.3:h:phoenixcontact:fc_350_pci_eth |
| phoenixcontact | ilc1x0 firmware | cpe:2.3:o:phoenixcontact:ilc1x0_firmware |
| phoenixcontact | ilc1x0 | cpe:2.3:h:phoenixcontact:ilc1x0 |
| phoenixcontact | ilc1x1 firmware | cpe:2.3:o:phoenixcontact:ilc1x1_firmware |
| phoenixcontact | ilc1x1 | cpe:2.3:h:phoenixcontact:ilc1x1 |
and 22 more
Versions reported by the vendor
Affected version ranges reported by the assigning authority (CERTVDE). Independent of NVD's CPE analysis and usually ahead of it.
PHOENIX CONTACT AXC 1050
- All Versionsaffected
PHOENIX CONTACT AXC 1050 XC
- All Versionsaffected
PHOENIX CONTACT AXC 3050
- All Versionsaffected
PHOENIX CONTACT FC 350 PCI ETH
- All Versionsaffected
PHOENIX CONTACT ILC 1x0
- All Versionsaffected
PHOENIX CONTACT ILC 1x1
- All Versionsaffected
PHOENIX CONTACT ILC 1x1 GSM/GPRS
- All Versionsaffected
PHOENIX CONTACT ILC 3xx
- All Versionsaffected
PHOENIX CONTACT PC WORX RT BASIC
- All Versionsaffected
PHOENIX CONTACT PC WORX SRT
- All Versionsaffected
PHOENIX CONTACT RFC 430 ETH-IB
- All Versionsaffected
PHOENIX CONTACT RFC 450 ETH-IB
- All Versionsaffected
Affected versions · NVD (17)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- phoenixcontact axc 1050 firmwareall versions
- phoenixcontact axc 1050 xc firmwareall versions
- phoenixcontact axc 3050 firmwareall versions
- phoenixcontact fc 350 pci eth firmwareall versions
- phoenixcontact ilc 1x1 gsm/gprs firmwareall versions
- phoenixcontact ilc 3xx firmwareall versions
- phoenixcontact ilc1x0 firmwareall versions
- phoenixcontact ilc1x1 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
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-22-0444 · Jun 22, 2022(PHOENIX Endüstriyel Ürünler Güvenlik Bildirimi)
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-345 · Insufficient Verification of Data AuthenticityCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- JSON Hijacking (aka JavaScript Hijacking)CAPEC-111likelihood: High · High
- Cache PoisoningCAPEC-141likelihood: High · High
- DNS Cache PoisoningCAPEC-142likelihood: High · High
- Content SpoofingCAPEC-148likelihood: Medium · Medium
- Spoofing of UDDI/ebXML MessagesCAPEC-218Medium
- Application API Message Manipulation via Man-in-the-MiddleCAPEC-384Low
- Transaction or Event Tampering via Application API ManipulationCAPEC-385Medium
- Application API Navigation RemappingCAPEC-386Medium
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.