What is CVE-2018-5459?A critical-severity flaw in Pfc200, explained.
CVE-2018-5459 is a critical-severity flaw (CVSS 9.8) in Pfc200 from Wago, published on 13 February 2018. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 2.7%. If you run an affected version, plan in the vendor’s fix.
Published 13 February 2018. Record last updated 9 October 2019. We keep this page's data up to date.
What is CVE-2018-5459? In plain terms.
It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
An Improper Authentication issue was discovered in WAGO PFC200 Series 3S CoDeSys Runtime versions 2.3.X and 2.4.X. An attacker can execute different unauthenticated remote operations because of the CoDeSys Runtime application, which is available via network by default on Port 2455. An attacker could execute some unauthenticated commands such as reading, writing, or deleting arbitrary files, or manipulate the PLC application during runtime by sending specially-crafted TCP packets to Port 2455.
What kind of flaw is it?
- CWE-287Improper Authentication
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAnywhere on the internet
- How hard it is to pull offEasy: no special conditions
- Login needed firstNo login needed
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan read data, change data and take it offline
Severity vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Is CVE-2018-5459 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 2.7%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2018-5459 scores 54. Action: Plan remediation.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2018-5459 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2018-5459? 19 products.
The published record lists 19 products from 1 vendor. Versions are shown as published: "before 02.07.07(10)" means every version up to, but not including, 02.07.07(10). If you run one of these, check your version, then go to the fix below.
- Hardware
Pfc200
by Wago
Affected versionsversion not specified - Hardware
750-8202
by Wago
Affected versionsversion not specified - Hardware
750-8202/025-000
by Wago
Affected versionsversion not specified - Hardware
750-8202/025-001
by Wago
Affected versionsversion not specified - Hardware
750-8202/025-002
by Wago
Affected versionsversion not specified - Hardware
750-8202/040-001
by Wago
Affected versionsversion not specified - Hardware
750-8203
by Wago
Affected versionsversion not specified - Hardware
750-8203/025-000
by Wago
Affected versionsversion not specified - Hardware
750-8204
by Wago
Affected versionsversion not specified
How do I fix CVE-2018-5459? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the latest update from the vendor. The references list where the vendor has published details.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
References
1 linkDoes CVE-2018-5459 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
An Improper Authentication issue was discovered in WAGO PFC200 Series 3S CoDeSys Runtime versions 2.3.X and 2.4.X. An attacker can execute different unauthen...
- Matched to
- Pfc200 on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2018-5459 is a critical-severity flaw in Pfc200 from Wago, published on 13 February 2018. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
It scores 9.8 out of 10 on the CVSS severity scale, which is critical. Our risk score for CVE-2018-5459 is 54 out of 100, which is Medium. Its action is "Plan remediation". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 2.7%. That can change at any time, which is why we keep watching.
For Pfc200 from Wago: version not specified. The record lists 19 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.