hloth/lufin
1
0
Fork 0
Code Issues 9 Pull requests Releases 1 Activity Actions

Hash deleteToken and authorToken in the database #4

New issue
Open
opened 2025-08-25 01:43:11 +02:00 by VityaSchel · 0 comments
VityaSchel commented 2025-08-25 01:43:11 +02:00 (Migrated from github.com)
Copy link

In case of database leak or readonly breach, an attacker could steal delete tokens and erase pages via API. Hashing this value would allow the backend to find matches in the database and attacker would not be able to use API to send delete requests.

In case of database leak or readonly breach, an attacker could steal delete tokens and erase pages via API. Hashing this value would allow the backend to find matches in the database and attacker would not be able to use API to send delete requests.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
v1.0.0
Labels
Clear labels   
bug

Something isn't working

  
documentation

Improvements or additions to documentation

  
duplicate

This issue or pull request already exists

  
enhancement

New feature or request

  
good first issue

Good for newcomers

  
help wanted

Extra attention is needed

  
invalid

This doesn't seem right

  
question

Further information is requested

  
wontfix

This will not be worked on

No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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: hloth/lufin#4
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?