In multiple Codesys products in multiple versions, after successful authentication as a user, specially crafted network communication requests can utilize the CmpApp component to download files with any file extensions to the controller. In contrast to the regular file download via CmpFileTransfer, no filtering of certain file types is performed here. As a result, the integrity of the CODESYS control runtime system may be compromised by the files loaded onto the controller.
The product makes files or directories accessible to unauthorized actors, even though they should not be.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Control_for_beaglebone_sl | Codesys | * | 4.10.0.0 (excluding) |
| Control_for_empc-a/imx6_sl | Codesys | * | 4.10.0.0 (excluding) |
| Control_for_iot2000_sl | Codesys | * | 4.10.0.0 (excluding) |
| Control_for_linux_sl | Codesys | * | 4.10.0.0 (excluding) |
| Control_for_pfc100_sl | Codesys | * | 4.10.0.0 (excluding) |
| Control_for_pfc200_sl | Codesys | * | 4.10.0.0 (excluding) |
| Control_for_plcnext_sl | Codesys | * | 4.10.0.0 (excluding) |
| Control_for_raspberry_pi_sl | Codesys | * | 4.10.0.0 (excluding) |
| Control_for_wago_touch_panels_600_sl | Codesys | * | 4.10.0.0 (excluding) |
Web servers, FTP servers, and similar servers may store a set of files underneath a “root” directory that is accessible to the server’s users. Applications may store sensitive files underneath this root without also using access control to limit which users may request those files, if any. Alternately, an application might package multiple files or directories into an archive file (e.g., ZIP or tar), but the application might not exclude sensitive files that are underneath those directories. In cloud technologies and containers, this weakness might present itself in the form of misconfigured storage accounts that can be read or written by a public or anonymous user.