📦

Audit History

routeros-qemu-chr - 3 audits

Audit version 3

Latest Medium Risk

May 9, 2026, 03:51 PM

Static analysis detected 347 potential security patterns across 5 files. After semantic evaluation, all findings are FALSE POSITIVES. The skill uses external commands for QEMU invocation, which is the core purpose of this documentation. Network access is limited to mikrotik.com download URLs. No malicious intent or actual security vulnerabilities confirmed.

5
Files scanned
799
Lines analyzed
9
findings
claude
Audited by
Medium Risk Issues (2)
External Command Invocation in Documentation
Skill contains numerous shell commands and script examples for QEMU invocation. These are intentional documentation patterns, not security vulnerabilities. Commands are hardcoded with fixed arguments (qemu-system-x86_64, specific flags) and not subject to user input injection.
System Device Access for Virtualization
Documentation references /dev/kvm access for KVM acceleration detection. This is standard practice for QEMU virtual machine management on Linux.
Low Risk Issues (4)
Historical Cryptographic Reference (MD5)
MD5 is mentioned in virtio-drivers.md in the context of a kernel config option (CONFIG_BLK_DEV_NVME is unrelated to MD5). The chr-licensing.md references are in documentation explaining license expiry behavior, not for security purposes.
Hardcoded Network URLs
MikroTik download URLs (download.mikrotik.com, cdn.mikrotik.com) are hardcoded for CHR image downloads. These are official MikroTik infrastructure URLs.
System Reconnaissance for Acceleration Detection
The skill checks for KVM availability (/dev/kvm) and HVF support (sysctl kern.hv_support) to determine appropriate QEMU acceleration.
Sudo Usage in CI Workflows
GitHub Actions CI documentation uses sudo for apt-get installation and udev configuration. This is standard CI practice.

Audit version 2

Low Risk

Apr 16, 2026, 09:11 PM

Documentation and reference skill for running RouterOS CHR in QEMU. Static analysis flagged 343 patterns, but evaluation reveals these are false positives: shell backtick notation in markdown code examples (not execution), sudo in GitHub Actions CI (expected), MD5 references in kernel history docs (not actual usage), and legitimate acceleration detection commands. All network access targets MikroTik infrastructure for downloading CHR images. Risk level set to LOW due to external command patterns in documentation examples, but no actual malicious code present.

5
Files scanned
794
Lines analyzed
12
findings
claude
Audited by

High Risk Issues (4)

Documentation Shell Examples Misidentified as Execution
Static scanner flagged 264 instances of Ruby/shell backtick notation. These are markdown code blocks showing shell command syntax, not actual command execution. Files are documentation with command examples.
sudo Commands in GitHub Actions CI (Expected Behavior)
GitHub Actions workflow uses sudo for package installation (apt-get install). This is standard CI/CD practice, not privilege escalation risk.
nohup for Background QEMU Process (Legitimate Use)
nohup is used to run QEMU in background during CI testing. This is standard practice for running VMs in CI environments.
Base64 HTTP Basic Auth (Standard Practice)
Static scanner flagged btoa('admin:') as weak crypto. This is standard HTTP Basic Auth encoding, not cryptographic weakness.
Medium Risk Issues (3)
Network Access to External URLs
Skill downloads CHR images from MikroTik infrastructure. URLs point to download.mikrotik.com and cdn.mikrotik.com for official RouterOS images.
Device File Access for Virtualization
/dev/kvm access for KVM acceleration detection. This is standard practice for virtualization tooling.
Temp Directory Access
/tmp used for QEMU vars files, serial sockets, and log files. Standard temp file usage for VM management.
Low Risk Issues (2)
Hardcoded IP Addresses (Localhost)
127.0.0.1 used for RouterOS REST API and port forwarding. Standard localhost addressing.
System Information Commands (Acceleration Detection)
uname, sysctl, and stat commands used for platform detection. Standard virtualization tooling practice.

Audit version 1

Safe

Mar 30, 2026, 02:11 AM

Static analysis detected 303 potential security issues in code examples and documentation. All findings are false positives: external commands are legitimate QEMU invocations for virtualization, network operations access official MikroTik servers, and filesystem operations are standard QEMU configuration patterns. No malicious intent detected.

4
Files scanned
668
Lines analyzed
3
findings
claude
Audited by
No security issues found