open-telemetry / open-telemetry/opentelemetry-ruby
Exporters reading response body have no size limit
Open
Nobody has claimed this yet.
bug
stale
- Dominant language
- Ruby
- Stars
- 606
- Forks
- 301
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 42
Description
Our OTLP exporters read the full HTTP response body into memory without a size cap.
Limiting the read size may help prevent memory exhaustion exploits when the configured collector endpoint is attacker-controlled (or a network attacker can mitm the exporter connection).
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
Locate the OTLP exporter implementations that read HTTP response bodies and inspect any existing tests around those reads. Apply a bounded-read behavior consistently, then verify that tests cover oversized responses as well as normal responses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100