OWASP / OWASP/SecurityShepherd
Security Misconfiguration: Sensitive Details returned in stack trace
Open
Nobody has claimed this yet.
Levels
WebApp
- Dominant language
- Java
- Stars
- 1.5k
- Forks
- 515
- Avg merge
- 3h 46m
- Merged PRs (30d)
- 1
Description
Force a 500 error and get The key from the disclosed information. Stack trace may have to be simulated, as Shepherd server masks the output
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 by reproducing a 500 error in SecurityShepherd and inspect the resulting stack trace, using the issue's warning that Shepherd may mask the output. Trace the disclosed information to determine which sensitive key is exposed; done means the error response no longer reveals that key.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100