T03 · Remote Payload Retrieval and Execution
- Location
INSTALL.md:37- Finding
Remote Bootstrap Script Is Downloaded and Executed Without Integrity Verification
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This knowledge-base skill has useful, coherent features, but it needs Review because installation, updating, LLM processing, and note-writing paths have high-impact access with incomplete scoping and disclosure.
Install only after reviewing the installer and updater behavior. Prefer a virtualenv with locked dependencies, do not use the curl-to-Python bootstrap command, avoid running the OCR sudo installer unless you want host-wide packages installed, keep Ollama bound to localhost unless you intentionally trust the remote endpoint, restrict indexed/source paths to non-sensitive directories, and back up any Obsidian vault before using writer or cleanup commands.
INSTALL.md:37Remote Bootstrap Script Is Downloaded and Executed Without Integrity Verification
kb/update.py:128Updater Installs Unverified Release Archives and Executes Downloaded Migration Code
kb/biblio/generator/essence_generator.py:218Unrestricted Source Files Can Be Transmitted to an Arbitrary Ollama Endpoint
install.sh:33Dependency Installation Is Not Reproducible or Cryptographically Locked
install.sh:20Default Installer Requests System-Wide Administrative Privileges for Optional OCR Support
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
# Symlink entfernen und Backup zurückspielen
rm ~/.openclaw/kb
cp -r <backup-pfad> ~/.openclaw/kb
Setting trust_remote_code=True allows HuggingFace to import and execute Python code supplied by the remote model repository during model loading. If an attacker controls the repository, compromises it, or convinces a user to load an untrusted model, this becomes arbitrary code execution in the local process, which is especially dangerous because this engine runs models in-process and may have access to filesystem, network, secrets, and GPU resources.
The file is presented and scheduled as an audit/check script, but the appended cleanup routine performs DELETE operations on production tables. That mismatch is dangerous because operators may run or reuse the script expecting read-only integrity checks, while the code contains destructive database logic that can remove records and alter evidence during troubleshooting or maintenance.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
test_paths = [
str(Path.home() / "file.txt"),
"relative/path/file.md",
"../../../etc/passwd",
str(Path.home() / "../../../etc/passwd"),
"file\x00.txt",
]
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
test_paths = [
str(Path.home() / "file.txt"),
"relative/path/file.md",
"../../../etc/passwd",
str(Path.home() / "../../../etc/passwd"),
"file\x00.txt",
]
This markdown file documents planned write access to an Obsidian vault, including overwriting, moving, syncing, and deleting notes. Although the operations are described functionally, there is no clear warning to users that these actions can modify or remove existing vault data and should be used carefully.
This markdown file documents VaultWriter methods that create, update, move, replace, and delete notes, which directly affect user data. The section presents these operations as examples but does not include any warning about overwriting, moving, or deleting files in the vault.
The KBUpdate section states that the updater checks GitHub releases and performs forced or normal updates, which implies outbound network access and software changes. The documentation does not warn users that running update commands may contact external services and modify the local installation.
The FileWatcher and TaskScheduler sections describe continuous directory monitoring and scheduled LLM jobs, which can process user documents automatically over time. The markdown does not disclose the privacy or data-handling implications of automatic file observation and downstream LLM processing.
The documentation instructs users to index, sync, and audit local directories, which implies ingestion of potentially sensitive file contents into SQLite and ChromaDB storage. Because there is no prominent warning about what data is collected, where it is stored, and how long it persists, users may unknowingly expose private documents to local indexing and later downstream processing.
The engine-management section documents use of an external Ollama instance but does not clearly warn that prompts or document-derived content may be transmitted to another local or remote service boundary. In a knowledge-base tool, retrieved or generated content can include sensitive indexed material, so lack of disclosure increases the risk of unintended data exposure.
Code scans file system directories looking for sensitive files. This could be reconnaissance for credential theft.
# Prüfe ob Verzeichnis existiert
ls -la ~/.openclaw/kb/chroma_db/
# Repair permissions
chmod 755 ~/.openclaw/kb/chroma_db/
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
ls -la ~/.openclaw/kb/chroma_db/
# Repair permissions
chmod 755 ~/.openclaw/kb/chroma_db/
# Full Re-Sync
kb sync --full
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
Falls ensurepip nicht verfügbar (Debian/Ubuntu):
sudo apt install python3.12-venv
# oder:
python3 -m venv --without-pipe ~/.openclaw/kb/venv
~/.openclaw/kb/venv/bin/python -m ensurepip
The sync command documentation advertises a --delete-orphans option but does not prominently warn that it can remove indexed data. Users may run maintenance commands from examples or habit and unintentionally delete records, especially in a system that synchronizes multiple stores (ChromaDB and SQLite).
The README promotes file watching, indexing, syncing, and LLM-based report generation over user documents without clearly warning that these features may continuously read, transform, and persist potentially sensitive content. In a knowledge-base/agent context, users may reasonably enable these capabilities on personal or enterprise document stores, creating privacy and data-handling risks if they do not understand what content is being processed or retained.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
config = LLMConfig.get_instance()
print(f"Model: {config.model}, Source: {config.model_source}")
# Create engine (single-source or auto mode)
engine = create_engine(config)
# Access registry for multi-engine modes
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
# and explains why they are necessary for the framework's functionality.
================================================================================
WRITE OPERATIONS
================================================================================
1. Indexer (kb/commands/index.py)
The skill advertises file watching and scheduled jobs that can automatically process user content over time, but it gives no warning that monitoring may be continuous and unattended. This is risky because users may enable background processing without understanding that newly added or changed files could be ingested and sent through LLM-related workflows automatically.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
# Add to .bashrc for global access:
alias kb="bash ~/.openclaw/kb/kb.sh"
source ~/.bashrc
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
config = LLMConfig.get_instance()
print(f"Source: {config.model_source}")
# Create engine (auto mode mit HF primary + Ollama fallback)
engine = create_engine(config)
# Registry für Multi-Engine Zugriff
The documentation explicitly describes storing absolute file paths, metadata, and full section content in local databases, but does not warn users that sensitive local content will be persistently collected and indexed. In a knowledge-base skill that processes arbitrary user files, this creates a real privacy and data-exposure risk if users index confidential material or if the database is later accessed by other local processes.
The documentation recommends a deletion-capable orphan cleanup command without any caution about data removal or recovery. Users could run destructive cleanup against misdetected or recently moved content and lose indexed records or associated data unintentionally.
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
# 1. System-Dependencies: Tesseract OCR + Sprachpakete
if ! command -v tesseract &> /dev/null; then
echo "Installing tesseract-ocr..."
sudo apt-get update -qq 2>/dev/null || true
sudo apt-get install -y -qq tesseract-ocr tesseract-ocr-deu tesseract-ocr-eng 2>/dev/null || \
apt-get install -y tesseract-ocr tesseract-ocr-deu tesseract-ocr-eng 2>/dev/null || \
echo -e "${YELLOW}⚠️ Tesseract-Installation fehlgeschlagen (keine Root-Rechte?)${NC}"
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
# 1. System-Dependencies: Tesseract OCR + Sprachpakete
if ! command -v tesseract &> /dev/null; then
echo "Installing tesseract-ocr..."
sudo apt-get update -qq 2>/dev/null || true
sudo apt-get install -y -qq tesseract-ocr tesseract-ocr-deu tesseract-ocr-eng 2>/dev/null || \
apt-get install -y tesseract-ocr tesseract-ocr-deu tesseract-ocr-eng 2>/dev/null || \
echo -e "${YELLOW}⚠️ Tesseract-Installation fehlgeschlagen (keine Root-Rechte?)${NC}"