GRI-2178: accept RUSTSEC-2026-0543 (chrono unmaintained) #308

Merged
vivy merged 1 commit from security/GRI-2178-chrono-unmaintained-advisory into dev 2026-11-17 13:16:19 +00:00
Member

Forge issue #305,
board GRI-2178.

Security judgement

RUSTSEC-2026-0543 (chrono is unmaintained), issued 2026-11-17, is INFO
category with no CVE and no exploit
— verified directly against the
advisory text. cargo-deny's own advisory data lists no patched version;
the advisory's own recommendation is a crate replacement (jiff or time),
not a version bump. That is "no safe upgrade is available" in the literal
sense cargo deny's own error reports, not a convenience judgement.

Under the product owner's rule on unmaintained advisories
(plan/decisions/0013-advisories-block-the-merge.md, GRI-2051): "unmaintained
is ignored only with no other option... fixed is preferred over ignored, but
one or the other is required."
No fix exists today, so the accept path is
the only option that unblocks dev and every open PR without a real crate
migration done under time pressure.

Residual risk, stated so it isn't lost in the config diff: chrono sits
on the auth path, not just display — crates/server/src/auth/handlers.rs
computes session expires_at with it. There is no known defect today, but
an unmaintained crate gets no fix if one is found later. That is the reason
this is dated and tracked, not a bare ignore.

Removal condition: forge issue
#307,
closed by a chrono -> jiff/time migration across client/server/shared
(and whatever drops the transitive pull through sqlx-core). -D advisory-not-detected already re-reds the gate the day either that migration
lands or a maintained chrono fork clears the advisory, so the entry cannot go
stale unnoticed.

Verified independently, not just from the reporter's evidence

  • Confirmed cargo deny advisories failing on PR #303 @ c8230e3, CI run 570
    job 6, failure at 12:30:15Z today — matches the reported timeline.
  • Fetched the advisory text directly from rustsec.org: INFO/Unmaintained, no
    CVE, no patched version, reference is a GitHub maintenance-status issue.
  • cargo deny check advisories -D advisory-not-detected passes clean on this
    branch.
  • ./scripts/local-gates.sh --rust-only passes clean (fmt, clippy, deny,
    bans, licenses, sources, cargo test) — exit 0.

Test plan

  • cargo deny check advisories -D advisory-not-detected — passes
  • scripts/local-gates.sh --rust-only — every gate passes
  • CI on this PR, including cargo deny advisories, green
Forge issue [#305](https://git.grimoirix.org/Grimoirix/grimoire-of-digital-signage/issues/305), board GRI-2178. ## Security judgement `RUSTSEC-2026-0543` (chrono is unmaintained), issued 2026-11-17, is **INFO category with no CVE and no exploit** — verified directly against the advisory text. `cargo-deny`'s own advisory data lists no patched version; the advisory's own recommendation is a crate replacement (`jiff` or `time`), not a version bump. That is "no safe upgrade is available" in the literal sense `cargo deny`'s own error reports, not a convenience judgement. Under the product owner's rule on unmaintained advisories (`plan/decisions/0013-advisories-block-the-merge.md`, GRI-2051): *"unmaintained is ignored only with no other option... fixed is preferred over ignored, but one or the other is required."* No fix exists today, so the accept path is the only option that unblocks `dev` and every open PR without a real crate migration done under time pressure. **Residual risk**, stated so it isn't lost in the config diff: `chrono` sits on the auth path, not just display — `crates/server/src/auth/handlers.rs` computes session `expires_at` with it. There is no known defect today, but an unmaintained crate gets no fix if one is found later. That is the reason this is dated and tracked, not a bare ignore. **Removal condition**: forge issue [#307](https://git.grimoirix.org/Grimoirix/grimoire-of-digital-signage/issues/307), closed by a `chrono` -> `jiff`/`time` migration across `client`/`server`/`shared` (and whatever drops the transitive pull through `sqlx-core`). `-D advisory-not-detected` already re-reds the gate the day either that migration lands or a maintained chrono fork clears the advisory, so the entry cannot go stale unnoticed. ## Verified independently, not just from the reporter's evidence - Confirmed `cargo deny advisories` failing on PR #303 @ `c8230e3`, CI run 570 job 6, `failure` at 12:30:15Z today — matches the reported timeline. - Fetched the advisory text directly from rustsec.org: INFO/Unmaintained, no CVE, no patched version, reference is a GitHub maintenance-status issue. - `cargo deny check advisories -D advisory-not-detected` passes clean on this branch. - `./scripts/local-gates.sh --rust-only` passes clean (fmt, clippy, deny, bans, licenses, sources, cargo test) — exit 0. ## Test plan - [x] `cargo deny check advisories -D advisory-not-detected` — passes - [x] `scripts/local-gates.sh --rust-only` — every gate passes - [ ] CI on this PR, including `cargo deny advisories`, green
GRI-2178: accept RUSTSEC-2026-0543 (chrono unmaintained), no safe upgrade
All checks were successful
CI / the pre-push hook (pull_request) Successful in 7s
CI / cargo fmt (pull_request) Successful in 5s
CI / install.sh client upgrade (pull_request) Successful in 17s
CI / cargo deny advisories (pull_request) Successful in 1m27s
CI / cargo clippy (pull_request) Successful in 2m13s
CI / cargo deny (pull_request) Successful in 1m28s
CI / repository boundary (pull_request) Successful in 5s
CI / frontend-web (pull_request) Successful in 1m33s
CI / cargo test (pull_request) Successful in 6m39s
CI / CI (pull_request) Successful in 1s
CI / Notify gate failed (pull_request) Has been skipped
3346fc1ee6
vivy merged commit 7f09d753f0 into dev 2026-11-17 13:16:19 +00:00
vivy deleted branch security/GRI-2178-chrono-unmaintained-advisory 2026-11-17 13:16:20 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Grimoirix/grimoire-of-digital-signage!308
No description provided.