Home/CVE/Multiple Phoenix Contact devices allow remote attackers to establish TCP sessions to port 1962 and obtain sensitive info
CVE
↯ PDF report

CVE-2019-92012

Multiple Phoenix Contact devices allow remote attackers to establish TCP sessions to port 1962 and obtain sensitive info

Multiple Phoenix Contact devices allow remote attackers to establish TCP sessions to port 1962 and obtain sensitive information or make changes, as demonstrated by using the Create Backup feature to traverse all directories.

CRITICAL · CVSS 9.8 EPSS 0.03079
EPSS exploitation odds3.08% · top 13%
Act now
  • Public exploit or PoC is available
  • SSVC automatable: yes - attacks can be scripted at scale
  • CVSS base score ≥ 7.0
No Sigma yet — build one → YARA rules0
Look this up elsewhere - one-click external pivots
NVDCVE.orgCISAExploit-DBGitHub PoCVulnCheck KEVGreyNoise
▸ How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2019-9201, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked. EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal. CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score. Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits. PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
⚠

Exploitation evidence

1 of 7 sources
Corroboration score 8/100 · emerging. This counts how many independent sources have exploitation evidence, and separates two different things: confirmed in-the-wild use (CISA KEV, Microsoft MSRC, ransomware activity) from exploit / PoC availability (Metasploit, ExploitDB, Nuclei, public PoCs). A template or PoC existing means an attack is possible and easy - it is not, on its own, proof the CVE is being exploited in the wild.
Exploit / PoC available
public PoC
↗

Exploitation momentum

1237 days of EPSS
dormant
Flat and low - no real exploitation pressure. This reads the direction and speed of EPSS over time, which can move before EPSS itself peaks or before CISA lists it.
Window
▣

Severity & exploitation scoring

View on NVD →
CVSS base score
9.8
CRITICALCVSS v3.1 · [email protected]
EPSS exploitation probability
3.08%
Top 13%odds of exploitation in the next 30 days
CVSS metric silhouette
VectorComplexityPrivilegesInteractionScopeConfidentialityIntegrityAvailability
shape grows toward worst-case
SSVC triage · cisa-vulnrichment
Exploitation
poc
Automatable
yes
Tech impact
total
CVSS vector breakdown
Exploitability - how they get in
Attack Vector
Network Adjacent Local Physical
Attack Complexity
Low High
Privileges Required
None Low High
User Interaction
None Required
Scope
Unchanged Changed
Impact - what breaks
Confidentiality
None Low High
Integrity
None Low High
Availability
None Low High
VECTORCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Lifecycle
  1. 26 Feb 2019Published to NVD
  2. 17 Jun 2026Last modified
Every entry is a recorded date - NVD publish/modify, CISA KEV add, public exploit disclosure. No inferred events.
Attack path
Full kill chain
→
⚠

Public Exploits & PoCs

2
These PoC and exploit links come from public sources and are not verified to be safe or functional. Review the code before running anything, and treat unverified entries as untrusted. Signed-in users mark whether it works, rate 1-10, and can report malware with a required reason that becomes a public comment.
poc Public PoC (nvd-reference)↗ date unknown
⋮
Vote & rate
Report or claim
⚠ Report this PoC

Becomes a public comment attributed as First L. (never full last name). Don't include private info. Rate-limited: 5/hour.

Works? no reports yet
Rating -
poc medium.com · misconfiguration-in-ilc-gsm-gprs-devices-leaves-over-1-20...↗ medium.com
⋮
Vote & rate
Report or claim
⚠ Report this PoC

Becomes a public comment attributed as First L. (never full last name). Don't include private info. Rate-limited: 5/hour.

Works? no reports yet
Rating -
◆

ATT&CK techniques

1

Techniques this CVE enables. Pills with a solid outline are high confidence - named directly in ATT&CK or Nuclei, or human-curated by CTID; the rest are inferred from the weakness type using MITRE's CVE Mapping Methodology and the CWE → CAPEC chain. Broad, generic-weakness guesses are filtered out. A small N× marks a technique that N independent sources agree on.

T1190 · Exploit Public-Facing Application
▤ Build a SIEM detection for these techniques
▤

CAPEC attack patterns

5

Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.

CAPEC-CAPEC-12 · Choosing Message Identifier CAPEC-CAPEC-166 · Force the System to Reset Values CAPEC-CAPEC-216 · Communication Channel Manipulation CAPEC-CAPEC-36 · Using Unpublished Interfaces or Functionality CAPEC-CAPEC-62 · Cross Site Request Forgery
⬡

Weakness Classification

CWE-306Missing Authentication for Critical Function
CWE-306Missing Authentication for Critical Function
▤

Affected Products & Versions

8
phoenixcontact ilc 131 eth firmwareall versions
phoenixcontact ilc 131 eth\/xc firmwareall versions
phoenixcontact ilc 151 eth firmwareall versions
phoenixcontact ilc 151 eth\/xc firmwareall versions
phoenixcontact ilc 171 eth 2tx firmwareall versions
phoenixcontact ilc 191 eth 2tx firmwareall versions
phoenixcontact ilc 191 me\/an firmwareall versions
phoenixcontact axc 1050 firmwareall versions
▤

Related CVEs

8
CVEs linked to this one by a shared weakness (CWE) or affected product - joins on data already in the engine, with the reason shown per row.
CVE-2002-1810 D-Link DWL-900AP+ Access Point 2.1 and 2.2 allows remote attackers to access the... same CWE-306 HIGH CVE-2004-0213 Utility Manager in Windows 2000 launches winhlp32.exe while Utility Manager is r... 4 same CWE-306 HIGH CVE-2006-0061 xlockmore 5.13 and 5.22 segfaults when using libpam-opensc and returns the under... same CWE-306 CRITICAL CVE-2006-0062 xlockmore 5.13 allows potential xlock bypass when FVWM switches to the same virt... same CWE-306 CRITICAL CVE-2022-31800 An unauthenticated, remote attacker could upload malicious logic to devices base... same product CRITICAL CVE-2023-46141 Incorrect Permission Assignment for Critical Resource vulnerability in multiple ... same product CRITICAL CVE-2023-46143 Download of Code Without Integrity Check vulnerability in PHOENIX CONTACT classi... same product HIGH CVE-2019-10953 ABB, Phoenix Contact, Schneider Electric, Siemens, WAGO - Programmable Logic Con... same product HIGH
⚑

Vendor Advisories

1
cisa-csafcisa-csaf-csaf_files-OT-white-2022-icsa-22-172-05
🔗

References & Sources

1
Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.
https://cert.vde.com/en/advisories/VDE-2019-015/
Third Party Advisory
◈SOC and Response
◆Detection Engineering
◎Threat Hunting
▲Red Team and Pentest
■Compliance and GRC
◯About
threatengine.sh Crafted with love in Toronto, Canada