Habilidades revdoku Historial de auditorías
📦

Historial de auditorías

revdoku - 1 auditoría

8 sept 2026, 08:19

The skill is a static-site publishing CLI with legitimate network, filesystem, and credential operations; most pattern matches are benign documentation, exclusions, or quoted shell usage. Publication is not recommended without remediation because the documented installer executes unverified remote code, and the CLI has credential and repository-binding trust-boundary weaknesses. Static review was capped at 400/670 representative findings; omitted static matches are unconfirmed, so automatic publishing stays disabled until manual review.

3
Archivos escaneados
3,321
Líneas analizadas
9
Elementos de revisión
0
Falsos positivos ignorados

Preocupaciones de seguridad confirmadas (5)

Crítico
Pipe to shell pattern
curl -fsSL https://revdoku.com/install.sh | bash
The documentation instructs users to download an installer over HTTPS and execute it directly with bash. The downloaded script is not pinned or verified before execution.
Crítico
Unverified remote bootstrap execution
The installer downloads the Revdoku executable and marks it executable without verifying a signature or checksum. The documentation also directs users to execute a remotely fetched installer through bash.
The script download and executable permission change are direct, and no integrity verification is present in the cited bootstrap path.
Alto
Bearer token can be sent to a caller-selected origin
The CLI accepts a configurable service URL and sends the saved API key as a Bearer token in requests. An untrusted URL setting can therefore redirect credentials to another origin.
The cited configuration and authenticated request code establish the credential flow. Exploitation depends on an attacker influencing the URL setting or command environment.
Alto
Repository binding can retarget destructive publishing
A project-local .revdoku file supplies a bucket identifier, and publication requests delete missing files. Publishing an untrusted checkout can therefore modify or remove content in a bucket accessible to the user.
The local binding is read without an interactive target confirmation, and the cited publish payload requests deletion of absent files. Exploitation requires valid credentials and a user-initiated publish.
Medio
Existing credentials file permissions are not repaired
Saving an API key sets a restrictive umask but does not explicitly chmod an existing credentials file. A previously permissive file can retain its permissions after being overwritten with a new key.
The cited save routine establishes umask but lacks a permission repair step. The exposure requires an existing file with insecure mode on a shared system.

Factores de riesgo

⚙️ Comandos externos (50)
🌐 Acceso a red (15)
📁 Acceso al sistema de archivos (50)
🔑 Variables de entorno (28)

Patrones detectados

Pipe to shell pattern
Auditado por: claude