Invalid log message and response on missing credentials
Open
Nobody has claimed this yet.
bug
Priority: High
size/M
V3
- Dominant language
- Java
- Stars
- 92
- Forks
- 81
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 46
Description
- The code above write always a message about status 400 even though a different code is returned.
- If the application returns 401 there should be just one message, multiple messages for 401 could help an attacker
- expired account is one exception
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with AuthExceptionHandler.java at lines 89-139, focusing on how the returned status and log message are selected for missing credentials. Confirm the intended behavior for status 400 and status 401, including the expired-account exception. Done means the log message matches the returned status and 401 responses do not expose multiple messages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100