-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changing state of notifications via API results in internal server error 500 #25545
Labels
Comments
Maybe we should return gitea/routers/api/v1/notify/user.go Lines 132 to 137 in b943318
|
silverwind
pushed a commit
that referenced
this issue
Jun 28, 2023
Backport #25548 by @Zettat123 This PR - fixes #25545 - fixes two incorrect `reqToken()` in `/notifications` endpoints (caused by #24767) Co-authored-by: Zettat123 <zettat123@gmail.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
Hi, I've been fuzzing Gitea with openapi-fuzzer and found, that sending a PUT request to
/api/v1/notifications
endpoint with invalidlast_read_at
query parameter causes the Gitea to respond with internal server error 500 status code.request & response
logs
Gitea Version
1.19.3
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
linux
How are you running Gitea?
Database
SQLite
The text was updated successfully, but these errors were encountered: