WAGO PFC200 03.02.02(14) iocheckd Service sprintf Argument injection

Summaryinfo

A vulnerability was found in WAGO PFC200 03.02.02(14). It has been classified as critical. Affected by this issue is the function sprintf of the component iocheckd Service. Performing a manipulation as part of Argument results in injection. This vulnerability is reported as CVE-2019-5167. The attack requires a local approach. No exploit exists.

Detailsinfo

A vulnerability classified as critical has been found in WAGO PFC200 03.02.02(14). This affects the function sprintf of the component iocheckd Service. The manipulation as part of a Argument leads to a injection vulnerability. CWE is classifying the issue as CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

An exploitable command injection vulnerability exists in the iocheckd service &acirc;&euro;&tilde;I/O-Check&acirc;&euro;&trade; function of the WAGO PFC 200 version 03.02.02(14). At 0x1e3f0 the extracted dns value from the xml file is used as an argument to /etc/config-tools/edit_dns_server %s dns-server-nr=%d dns-server-name=<contents of dns node> using sprintf(). This command is later executed via a call to system(). This is done in a loop and there is no limit to how many dns entries will be parsed from the xml file.

The weakness was disclosed 03/11/2020. This vulnerability is uniquely identified as CVE-2019-5167 since 01/04/2019. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1055 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The entries VDB-151321, VDB-151320, VDB-151319 and VDB-151318 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• WAGO

Name

• PFC200

Version

• 03.02.02(14)

License

• commercial

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion