[GH-ISSUE #1022] Cloning entry with attachment fails, "Attachment is not owned by the cipher" #718

Closed
opened 2026-03-03 02:02:32 +03:00 by kerem · 1 comment
Owner

Originally created by @jcklie on GitHub (Jun 5, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1022

Cloning entry with attachment fails

When I clone an entry with attachment, then I get the error message "Attachment is not owned by the cipher".

Your environment

  • Bitwarden_rs version: Master self compiled db53511855
  • Install method: built from source
  • Clients used: vault
  • Reverse proxy and version: Nginx (by shauder)
  • Version of mysql/postgresql: sqlite
  • Other relevant information: Self signed certs, everything else works

Steps to reproduce

Websockets enabled ,smtp works

  1. In an organization, create a new item
  2. Attach an image
  3. Try to clone it
  4. See error

Expected behaviour

No error, thing gets cloned

Actual behaviour

Error toast "Attachment is not owned by the cipher", bitwarden_rs returns 400, empty entry is created

Relevant logs

Bitwarden log:

Jun 05 17:24:48 timetracking bitwarden_rs[22080]: [2020-06-05 17:24:48][request][INFO] POST /api/ciphers/admin
Jun 05 17:24:49 timetracking bitwarden_rs[22080]: [2020-06-05 17:24:49][error][ERROR] Attachment is not owned by the cipher
Jun 05 17:24:49 timetracking bitwarden_rs[22080]: [2020-06-05 17:24:49][response][INFO] POST /api/ciphers/admin (post_ciphers_admin) => 400 Bad Request

JS console:
Failed to load resource: the server responded with a status of 400 ()
image

Originally created by @jcklie on GitHub (Jun 5, 2020). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1022 <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unneccessary for your issue, feel free to remove them. Remember to hide/obfuscate personal and confidential information, such as names, global IP/DNS adresses and especially passwords, if neccessary. --> ### Cloning entry with attachment fails When I clone an entry with attachment, then I get the error message "Attachment is not owned by the cipher". ### Your environment <!-- The version number, obtained from the logs or the admin page --> * Bitwarden_rs version: Master self compiled db53511855146330fe251334dd769678074b31ff <!-- How the server was installed: Docker image / package / built from source --> * Install method: built from source * Clients used: vault * Reverse proxy and version: Nginx (by shauder) <!-- if applicable --> * Version of mysql/postgresql: sqlite<!-- if applicable --> * Other relevant information: Self signed certs, everything else works ### Steps to reproduce <!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults) and how did you start bitwarden_rs? --> Websockets enabled ,smtp works 1. In an organization, create a new item 2. Attach an image 3. Try to clone it 4. See error ### Expected behaviour No error, thing gets cloned ### Actual behaviour Error toast "Attachment is not owned by the cipher", bitwarden_rs returns 400, empty entry is created ### Relevant logs <!-- Share some logfiles, screenshots or output of relevant programs with us. --> Bitwarden log: ``` Jun 05 17:24:48 timetracking bitwarden_rs[22080]: [2020-06-05 17:24:48][request][INFO] POST /api/ciphers/admin Jun 05 17:24:49 timetracking bitwarden_rs[22080]: [2020-06-05 17:24:49][error][ERROR] Attachment is not owned by the cipher Jun 05 17:24:49 timetracking bitwarden_rs[22080]: [2020-06-05 17:24:49][response][INFO] POST /api/ciphers/admin (post_ciphers_admin) => 400 Bad Request ``` JS console: `Failed to load resource: the server responded with a status of 400 () ` ![image](https://user-images.githubusercontent.com/934600/83894467-a1fb1e00-a751-11ea-9c13-b8e556577b26.png)
kerem closed this issue 2026-03-03 02:02:32 +03:00
Author
Owner

@BlackDex commented on GitHub (Jun 6, 2020):

i can confirm the error.
And, if i check the upstream project it doesn't clone attachments at all.
So i think we should match that for now, but this bug causes those items to not being cloned at all.

<!-- gh-comment-id:640074748 --> @BlackDex commented on GitHub (Jun 6, 2020): i can confirm the error. And, if i check the upstream project it doesn't clone attachments at all. So i think we should match that for now, but this bug causes those items to not being cloned at all.
Sign in to join this conversation.
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
starred/vaultwarden#718
No description provided.