You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is potentialyl very dangerous because the attacker could upload .env file, ssh keys or other secrets
To Reproduce
I have not tried to reproduce this, but it seems pretty obvious that an agent with 0g plugin enabled would not have an issue with uploading any filepath parsed by the template
Expected behavior
No private files are uploaded ever.
This could involve multiple approaches and risks should be highlighted to agent operator.
The template should check for potential security issues (assuming LLMs would generally understand where private files are stored)
More secure option would be to limit the filePath to some safe subdir, make it configurable in .env and then prefix or match the filePath with the prefix
Screenshots
Additional context
The text was updated successfully, but these errors were encountered:
Describe the bug
Looking at 0g plugin, it seems it will allow anyone interacting with the agent to upload any file from the filesystem
https://github.com/elizaOS/eliza/blob/main/packages/plugin-0g/src/actions/upload.ts#L111
This is potentialyl very dangerous because the attacker could upload .env file, ssh keys or other secrets
To Reproduce
I have not tried to reproduce this, but it seems pretty obvious that an agent with 0g plugin enabled would not have an issue with uploading any filepath parsed by the template
Expected behavior
No private files are uploaded ever.
This could involve multiple approaches and risks should be highlighted to agent operator.
The template should check for potential security issues (assuming LLMs would generally understand where private files are stored)
More secure option would be to limit the
filePath
to some safe subdir, make it configurable in .env and then prefix or match thefilePath
with the prefixScreenshots
Additional context
The text was updated successfully, but these errors were encountered: