You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello.
I have noticed some behavior that I believe is potentially unsafe.
When I open a private memo that has an attachment, I am able to open the attachment in a separate browser window or tab.
The link to the attachment appears to be: https://domain.memos.com/file/resources/abcdef/doc.pdf.
My concern is that anyone with access to this link could potentially view or download the attached file without authorization. Is this intended behavior, or is it a bug?
Thank you for your attention to this matter.
Steps to reproduce
Open a private memo with attachment
Copy a link to attachment
Open it on any other device
The version of Memos you're using
v0.24.2
Screenshots or additional context
No response
The text was updated successfully, but these errors were encountered:
I performed the same steps and when I tried to access the resource in a private window or from my terminal I got: {"code":16, "message":"unauthorized access", "details":[]}
I wasn't able to reproduce this either. One possible cause I can think of is that you might have Nginx or something else that's serving the file directly, bypassing the Memos permission check? @v-sulimov
Describe the bug
Hello.
I have noticed some behavior that I believe is potentially unsafe.
When I open a private memo that has an attachment, I am able to open the attachment in a separate browser window or tab.
The link to the attachment appears to be: https://domain.memos.com/file/resources/abcdef/doc.pdf.
My concern is that anyone with access to this link could potentially view or download the attached file without authorization. Is this intended behavior, or is it a bug?
Thank you for your attention to this matter.
Steps to reproduce
The version of Memos you're using
v0.24.2
Screenshots or additional context
No response
The text was updated successfully, but these errors were encountered: