Habilidades routeros-qemu-chr

📦

routeros-qemu-chr

Name: routeros-qemu-chr
Author: tikoci

Revisión del contenido r1 Riesgo alto 🌐 Acceso a red⚙️ Comandos externos📁 Acceso al sistema de archivos

Ejecutar RouterOS CHR en QEMU

Ejecutar RouterOS CHR en QEMU puede fallar porque el firmware de arranque, los dispositivos VirtIO y la aceleración varían según el host. Esta skill ofrece comandos y comprobaciones prácticas para laboratorios locales y flujos de trabajo de CI.

Compatible con: Claude Codex Code(CC)

⚠️ 38 Deficiente

Esta habilidad forma parte de un paquete

Instala el paquete completo y obtén en un solo comando todas las habilidades que necesita la tarea.

TIKOCI RouterOS · 10 habilidades Instalar paquete completo

Detente y solicita confirmación antes de instalar.

Revisa el plan y obtén el consentimiento explícito del usuario antes de modificar archivos.

Instalar con mi Agente

Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.

Solicitud de agente

Review the Skillstore skill "routeros-qemu-chr" from https://skillstore.io/skills/tikoci-routeros-qemu-chr.md and its manifest at https://skillstore.io/api/skills/tikoci-routeros-qemu-chr/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.

Recursos legibles por agentes

Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.

Detalle Markdown GET /skills/tikoci-routeros-qemu-chr.md Manifest firmado GET /api/skills/tikoci-routeros-qemu-chr/manifest Lockfile firmado GET /api/skills/tikoci-routeros-qemu-chr/lockfile

Pruébalo

Usando "routeros-qemu-chr". El usuario pregunta por qué CHR aarch64 se bloquea tras cambiar a if=virtio.

Resultado esperado:

La respuesta identifica la trampa de VirtIO MMIO, explica por qué RouterOS necesita transporte PCI y recomienda una configuración explícita de virtio-blk-pci.

Usando "routeros-qemu-chr". El usuario pide un plan de CI para probar un cliente REST de RouterOS.

Resultado esperado:

La respuesta describe la instalación de QEMU, la descarga de CHR, la alternativa a KVM, el sondeo de arranque, las comprobaciones de disponibilidad de REST, la ejecución de pruebas y la limpieza.

Usando "routeros-qemu-chr". El usuario pregunta si la licencia gratuita de CHR es suficiente para pruebas de API.

Resultado esperado:

La respuesta explica que la licencia gratuita limita el throughput de reenvío, pero suele ser suficiente para pruebas de REST, SSH, WebFig y CI.

Auditoría de seguridad

Riesgo alto

v6 • 7/7/2026 Abrir el informe versionado

No prompt injection, hidden exfiltration, or malicious intent was found. The skill is legitimate RouterOS CHR and QEMU guidance, but it includes privileged host changes, external downloads, VM process launch, local service exposure, and predictable temp paths. These risks should be documented and gated by user confirmation before execution.

Archivos escaneados

799

Líneas analizadas

Elementos de revisión

Falsos positivos ignorados

Preocupaciones de seguridad confirmadas (4)

Alto

references/github-actions-ci.md:46

World-Writable KVM Device Permission

The CI pattern writes a udev rule that sets the KVM device mode to 0666. This broadens virtualization access to every local user on shared or self-hosted runners.

The exact rule sets MODE="0666" for the KVM device. The impact is clear in shared runner or multi-user host contexts.

Medio

references/github-actions-ci.md:162

Network reconnaissance

sshpass -p '' scp -P 9122 -o StrictHostKeyChecking=no "$pkg" admin@127.0.0.1:/

The package upload uses sshpass with an empty admin password and disables host key checking against localhost. This is acceptable only for disposable local CHR instances.

Medio

references/chr-licensing.md:70 references/github-actions-ci.md:162-166

Default Empty RouterOS Administrator Credentials

Several examples use the default admin account with an empty password over SSH or HTTP. This is suitable only for disposable local CHR instances.

The examples show admin: or sshpass with an empty password. The context is local CI, but copying the pattern to persistent labs would be unsafe.

Medio

references/github-actions-ci.md:204-205

Destructive Git Cleanup Commands in CI Example

The retry pattern resets tracked files and removes untracked files before rebasing. This can delete local work if reused outside a disposable CI worktree.

The commands are explicitly present in the CI retry pattern. The documented context is CI, but the destructive behavior is real if copied elsewhere.

