Default_Unexpected_Exception_Handler may leak sensitive data
Nobody has claimed this yet.
- Dominant language
- Ada
- Stars
- 162
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Description
If a file named 500.tmplt does not exist, AWS.Server.Default_Unexpected_Exception_Handler will send the traceback from Ada.Exceptions.Exception_Information to clients, leaking information about memory offsets and program information that may be useful to an attacker trying to build an exploit.
See CWE-209 for more information about this class of vulnerability.
I believe this is unsafe default behavior and Default_Unexpected_Exception_Handler should be modified to only send Exception_Information to Log and/or Standard_Error and return a generic 500 Internal Server Error to clients.
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 at AWS.Server.Default_Unexpected_Exception_Handler and inspect how it handles a missing 500.tmplt file. Verify where Ada.Exceptions.Exception_Information is sent, then ensure exception details go only to Log and/or Standard_Error while clients receive a generic 500 Internal Server Error.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100