Skip to content
Fencer Vulns
high 7.8

CVE-2022-3461 json

Buffer Overflow in PHOENIX CONTACT Automationworx Software Suite

published 2022-11-15 3 y ago modified 2026-06-17 4 mo ago also EUVD-2022-42833

cvss
7.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 11%
public exploits
0
none known

Summary

In PHOENIX CONTACT Automationworx Software Suite up to version 1.89 manipulated PC Worx or Config+ files could lead to a heap buffer overflow and a read access violation. Availability, integrity, or confidentiality of an application programming workstation might be compromised by attacks using these vulnerabilities.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-22-326-03 updated cvss 7.8

Phoenix Contact Automation Worx

  • Phoenix Contact Automation Worx Config+ <= 1.89 Phoenix Contact Automation Worx PC Worx <= 1.89 Phoenix Contact Automation Worx PC Worx Express <= 1.89
    affected: mitigation “CERT@VDE has released an advisory on these vulnerabilities, accessible here.” phoenixcontact.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
18 mo ago

Exploit prediction

0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected products

  • PHOENIX CONTACT Config+
  • PHOENIX CONTACT PC Worx
  • PHOENIX CONTACT PC Worx Express

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.