Elementos de revisión de capacidades (33)

Estas son capacidades locales reales que pueden esperarse para esta habilidad, por lo que requieren revisión, pero no se cuentan como comportamiento malicioso confirmado.

Alto

references/github-actions-ci.md:34

sudo privilege escalation

sudo apt-get update

The CI example runs apt with sudo, which modifies the host runner package state. This is legitimate setup work but requires elevated privileges.

Alto

references/github-actions-ci.md:35

sudo privilege escalation

sudo apt-get install -y qemu-system-x86 qemu-utils

The CI example runs apt with sudo, which modifies the host runner package state. This is legitimate setup work but requires elevated privileges.

Alto

references/github-actions-ci.md:46

sudo privilege escalation

echo 'KERNEL=="kvm", GROUP="kvm", MODE="0666", OPTIONS+="static_node=kvm"' | sudo tee /etc/udev/rule

The CI example uses sudo to alter udev/KVM handling on the host. This broadens virtualization device access and is security-sensitive.

Alto

references/github-actions-ci.md:47

sudo privilege escalation

sudo udevadm control --reload-rules

The CI example uses sudo to alter udev/KVM handling on the host. This broadens virtualization device access and is security-sensitive.

Alto

references/github-actions-ci.md:48

sudo privilege escalation

sudo udevadm trigger --name-match=kvm

The CI example uses sudo to alter udev/KVM handling on the host. This broadens virtualization device access and is security-sensitive.

Alto

SKILL.md:97

Process spawn

