CVE-2014-9195

highpriority · attend · 68OT risk · highEPSS 0.807 · 100 %ileexploit · functionalDEEUUS
grimoire priorityP1 · Urgent
Exploitable?
Public exploit
2 exploits · functional
Likely / severe?
80.7% (100th) EPSS
CVSS 7.5 · high
Is it mine?
16 products
Check your exposure
Who says so?
6 sources
cnnvd · enisa_euvd · cert_bund · cisa_csaf_ot

EPSS · scored 2026-10-22

Phoenix Contact ProConOs and MultiProg do not require authentication, which allows remote attackers to execute arbitrary commands via protocol-compliant traffic.

01

remediations

Vendor fix, mitigation, or workaround guidance, as published by each source.

A vendor fix is available.

  • FixedRTU500 series CMU Firmwarecisa_csaf_ot

    Upgrade to version 12.7.8 or 13.9.1 or latest

  • Mitigationphoenix_contact_psirt

    Manufacturers using ProConOS/ProConOS eCLR in their automation devices are advised to check their implementation and may publish an advisory according to their product. Users of automation devices utilizing ProConOS/ProConOS eCLR in their automation systems may check if their application requires additional security measures like an adequate defense– in-depth networking architecture, the use of virtual private networks (VPNs) for remote access, as well as the use of firewalls for network segmentation or controller isolation. Users should check their manufacturers security advisories for more adequate information according to their dedicated device. Generic information and recommendations for security measures to protect network-capabledevices can be found in the application note.

  • MitigationMultiProgcisa_csaf_ot

    Phoenix Contact Software designed the applications and protocols without authentication mechanisms. It is the understanding of Phoenix Contact Software that vendors using the application software and its protocol would incorporate its own authentication mechanism in its final product. Phoenix Contact Software is considering adding authentication software into future versions of its application software and its protocol.

  • MitigationProConOscisa_csaf_ot

    Phoenix Contact Software designed the applications and protocols without authentication mechanisms. It is the understanding of Phoenix Contact Software that vendors using the application software and its protocol would incorporate its own authentication mechanism in its final product. Phoenix Contact Software is considering adding authentication software into future versions of its application software and its protocol.

02

cvss

Technical severity, 0–10. One row per scoring source.

10.0
010

base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · high–critical · 7.5–10

v2.07.5highAV:N/AC:L/Au:N/C:P/I:P/A:Pprimary · NVD / NIST USexploitability 10 · impact 6.4
v2.010criticalAV:N/AC:L/Au:N/C:C/I:C/A:Csecondary · CISA US
v2.010criticalAV:N/AC:L/Au:N/C:C/I:C/A:Csecondary · ENISA EU
v2.010highAV:N/AC:L/Au:N/C:C/I:C/A:Csecondary · ics-cert@hq.dhs.gov USexploitability 10 · impact 10
v2.07.5highAV:N/AC:L/Au:N/C:P/I:P/A:P/E:Hsecondary · CVSS-BT (t0sche)
v3.18.1highCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:Hsecondary · CISA US
03

weaknesses

The CWE weakness classes this flaw belongs to.

04

exploits (2)

Public proof-of-concept and weaponised exploit code.

05

affected products (16)

Products and version ranges known to be affected.

06

advisories (4)

Vendor and ecosystem advisories describing this.

  • VDE-2022-028PHOENIX CONTACT: Missing Authentication in ProConOS/ProConOS eCLR SDK and MULTIPROG Engineering tool2022-06-21csaf · phoenix_contact_psirtDE

    ProConOS/ProConOS eCLR designed for use in closed industrial networks provide communication protocols without authentication. Please also refer the original ICS-CERT advisory ICSA-15-013-03 published 13 January 2015.

  • WID-SEC-W-2026-3658Hitachi Energy RTU500: Mehrere SchwachstellenDeutsch2026-09-29csaf · cert_bundDE

    Ein Angreifer kann mehrere Schwachstellen in Hitachi Energy RTU500 ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, die Gerätefunktionalität zu verändern oder Denial-of-Service-Zustände zu verursachen.

  • ICSA-15-013-03Phoenix Contact Software ProConOs and MultiProg Authentication Vulnerability2015-10-16icsa · cisa_csaf_otUS

    This CSAF advisory was extracted from unstructured data and may contain inaccuracies. If you notice any errors, please reach out to the designated contact at CISA CSAF: central@cisa.dhs.gov

  • ICSA-26-279-06Hitachi Energy RTU5002026-09-29icsa · cisa_csaf_otUS

    Hitachi Energy is publishing this cybersecurity advisory in response to the security findings reported by Dragos affecting end-of-life RTU500 CMU firmware version 9.x. The reported findings are associated with legacy RTU500 firmware versions that were developed according to the cybersecurity requirements, threat landscape, and industry practices that existed at the time of their release. As cybersecurity threats and security expectations have evolved, these end-of-life versions no longer incorporate many of the security controls and hardening measures that are standard in modern industrial control systems. Over successive RTU500 releases, Hitachi Energy has continuously enhanced the security of the product through the introduction of additional security features, protocol hardening, stronger authentication and access controls, encrypted communications, and other security-by-design improvements. While the findings reported by Dragos do not affect currently supported RTU500 CMU firmware versions, there is a likelihood that the end-of-life versions 11.x and prior are affected by these vulnerabilities. Since the end-of-life versions are no longer maintained with security updates, Hitachi Energy strongly recommends upgrading to a currently supported RTU500 firmware version. Customers should also implement appropriate defense-in-depth measures and cybersecurity best practices to reduce risk and strengthen the security posture of their operational environments. Please refer to the Recommended Immediate Actions for information about the mitigation/remediation.

07

also known as (3)

Other names and identifiers for this entity.

08

sources

Which sources assert this record, and when.

09

references (7)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan