Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2019-14927: Unauthenticated Configuration Download in Mitsubishi Electric/INEA ME-RTU

Published Oct 28, 2019 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v3.1
EPSS40.9%99th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendors
IneaMitsubishi Electric Corporation
IdentifiersCVE-2019-14927CWE-200

CVE-2019-14927 is a vulnerability in Mitsubishi Electric Europe B.V. ME-RTU devices through version 2.02 and INEA ME-RTU devices through version 3.0. The vulnerability allows an unauthenticated remote attacker to download the smartRTU's configuration file, which contains sensitive information such as usernames, passwords, and other RTU data. The flaw is due to insufficient authentication controls on the configuration download functionality.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An unauthenticated attacker can remotely obtain the configuration file, exposing sensitive credentials and operational data. This can lead to further compromise of the device, unauthorized access to the RTU, and potentially broader network compromise if the credentials are reused or privileged.

Mitigation

If you can’t patch tonight, do this now.

Restrict network access to the affected devices to trusted hosts only, implement network segmentation, and monitor for unauthorized access attempts. Where possible, disable remote configuration download functionality or enforce strong authentication controls via compensating controls such as VPNs or firewalls.

Remediation

Patch, then assume compromise.

Upgrade ME-RTU devices to a version beyond 2.02 and INEA ME-RTU devices to a version beyond 3.0 where this vulnerability is addressed. Apply vendor-provided patches or firmware updates that enforce authentication for configuration downloads.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
IneaMe Rtu Firmwareoperating_system
Mitsubishi Electric CorporationSmartrtu Firmwareoperating_system
FAQ

Frequently asked questions

Is CVE-2019-14927 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2019-14927?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2019-14927.
Is there a patch for CVE-2019-14927?
Upgrade ME-RTU devices to a version beyond 2.02 and INEA ME-RTU devices to a version beyond 3.0 where this vulnerability is addressed. Apply vendor-provided patches or firmware updates that enforce authentication for configuration downloads.
What products are affected by CVE-2019-14927?
Inea Me Rtu Firmware and Mitsubishi Electric Corporation Smartrtu Firmware.
How severe is CVE-2019-14927?
CVE-2019-14927 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 40.9% (99th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware2Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.