Ievgen Bondarenko

A missing authorization vulnerability exists in the internal API `/api/v1/secrets/` of some of Moxa's industrial computing products. A low-privileged authenticated attacker with adjacent network access could exploit this vulnerability to access sensitive information, potentially resulting in the disclosure of confidential data, including cryptographic key material.

A hard-coded cryptographic key vulnerability exists in the `/usr/bin/sysman` of some of Moxa's industrial computing products. An unauthenticated attacker with adjacent network access could exploit the exposed private key material to compromise the confidentiality and integrity of communications.

The device's update mechanism retrieves metadata for software updates over an unencrypted HTTP connection and stores portions of that metadata for later use. A management interface subsequently returns this stored value in a JSON response, and the web interface responsible for displaying update information inserts that value directly into the page as HTML. This behavior allows attacker‑controlled metadata to be interpreted as script content. In addition, the same authenticated origin provides an interface capable of executing system‑level commands with root privileges. An attacker able to influence update metadata could exploit these conditions to execute arbitrary code within the administrative context of the device.

**Name of the Vulnerable Software and Affected Versions** Eclipse Ankaios versions 0.5.1 through 1.0.1 **Description** The agent-side Control Interface authorizer incorrectly evaluates multi-segment allow rules when the first path segment is a wildcard. An authenticated workload restricted by such a rule can submit a `CompleteStateRequest` or `UpdateStateRequest` with an empty field mask. This can lead to the request being incorrectly authorized, enabling the workload to read the complete cluster state or replace state outside its authorized subtree, potentially resulting in unauthorized disclosure or modification of other workloads and cluster configuration. **Recommendations** For versions 0.5.1 through 1.0.1, avoid using multi-segment Control Interface allow-rule filter masks that begin with a wildcard, such as `*.workloads.some workload`, and replace them with explicit paths such as `desiredState.workloads.some workload` where applicable.