Moai Adk
Monthly
Improper link resolution in the MoAI-ADK `moai init` template deployer (all versions through 3.1.2) lets a malicious repository redirect the tool's atomic file write so that it truncates and overwrites files outside the project directory. The deployer stages template content at a path formed by appending a `.moai-tmp` suffix to the destination and does not verify that this staging path is a regular file rather than a symlink, so an attacker who commits a path such as `.claude/settings.json.moai-tmp` pointing elsewhere on disk can cause the write to follow the link when a developer runs `moai init` against the repository. Exploitation is local and requires the victim to clone, trust, and execute the deployer on attacker-controlled content (CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P, assessed as CVSS:3.1/AV:L/AC:L/PR:N/UI:R); no authentication to the tool is required, impact is bounded to files the victim user can already write, and no public exploit code was identified at time of analysis.
Improper link resolution in the MoAI-ADK `moai init` template deployer (all versions through 3.1.2) lets a malicious repository redirect the tool's atomic file write so that it truncates and overwrites files outside the project directory. The deployer stages template content at a path formed by appending a `.moai-tmp` suffix to the destination and does not verify that this staging path is a regular file rather than a symlink, so an attacker who commits a path such as `.claude/settings.json.moai-tmp` pointing elsewhere on disk can cause the write to follow the link when a developer runs `moai init` against the repository. Exploitation is local and requires the victim to clone, trust, and execute the deployer on attacker-controlled content (CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P, assessed as CVSS:3.1/AV:L/AC:L/PR:N/UI:R); no authentication to the tool is required, impact is bounded to files the victim user can already write, and no public exploit code was identified at time of analysis.