Proof Portal
Omarchy
ProbeLabsviewing a historical runA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Guard ids interpolated unquoted into the shared bash batch: metacharacter ids break the protocol or execute commands
Low-severity issue, currently open.
Description
The issue as recorded.
guardLine splices the id unquoted: guardScript({'my;id': {when:'true'}}) emits 'echo my;id:w:1' - a second command and a broken record format (F16a2). The result parser then attributes answers to the wrong ids. Because all guards share ONE script, a single unbalanced expression makes the entire batch fail bash -n. Every row then silently keeps its last answers (F16b2). A boolean when/checked/disabled (normalizeItem preserves it) throws inside generation and aborts the script build entirely (F16c2).
Affected requirements
The requirement(s) this issue violates — click through to the spec.
Severity, explained
Why this is rated the way it is — and the scoring signals behind the rating (each ⓘ explains the term).
- why this rating
- Risk-rated
- risk area
- Correctness
- CVE surface
- None
How it's proven
The reproducer — an actual test that drives the real code and shows the issue happening. Run it yourself, or peek the test and the source it covers.
known_issue_reproducernode pocs/menu-probes3.js ../shell/plugins/menu/MenuModel.js
Reproduction steps
Technical steps for your engineers to confirm the issue by hand.
node pocs/menu-probes3.js ../shell/plugins/menu/MenuModel.js
What protects you, and the fix
What limits your exposure today, and the planned remediation.
What protects you now
Ids come from the user's own menu JSONC, so the injection harms only the user's own config. A broken batch leaves guards stale until the next rebuild
The fix
single-quote the id into the echo (or base64 it) and sanitize/validate expressions at parse time; fail one guard without failing the batch
Blast radius
If you touch this issue, what else may need re-checking — the requirements it affects and the code and tests that hang off them. Historical view: authored trace links only — automatically derived links aren't reconstructible for past runs.
Touch this finding and you re-check 2 requirements · 1 code files · 1 tests.
- MenuModel.js
- menu-guards-test.sh
Per-requirement evidence
For each requirement this finding touches: the implementing code, verifying tests, and proof obligations that discharge it.
Per-requirement evidence
For each requirement this finding touches: the implementing code, verifying tests, and proof obligations that discharge it.
Evidence trail
The raw evidence manifests behind this finding — superseded by the resolved reproducer above, kept here for traceability.
Evidence trail
The raw evidence manifests behind this finding — superseded by the resolved reproducer above, kept here for traceability.
- pocs/menu-probes.js
- pocs/menu-probes2.js
- pocs/menu-probes3.js
- proof/evidence/ki-menu-guard-id-injection-batch-abort.yaml
Change history
Every recorded revision of this finding's source file — when it was added, edited, or re-classified, with the diff for each change.
Discussions
Discuss this with the proof team. Nothing changes in your audit automatically — you open a request and a staff member records any outcome inside the thread.