Skip to content
Fencer Intel
high 7.2

CVE-2022-2334 in the critical feed json

Softing Secure Integration Server Uncontrolled Search Path Element

published 4y ago modified 4mo ago also EUVD-2022-34603

cvss
7.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
12.1%
EPSS 12.1% chance of exploitation in 30 days, percentile 96%
public exploits
1
Metasploit

Summary

The application searches for a library dll that is not found. If an attacker can place a dll with this name, then the attacker can leverage it to execute arbitrary code on the targeted Softing Secure Integration Server V1.22.

Is CVE-2022-2334 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

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

cisa ICSA-22-228-04 updated cvss 7.2

Softing Secure Integration Server

  • Softing edgeAggregator 3.1 Softing edgeConnector 3.1 Softing OPC Suite 5.2 Softing OPC UA C++ Server SDK 6 Softing Secure Integration Server <= 1.22 Softing uaGate 1.74
    affected: mitigation “Softing Secure Integration Server: V1.30” industrial.softing.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

Timeline

  1. First public exploit (Metasploit exploit/windows/http/softing_sis_rce)
  2. Published

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

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

Exploits and checks

CVSS scores

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

Affected products

  • Softing Secure Integration Server

Classification

Weakness
  • CWE-427 Uncontrolled Search Path Element

References

Sources

Fencer Intel 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.