OpenTelemetry.Exporter.Jaeger vulnerabilities
Jaeger exporter for OpenTelemetry .NET
- Registry
- NuGet
- Latest
- 1.5.1
- License
- Apache-2.0
1 known advisory
The latest version, 1.5.1, is affected by 1 of them.
Is your project on an affected OpenTelemetry.Exporter.Jaeger?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for OpenTelemetry.Exporter.Jaeger
OpenTelemetry .NET has potential memory exhaustion via unbounded pooled-list sizing in Jaeger exporter conversion path
- Affected
- <=1.6.0-rc.1
- Fixed in
- No fix released
Is your OpenTelemetry.Exporter.Jaeger version vulnerable?
- OpenTelemetry.Exporter.Jaeger 1.51 advisory in 1.5.1
- OpenTelemetry.Exporter.Jaeger 1.41 advisory in 1.4.0
- OpenTelemetry.Exporter.Jaeger 1.31 advisory in 1.3.2
- OpenTelemetry.Exporter.Jaeger 1.21 advisory in 1.2.0
- OpenTelemetry.Exporter.Jaeger 1.11 advisory in 1.1.0
- OpenTelemetry.Exporter.Jaeger 1.01 advisory in 1.0.1
Which of your client projects still run an old OpenTelemetry.Exporter.Jaeger?
NPMscan reads the packages.lock.json and .csproj files in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other NuGet packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the NuGet registry.