Skip to main content
No exploitation reported

CVE-2022-31801

No exploitation reported by the sources we read.

  • Published2022-06-21
  • WeaknessCWE-345

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

An unauthenticated, remote attacker could upload malicious logic to the devices based on ProConOS/ProConOS eCLR in order to gain full control over the device.

Timeline

dates in UTC
  1. 2022-06-2108:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2022-31801?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2022-31801?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Phoenixcontact multiprog
BranchAffectedFixed in
—all versionsno fix published
Phoenixcontact proconos
BranchAffectedFixed in
—all versionsno fix published
Phoenixcontact-software proconos eclr
BranchAffectedFixed in
—all versionsno fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • ICSA-22-172-04 CISA3 known affected

    Phoenix Contact ProConOS and MULTIPROG

    MULTIPROG: All versions · ProConoS: All versions · ProConoS eCLR: All versions

Full record on NVD

Fix

  1. Mitigation from the vendor CISA ICSA-22-172-04 · 3 productsIndustrial controllers based on ProConOS/ProConOS eCLR are typically developed and designed for use in closed industrial networks using a defense-in-depth approach and focusing on network segmentation. In such an approach, the production plant is protected against attacks (especially from the outsi…
  2. Mitigation from the vendor CISA ICSA-22-172-04 · 3 productsManufacturers using ProConOS/ProConOS eCLR in automation devices are advised to check implementation and publish an advisory according to their product.
  3. Mitigation from the vendor CISA ICSA-22-172-04 · 3 productsUsers of automation devices utilizing ProConOS/ProConOS eCLR in their automation systems may check if their application requires additional security measures, such as adequate defense-in-depth networking architecture, the use of virtual private networks (VPNs) for remote access, or the use of firew…
  4. Mitigation from the vendor CISA ICSA-22-172-04 · 3 productsUsers should ensure logic is always transferred or stored in protected environments. This is valid for data in transmission as well as data in rest.
  5. Mitigation from the vendor CISA ICSA-22-172-04 · 3 productsUsers should ensure connections between the engineering tools and the controller are located in a locally protected environment or protected by VPN for remote access.
  6. Mitigation from the vendor CISA ICSA-22-172-04 · 3 productsDo not send project data as a file via email or other transfer mechanisms without additional integrity and authenticity checks. Save project data in protected environments only.

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • CISA-ADPSSVC decisionnone2026-06-02
  • OpenCVESSVC decisionnone—
  • CNACVSS 3.19.8read 2026-10-23
  • NVDCVSS 2.010read 2026-10-23
  • CNAweakness (CWE)CWE-345read 2026-10-23
  • FIRST EPSSEPSS score1.1 %2026-10-23

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2022-06-21
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2022-31801?

An unauthenticated, remote attacker could upload malicious logic to the devices based on ProConOS/ProConOS eCLR in order to gain full control over the device.

Is CVE-2022-31801 actively exploited?

Active exploitation of CVE-2022-31801 has not been confirmed. Its EPSS score was 1.1% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2022-31801?

CVE-2022-31801 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month