Threat Intelligence Database

NanoClaw before 2.1.0 contains a privilege escalation vulnerability in the channel-registration approval flow where handleChannelApprovalResponse fails to validate admin privileges over target agent groups. Scoped admins can submit forged or stale connect callback values to wire messaging channels into out-of-scope agent groups, exposing unauthorized groups to unapproved channels and enabling unauthorized observation or control of restricted agent group activity.

NanoClaw before 2.1.17 contains a privilege escalation vulnerability in the create_agent delivery-action handler that performs privileged central-database writes without host-side authorization checks. Confined agent containers can invoke create_agent to create arbitrary agent groups, container configurations, and destinations, escalating beyond their intended confinement boundary.

NanoClaw versions before 2.1.17 contain a symlink following vulnerability in the forwardAttachedFiles function. This flaw allows container-controlled agents to exfiltrate files readable by the host system. The vulnerability arises because the host only validates attachment filenames with isSafeAttachmentName before copying files using fs.copyFileSync, which follows symlinks without containment checks. This can lead to disclosure of arbitrary host files.

NanoClaw before 2.1.17 contains a privilege escalation vulnerability in the handleApprovalsResponse function that fails to verify responder role authorization. Attackers with a valid questionId can approve or reject privileged actions like package installation by submitting approval response payloads without proper role validation.