const proc = Bun.spawn([

The skill shows Bun.spawn launching qemu-system-x86_64 with VM devices and forwarded ports. This is intended functionality, but it executes a host binary and starts a VM process.

Medio

references/chr-licensing.md:70

Hardcoded URL

curl -u admin: http://<router-ip>/rest/system/license

The example uses cleartext HTTP Basic auth to query a RouterOS license endpoint. This can expose credentials if copied outside a trusted local lab.

Medio

references/github-actions-ci.md:224

Shell command substitution

kill $(cat /tmp/qemu.pid) 2>/dev/null || true

The cleanup command reads a PID from a predictable temp file and passes it to kill. A tampered PID file could terminate an unintended process on less isolated hosts.

Medio

references/github-actions-ci.md:103

nohup (background persistent process)

nohup qemu-system-x86_64 \

The workflow backgrounds QEMU with nohup, creating a long-lived VM process. If cleanup fails, the process can persist and keep forwarded ports open.

Medio

references/github-actions-ci.md:166

Hardcoded URL

curl -sf -u admin: -X POST http://127.0.0.1:9180/rest/system/reboot || true

The workflow sends an authenticated reboot request using the default admin account with no password. This is safe only when the forwarded REST service is local and ephemeral.

Medio

references/github-actions-ci.md:162

Hardcoded IP address

sshpass -p '' scp -P 9122 -o StrictHostKeyChecking=no "$pkg" admin@127.0.0.1:/

The package upload uses sshpass with an empty admin password and disables host key checking against localhost. This is acceptable only for disposable local CHR instances.

Medio

references/github-actions-ci.md:166

Hardcoded IP address

curl -sf -u admin: -X POST http://127.0.0.1:9180/rest/system/reboot || true

The workflow sends an authenticated reboot request using the default admin account with no password. This is safe only when the forwarded REST service is local and ephemeral.

Medio

references/github-actions-ci.md:110

Temp directory access

> /tmp/qemu.log 2>&1 &

The workflow stores QEMU logs and PID data in predictable /tmp paths. On shared hosts, predictable temp paths can enable clobbering or process-control mistakes.

Medio

references/github-actions-ci.md:111

Temp directory access

echo $! > /tmp/qemu.pid

The workflow stores QEMU logs and PID data in predictable /tmp paths. On shared hosts, predictable temp paths can enable clobbering or process-control mistakes.

Medio

references/github-actions-ci.md:223

Temp directory access

if [ -f /tmp/qemu.pid ]; then

The workflow stores QEMU logs and PID data in predictable /tmp paths. On shared hosts, predictable temp paths can enable clobbering or process-control mistakes.

Medio

references/github-actions-ci.md:224

Temp directory access

kill $(cat /tmp/qemu.pid) 2>/dev/null || true

The workflow stores QEMU logs and PID data in predictable /tmp paths. On shared hosts, predictable temp paths can enable clobbering or process-control mistakes.

Medio

references/known-issues.md:55

nohup (background persistent process)

When backgrounding QEMU (e.g., `nohup qemu-system-x86_64 ... &`), use `exec` in the shell wrapper to

The reference discusses backgrounding QEMU with nohup. The surrounding text explains safe PID handling, but the pattern can still leave orphaned VMs if copied incorrectly.

Medio

references/known-issues.md:59

nohup (background persistent process)

nohup sh -c "qemu-system-x86_64 ..." &

The reference discusses backgrounding QEMU with nohup. The surrounding text explains safe PID handling, but the pattern can still leave orphaned VMs if copied incorrectly.

Medio

references/known-issues.md:62

nohup (background persistent process)

nohup sh -c "exec qemu-system-x86_64 ..." &

The reference discusses backgrounding QEMU with nohup. The surrounding text explains safe PID handling, but the pattern can still leave orphaned VMs if copied incorrectly.

Medio

references/known-issues.md:72

Temp directory access

socat -,rawer UNIX-CONNECT:/tmp/serial.sock,retry=10,interval=1

The example uses predictable /tmp paths for sockets or firmware variable files. This is operationally useful but can collide across users or VM instances.

Medio

references/known-issues.md:81

Temp directory access

VARS_COPY="/tmp/qemu-${VM_NAME}-vars.fd"

The example uses predictable /tmp paths for sockets or firmware variable files. This is operationally useful but can collide across users or VM instances.

Medio

SKILL.md:104

Temp directory access

"-chardev", `socket,id=serial0,path=/tmp/chr-serial.sock,server=on,wait=off`,

The programmatic QEMU example creates monitor or serial sockets under predictable /tmp paths. Shared hosts should use private per-instance directories and permissions.

Medio

SKILL.md:106

Temp directory access

"-monitor", `unix:/tmp/chr-monitor.sock,server,nowait`,

The programmatic QEMU example creates monitor or serial sockets under predictable /tmp paths. Shared hosts should use private per-instance directories and permissions.

Medio

SKILL.md:146

Temp directory access

cp /path/to/edk2-arm-vars.fd /tmp/my-vars.fd

The UEFI example copies writable firmware variables into /tmp. Predictable firmware-variable paths can collide or be clobbered on shared systems.

Medio

SKILL.md:150

Temp directory access

-drive if=pflash,format=raw,unit=1,file=/tmp/my-vars.fd \

The UEFI example copies writable firmware variables into /tmp. Predictable firmware-variable paths can collide or be clobbered on shared systems.

Bajo

references/github-actions-ci.md:71

Hardcoded URL

wget -q "https://download.mikrotik.com/routeros/${ROSVER}/chr-${ROSVER}.vdi.zip" \

The workflow downloads VM images or package bundles from external MikroTik endpoints. The domains are expected, but this remains a remote supply-chain dependency.

Bajo

references/github-actions-ci.md:72

Hardcoded URL

|| wget -q "https://cdn.mikrotik.com/routeros/${ROSVER}/chr-${ROSVER}.vdi.zip"

The workflow downloads VM images or package bundles from external MikroTik endpoints. The domains are expected, but this remains a remote supply-chain dependency.

Bajo

references/github-actions-ci.md:156

Hardcoded URL

wget -q "https://download.mikrotik.com/routeros/${ROSVER}/all_packages-x86-${ROSVER}.zip" \

The workflow downloads VM images or package bundles from external MikroTik endpoints. The domains are expected, but this remains a remote supply-chain dependency.

Bajo

references/github-actions-ci.md:157

Hardcoded URL

|| wget -q "https://cdn.mikrotik.com/routeros/${ROSVER}/all_packages-x86-${ROSVER}.zip"

The workflow downloads VM images or package bundles from external MikroTik endpoints. The domains are expected, but this remains a remote supply-chain dependency.

Bajo

SKILL.md:31

Fetch API call

const version = await fetch(

The download guidance contacts MikroTik services to resolve or fetch CHR images. The endpoints are expected, but the skill depends on external network content.

Bajo

SKILL.md:32

Hardcoded URL

`https://upgrade.mikrotik.com/routeros/NEWESTa7.${channel}`

The download guidance contacts MikroTik services to resolve or fetch CHR images. The endpoints are expected, but the skill depends on external network content.

Bajo

SKILL.md:36

Hardcoded URL

const url = `https://download.mikrotik.com/routeros/${version}/chr-${version}.img.zip`;

The download guidance contacts MikroTik services to resolve or fetch CHR images. The endpoints are expected, but the skill depends on external network content.

Bajo

SKILL.md:38

Hardcoded URL

const armUrl = `https://download.mikrotik.com/routeros/${version}/chr-${version}-arm64.img.zip`;

The download guidance contacts MikroTik services to resolve or fetch CHR images. The endpoints are expected, but the skill depends on external network content.

Factores de riesgo

🌐 Acceso a red (20)

⚙️ Comandos externos (92)

📁 Acceso al sistema de archivos (30)

Patrones detectados

Network reconnaissance

Auditado por: codex Ver historial de auditorías →

Compartir y citar este informe

Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.

Abrir el informe versionado

Copiar enlace del informe

https://skillstore.io/skills/tikoci-routeros-qemu-chr/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Insignia Markdown

[![Skillstore security assessment](https://skillstore.io/badges/skills/tikoci-routeros-qemu-chr/security.svg)](https://skillstore.io/skills/tikoci-routeros-qemu-chr?utm_source=security_passport_badge)

Insignia HTML

<a href="https://skillstore.io/skills/tikoci-routeros-qemu-chr?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/tikoci-routeros-qemu-chr/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Tarjeta para insertar

<iframe src="https://skillstore.io/embed/skills/tikoci-routeros-qemu-chr.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Citas académicas (APA · BibTeX · CFF)

Cita APA

tikoci. (2026). routeros-qemu-chr security audit report (audit version 6) [Author version unspecified]. Skillstore. https://skillstore.io/skills/tikoci-routeros-qemu-chr/audits/6

Cita BibTeX

@techreport{tikoci-tikoci-routeros-qemu-chr-2026,
  author = {tikoci},
  title = {routeros-qemu-chr security audit report (audit version 6)},
  institution = {Skillstore},
  year = {2026},
  number = {6},
  url = {https://skillstore.io/skills/tikoci-routeros-qemu-chr/audits/6},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "routeros-qemu-chr security audit report (audit version 6)"
version: "unspecified"
type: report
authors:
  - name: "tikoci"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/tikoci-routeros-qemu-chr/audits/6"
identifiers:
  - type: other
    value: "skillstore:tikoci-routeros-qemu-chr:audit:6"
    description: "Skillstore immutable audit report identifier"

Puntuación de Skillstore

Por qué esta puntuación Confianza de la evidencia: Medio

Arquitectura

Mantenibilidad

Contenido

Comunidad

Cumplimiento de la especificación

Lo que puedes crear

Configuración de un laboratorio local de RouterOS

Elige la imagen CHR, el firmware de QEMU y los dispositivos VirtIO correctos para un router de prueba local repetible.

Pruebas de integración de RouterOS

Crea un trabajo de GitHub Actions que arranque CHR, espere a que REST esté listo, ejecute pruebas y limpie QEMU.

Diagnóstico de fallos de arranque

Identifica desajustes de arquitectura, firmware y modelo de dispositivo que provocan bloqueos silenciosos en el arranque de CHR.

Prueba estos prompts

Elegir una imagen CHR

Ayúdame a elegir una imagen de RouterOS CHR para QEMU en mi host. Mi sistema operativo host es [OS], la CPU es [CPU] y necesito [local testing or CI].

Crear un comando de lanzamiento de QEMU

Genera un comando de QEMU para RouterOS CHR con [architecture], [acceleration], [firmware path] y puertos del host para WebFig y SSH.

Depurar un problema de arranque de CHR

Diagnostica este fallo de arranque de RouterOS CHR en QEMU. Host: [host details]. Comando: [command]. Síntoma o log: [symptom].

Diseñar un flujo de trabajo de CI

Diseña un flujo de trabajo de GitHub Actions que descargue RouterOS CHR, lo arranque con QEMU, espere a que REST esté listo, ejecute pruebas y siempre haga limpieza.

Mejores prácticas

Ejecuta primero los ejemplos copiados de QEMU y sudo en entornos aislados de laboratorio o CI.
Usa dispositivos VirtIO PCI explícitos al arrancar RouterOS CHR aarch64.
Verifica las imágenes de RouterOS descargadas y mantén los puertos de administración vinculados a interfaces de confianza.

Evitar

No uses arranque directo del kernel de QEMU para RouterOS CHR.
No asumas que /dev/kvm existe o tiene permisos de escritura sin comprobar la arquitectura del host y del guest.
No expongas puertos de administración de CHR recién creados a redes no confiables.