Skip to content

sorona.xyz bug bounty programs

opentelemetry.io Updated

Sorona.xyz runs two public programs: a Sorona bug bounty paying up to $1,500 and a Sorona bug bounty paying up to $1,500.

Top reward
$1,500
Sorona
Programs
2
2 pay cash
Targets in scope
21
2 types, deduplicated
Last change
None yet
Tracked since Nov 2026

Where to report

2 programs, side by side. Report where the affected target is in scope; when two programs cover it, pick the one that pays more.

Start here

OpenTelemetry Go

Sorona · Pays the most of the 2 programs: up to $1,500.

Amounts are the top reward per severity in the currency each program pays. Green marks the highest per severity. First response is the platform's measured average when it publishes one, else what the policy promises.

What is in scope

21 targets across all 2 programs, each listed once with the programs that cover it. 12 excluded.

  • https://opentelemetry.io

    Web

    Covered by OpenTelemetry Go

  • https://opentelemetry.io/docs/collector

    Web

    Covered by OpenTelemetry Collector

  • Baggage and TraceContext header parsing, which processes attacker-controllable HTTP headers on every single request

    Products and areas

    Covered by OpenTelemetry Go

  • Cardinality control and attribute handling in the metric SDK, the point at which a request attribute becomes a metric label and an allocation

    Products and areas

    Covered by OpenTelemetry Go

  • Connectors and the service graph that routes data between pipelines

    Products and areas

    Covered by OpenTelemetry Collector

  • Every exporter and the credentials it holds for its backend, along with the retry and queue behaviour behind it

    Products and areas

    Covered by OpenTelemetry Collector

  • Every receiver, starting with OTLP over gRPC and HTTP, and extending across the Prometheus, Jaeger, Zipkin, Fluent Forward, syslog, statsd, kafka, filelog, hostmetrics and webhook receivers in contrib

    Products and areas

    Covered by OpenTelemetry Collector

  • Exporter transport and configuration, covering endpoint selection, TLS setup and the credentials an exporter carries off-host

    Products and areas

    Covered by OpenTelemetry Go

  • Extensions in full, covering the auth extensions (bearer token, OIDC, basic auth, sigv4, headers setter), the health check, pprof and zpages

    Products and areas

    Covered by OpenTelemetry Collector

  • open-telemetry/opentelemetry-go in full: the trace, metric and log SDKs, the OTLP exporters over gRPC and HTTP, the W3C TraceContext and Baggage propagators, and the semantic-convention packages

    Products and areas

    Covered by OpenTelemetry Go

  • open-telemetry/opentelemetry-go-contrib in full, meaning every instrumentation library it carries, of which otelhttp and otelgrpc matter most because they sit in the request path of an enormous number of Go services

    Products and areas

    Covered by OpenTelemetry Go

  • Protobuf and JSON decoding on the OTLP receive and export paths

    Products and areas

    Covered by OpenTelemetry Go

  • The batch processor, the memory limiter and the behaviour of the whole pipeline under load or backpressure

    Products and areas

    Covered by OpenTelemetry Collector

  • The builder that assembles a custom distribution and the component manifest it consumes

    Products and areas

    Covered by OpenTelemetry Collector

  • The Collector's own internal telemetry: the metrics it exposes about itself and the debug surfaces that describe its configuration

    Products and areas

    Covered by OpenTelemetry Collector

  • The configuration loader, environment variable expansion, and the confmap providers that resolve configuration from a file, an HTTP endpoint, S3 or another remote source

    Products and areas

    Covered by OpenTelemetry Collector

  • The OpAMP supervisor and remote configuration where it is enabled, which lets a control server change what the Collector runs

    Products and areas

    Covered by OpenTelemetry Collector

  • The processors, in particular the transform, filter, attributes, redaction and tail sampling processors that decide what leaves the pipeline

    Products and areas

    Covered by OpenTelemetry Collector

  • The project takes reports at [email protected] or through GitHub private advisory reporting and publishes a GHSA. The Google patch pathway is narrower and reaches two repositories only: opentelemetry-go and opentelemetry-go-contrib

    Products and areas

    Covered by OpenTelemetry Go

  • The security process asks for a private GitHub advisory on the collector repositories with [email protected] as fallback, and declares no boundary narrower than the Collector itself. Both the core and contrib repositories sit inside it

    Products and areas

    Covered by OpenTelemetry Collector

  • TLS configuration on every receiver and exporter, including certificate verification, minimum versions and mutual TLS

    Products and areas

    Covered by OpenTelemetry Collector

No target matches. Try part of a host name, such as the company name.

Out of scope 12

Don't test these. A program can exclude a host another program covers; the program you report to decides.

  • A pipeline an operator configured to forward or expose data they did not intend to forward or expose

    OpenTelemetry Collector

  • One-line fixes for non-exploitable crashes, which the Patch Rewards rules exclude by name

    OpenTelemetry Go

  • opentelemetry-collector and opentelemetry-collector-contrib, which have no OSS-Fuzz project and therefore no patch pathway

    OpenTelemetry Go

  • Patches outside the one-to-twelve-month age window the rules impose

    OpenTelemetry Go

  • Resource consumption that the memory limiter is configured to allow

    OpenTelemetry Collector

  • The bare opentelemetry OSS-Fuzz entry, which points at open-telemetry/community, a governance repository rather than code, and must not be cited as covering anything

    OpenTelemetry Go

  • The non-Go language SDKs, covering Java, Python, JavaScript, .NET, PHP, Rust and C++, none of which has an OSS-Fuzz directory

    OpenTelemetry Go

  • The observability backends the Collector exports to, which belong to their vendors

    OpenTelemetry Collector

  • The OpenTelemetry language SDKs and instrumentation libraries, separate repositories with their own advisory streams

    OpenTelemetry Collector

  • The OpenTelemetry Operator and Helm charts, which live in their own repositories

    OpenTelemetry Collector

  • Third-party components maintained outside the two collector repositories

    OpenTelemetry Collector

  • Vendor distributions of OpenTelemetry, which belong to the vendor's own program where one exists

    OpenTelemetry Go

Recent changes

Reward and scope changes across every sorona.xyz program, newest first.

No changes recorded yet. New targets and reward moves show up here and in the RSS feed.

Recent CVEs

Published vulnerabilities in sorona.xyz products, from the NVD.

Search NVD
  • opentelemetry-js is the OpenTelemetry JavaScript Client. Prior to 2.8.0, W3CBaggagePropagator.extract() in @opentelemetry/core does not enforce size limits when parsing inbound baggage HTTP headers. The W3C Baggage specification recommends a maximum of 8,192 bytes and 180 entries; these limits were only enforced on the outbound (inject()) path, not on the inbound (extract()) path. Parsing oversize

  • opentelemetry-js is the OpenTelemetry JavaScript Client. Prior to 2.8.0, W3CBaggagePropagator.extract() in @opentelemetry/core does not enforce size limits when parsing inbound baggage HTTP headers. The W3C Baggage specification recommends a maximum of 8,192 bytes and 180 entries; these limits were only enforced on the outbound (inject()) path, not on the inbound (extract()) path. Parsing oversize

  • OpenTelemetry-cpp is the C++ implementation of OpenTelemetry. Prior to release 1.27.0, the OTLP HTTP exporters (traces/metrics/logs) read the full HTTP response into an in-memory vector of bytes without a size cap. This is exploitable for memory exhaustion when the configured collector endpoint is attacker-controlled (or a network attacker can MITM the exporter connection). This vulnerability is f

  • OpenTelemetry-cpp is the C++ implementation of OpenTelemetry. Prior to release 1.27.0, the OTLP HTTP exporters (traces/metrics/logs) read the full HTTP response into an in-memory vector of bytes without a size cap. This is exploitable for memory exhaustion when the configured collector endpoint is attacker-controlled (or a network attacker can MITM the exporter connection). This vulnerability is f

  • OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to version 0.0.17, `go.opentelemetry.io/otel/schema/v1.0` and `go.opentelemetry.io/otel/schema/v1.1` leaks one file descriptor on each successful `ParseFile` call. `ParseFile` opens the schema file and passes it to `Parse` without closing it; repeated parsing in a long-running process can exhaust the process file descriptor limit an

  • OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to version 0.0.17, `go.opentelemetry.io/otel/schema/v1.0` and `go.opentelemetry.io/otel/schema/v1.1` leaks one file descriptor on each successful `ParseFile` call. `ParseFile` opens the schema file and passes it to `Parse` without closing it; repeated parsing in a long-running process can exhaust the process file descriptor limit an

  • OpenTelemetry-Go is the Go implementation of OpenTelemetry. Versions 1.41.0 and 1.43.0 removed raw-length rejection and it causes `Parse` to process arbitrarily large/invalid baggage headers and log errors, enabling DoS via oversized inputs. Versions 1.42.0 and 1.44.0 fix the issue.

  • OpenTelemetry-Go is the Go implementation of OpenTelemetry. Versions 1.41.0 and 1.43.0 removed raw-length rejection and it causes `Parse` to process arbitrarily large/invalid baggage headers and log errors, enabling DoS via oversized inputs. Versions 1.42.0 and 1.44.0 fix the issue.

About this page

This page gathers every public program listed under opentelemetry.io: platform programs, self-hosted policies and security.txt contacts. Each program's own policy decides what is in scope and what it pays; check it before you test.

Something wrong or missing? Report a correction.