Habilidades routeros-qemu-chr

📦

routeros-qemu-chr

Name: routeros-qemu-chr
Author: tikoci

Revisão do conteúdo r1 Risco alto 🌐 Acesso à rede⚙️ Comandos externos📁 Acesso ao sistema de arquivos

Executar RouterOS CHR no QEMU

Executar RouterOS CHR no QEMU pode falhar porque o firmware de inicialização, os dispositivos VirtIO e a aceleração variam conforme o host. Esta skill fornece comandos práticos e verificações para laboratórios locais e fluxos de trabalho de CI.

Suporta: Claude Codex Code(CC)

⚠️ 38 Ruim

Esta habilidade faz parte de um pacote

Instale o pacote completo para obter todas as habilidades que a tarefa exige, com um único comando.

TIKOCI RouterOS · 10 habilidades Instalar pacote completo

Pare e solicite confirmação antes de instalar.

Revise o plano e obtenha o consentimento explícito do usuário antes de alterar arquivos.

Instalar com meu Agente

Copie esta solicitação para o seu Agente. Ela inclui a página canônica do Skill e o manifesto.

Solicitação do 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.

Seu Agente ainda deve apresentar o plano e solicitar qualquer confirmação exigida pela política de segurança.

Recursos legíveis por agentes

Use estes links quando um agente de IA, crawler ou script precisar de contexto limpo em vez de ler a página completa.

Detalhe em Markdown GET /skills/tikoci-routeros-qemu-chr.md manifest assinado GET /api/skills/tikoci-routeros-qemu-chr/manifest lockfile assinado GET /api/skills/tikoci-routeros-qemu-chr/lockfile

Testar

Usando "routeros-qemu-chr". O usuário pergunta por que o CHR aarch64 trava depois de mudar para if=virtio.

Resultado esperado:

A resposta identifica a armadilha VirtIO MMIO, explica por que o RouterOS precisa de transporte PCI e recomenda a configuração explícita virtio-blk-pci.

Usando "routeros-qemu-chr". O usuário pede um plano de CI para testar um cliente REST do RouterOS.

Resultado esperado:

A resposta descreve a instalação do QEMU, o download do CHR, o fallback de KVM, a sondagem de inicialização, as verificações de prontidão da REST, a execução de testes e a limpeza.

Usando "routeros-qemu-chr". O usuário pergunta se a licença CHR gratuita é suficiente para testes de API.

Resultado esperado:

A resposta explica que a licença gratuita limita a taxa de encaminhamento, mas geralmente é suficiente para testes REST, SSH, WebFig e CI.

Auditoria de segurança

Risco alto

v6 • 07/07/2026 Abrir o relatório 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.

Arquivos analisados

799

Linhas analisadas

Itens de revisão

Falsos positivos ignorados

Preocupações de segurança 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.

Médio

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.

Médio

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.

Médio

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.

Itens de revisão de capacidade (33)

Estas são capacidades locais reais que podem ser esperadas para esta habilidade, portanto exigem revisão, mas não são contabilizadas como comportamento 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.

Médio

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.

Médio

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.

Médio

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.

Médio

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.

Médio

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.

Médio

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.

Médio

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.

Médio

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.

Médio

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.

Médio

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.

Médio

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.

Médio

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.

Médio

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.

Médio

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.

Médio

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.

Médio

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.

Médio

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.

Médio

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.

Médio

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.

Baixo

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.

Baixo

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.

Baixo

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.

Baixo

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.

Baixo

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.

Baixo

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.

Baixo

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.

Baixo

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.

Fatores de risco

🌐 Acesso à rede (20)

⚙️ Comandos externos (92)

📁 Acesso ao sistema de arquivos (30)

Padrões detectados

Network reconnaissance

Auditado por: codex Ver histórico de auditoria →

Compartilhar e citar este relatório

Compartilhe o relatório de avaliação versionado, o badge neutro, o cartão incorporável e as citações. A Skillstore apresenta evidências sem decidir se este Skill é seguro.

Abrir o relatório versionado

Copiar link do relatório

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

Badge 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)

Badge 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>

Cartão incorporável

<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>

Citações acadêmicas (APA · BibTeX · CFF)

Citação 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ção 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"

Pontuação do Skillstore

Por que esta pontuação Confiança das evidências: Médio

Arquitetura

Manutenibilidade

Conteúdo

Comunidade

Conformidade com a especificação

O que você pode criar

Configuração de laboratório local do RouterOS

Escolha a imagem CHR, o firmware QEMU e os dispositivos VirtIO corretos para um roteador de teste local repetível.

Testes de integração do RouterOS

Crie um job do GitHub Actions que inicializa o CHR, aguarda a prontidão da REST, executa testes e limpa o QEMU.

Diagnóstico de falha de inicialização

Identifique incompatibilidades de arquitetura, firmware e modelo de dispositivo que causam travamentos silenciosos na inicialização do CHR.

Teste estes prompts

Escolher uma imagem CHR

Ajude-me a escolher uma imagem RouterOS CHR para QEMU no meu host. Meu sistema operacional host é [OS], a CPU é [CPU], e eu preciso de [local testing or CI].

Criar um comando de inicialização do QEMU

Gere um comando QEMU para RouterOS CHR com [architecture], [acceleration], [firmware path] e portas do host para WebFig e SSH.

Depurar um problema de inicialização do CHR

Diagnostique esta falha de inicialização do RouterOS CHR no QEMU. Host: [host details]. Comando: [command]. Sintoma ou log: [symptom].

Projetar um fluxo de trabalho de CI

Projete um fluxo de trabalho do GitHub Actions que baixa o RouterOS CHR, inicializa-o com QEMU, aguarda a prontidão da REST, executa testes e sempre faz a limpeza.

Boas práticas

Execute primeiro os exemplos copiados de QEMU e sudo em ambientes isolados de laboratório ou CI.
Use dispositivos VirtIO PCI explícitos ao inicializar RouterOS CHR em aarch64.
Verifique as imagens RouterOS baixadas e mantenha as portas de gerenciamento vinculadas a interfaces confiáveis.

Evitar

Não use inicialização direta de kernel do QEMU para RouterOS CHR.
Não presuma que /dev/kvm existe ou é gravável sem verificar a arquitetura do host e do convidado.
Não exponha portas de gerenciamento CHR recém-criadas a redes não confiáveis.