oasisprotocol / oasisprotocol/oasis-core
[EXT-SEC-AUDIT] Excessive gRPC timeout
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
Issue transferred from an external security audit report.
Nodes are configured to use an excessively long timeout of 10 minutes when accepting
gRPC connections.
Short term, set MaxConnectionIdle to a lower value (e.g., 5 seconds).
Long term, make this value configurable to support applications that require a longer timeout. Ensure the default value is kept low, as recommended above.
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 in go/common/grpc/grpc.go at the referenced MaxConnectionIdle configuration and inspect how gRPC connection options are constructed. Done means reducing the default timeout to a low value such as 5 seconds and making the value configurable for applications that need a longer timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100