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
It's a single bug. Do not report multiple bugs in one issue.
It's a frontend issue, not a backend issue; Otherwise please create an issue on the backend repo instead.
Summary
On v0.18 versions when Lemmy hits an error, it gives an error screen. Unfortunately, this error also gives out the users access token.
This is a major vulnerability, since the page almost encourages sharing the error page. This is a severe vulnerability because of: LemmyNet/lemmy#3364
Steps to Reproduce
Get a error (for example, one I got was" FetchError: request to http://lemmy:8536/api/v3/community?name=wisconsin&auth= failed, reason: connect ECONNREFUSED 172.18.0.5:8536."
The auth= part contains my token, edited out for security.
Accidentally share the error message and expose my account token
Technical Details
Independent of web browser/OS. Depends on when you get an error page.
Lemmy Instance Version
v0.18
Lemmy Instance URL
No response
The text was updated successfully, but these errors were encountered:
Thanks @JackFromWisconsin. Where does this error appear? In a popup box in the lower-left? Can you include a screenshot, and/or steps to take to reproduce an error like this?
Requirements
Summary
On v0.18 versions when Lemmy hits an error, it gives an error screen. Unfortunately, this error also gives out the users access token.
This is a major vulnerability, since the page almost encourages sharing the error page. This is a severe vulnerability because of: LemmyNet/lemmy#3364
Steps to Reproduce
Technical Details
Independent of web browser/OS. Depends on when you get an error page.
Lemmy Instance Version
v0.18
Lemmy Instance URL
No response
The text was updated successfully, but these errors were encountered: