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.
argv budget with a leading zero (08/09) bypasses the validation guard via an octal arithmetic error
Low-severity issue, currently open.
Description
The issue as recorded.
The argv budget guard (bin/omarchy-system-sleep-lock:45) matches ^[0-9]+$ then evaluates (( budget_ms < 1 )) in bash arithmetic, which reads a leading zero as octal. '08'/'09' raise 'value too great for base', the guard compound goes false, and the script keeps the literal token as its budget. The deadline assignment at line 52 errors the same way, and every lock_ipc fails its remaining guard. The run ends in report_unsecured claiming 'within 08ms' with no lock request issued. '010' is silently accepted as octal 8.
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.
./pocs/crs-260930-gzq0-c03.sh
Reproduction steps
Technical steps for your engineers to confirm the issue by hand.
./pocs/crs-260930-gzq0-c03.sh
What protects you, and the fix
What limits your exposure today, and the planned remediation.
What protects you now
Leading-zero budgets only arrive from hand-typed commands; keybinds and scripts pass plain decimal or no argument
The fix
Force decimal (10#) in the guard and deadline arithmetic, or reject any budget token bash cannot evaluate in base 10 with a usage error
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 1 requirements · 1 code files · 1 tests.
- omarchy-system-sleep-lock
- sleep-lock-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.
- proof/evidence/ki-sleep-lock-budget-arg-octal.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.