[GH-ISSUE #7067] Cipher::to_json() panics on unknown atype instead of returning an error #15393

New Issue

GiteaMirror · 2026-04-23T07:16:34-05:00

GiteaMirror commented

2026-04-23 07:16:34 -05:00

Originally created by @mango766 on GitHub (Apr 9, 2026).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/7067

Bug Description

Cipher::to_json() in src/db/models/cipher.rs returns Result<Value, Error>, but the match arm for unknown atype values calls panic!("Wrong type") rather than returning a proper Err.

Affected code (around line 395–402):

let key = match self.atype {
    1 => "login",
    2 => "secureNote",
    3 => "card",
    4 => "identity",
    5 => "sshKey",
    _ => panic!("Wrong type"),   // ← panics instead of returning Err
};

Why This Matters

Because the whole function signature is -> Result<Value, crate::Error>, the intent is clearly to propagate failures to callers — but a panic! bypasses that entirely and terminates the Rocket worker thread (or the whole process, depending on the panic hook).

A cipher with an unexpected atype can end up in the database via:

Direct database edits / migrations
Corruption or a future Bitwarden protocol extension that adds a new type before vaultwarden is updated

When a user with such a cipher calls /sync, vaultwarden crashes instead of returning a 500/error response, which also affects all other concurrent users on the same instance.

Expected Behavior

Return an Err (using the existing err! macro already used elsewhere in the same file) so the error is logged and the request fails gracefully without crashing the server.

Suggested Fix

_ => err!(format!("Cipher {} has an invalid type {}", self.uuid, self.atype)),

I have a PR ready with this one-line fix.

Originally created by @mango766 on GitHub (Apr 9, 2026). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/7067 ## Bug Description `Cipher::to_json()` in `src/db/models/cipher.rs` returns `Result<Value, Error>`, but the match arm for unknown `atype` values calls `panic!("Wrong type")` rather than returning a proper `Err`. **Affected code** (around line 395–402): ```rust let key = match self.atype { 1 => "login", 2 => "secureNote", 3 => "card", 4 => "identity", 5 => "sshKey", _ => panic!("Wrong type"), // ← panics instead of returning Err }; ``` ## Why This Matters Because the whole function signature is `-> Result<Value, crate::Error>`, the intent is clearly to propagate failures to callers — but a `panic!` bypasses that entirely and terminates the Rocket worker thread (or the whole process, depending on the panic hook). A cipher with an unexpected `atype` can end up in the database via: - Direct database edits / migrations - Corruption or a future Bitwarden protocol extension that adds a new type before vaultwarden is updated When a user with such a cipher calls `/sync`, vaultwarden crashes instead of returning a 500/error response, which also affects all other concurrent users on the same instance. ## Expected Behavior Return an `Err` (using the existing `err!` macro already used elsewhere in the same file) so the error is logged and the request fails gracefully without crashing the server. ## Suggested Fix ```rust _ => err!(format!("Cipher {} has an invalid type {}", self.uuid, self.atype)), ``` I have a PR ready with this one-line fix.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#15393