GHSA-W2JH-77FQ-7GP8
OpAMP client reads unbounded HTTP response bodies
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche 0.2.0-alpha.1 | OpenTelemetry.OpAmp.Client · -14 d desde divulgación | |
| Divulgación | Publicada | GHSA-W2JH-77FQ-7GP8 divulgada | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Detectada | Ingresó al índice |
Summary
When receiving responses from the OpAMP server over HTTP, the OpAMP client allocates an unbounded buffer to read all bytes from the server, with no upper-bound on the number of bytes consumed.
This could cause memory exhaustion in the consuming application if the configured OpAMP server is attacker-controlled (or a network attacker can MitM the connection) and an extremely large body is returned in the response.
Details
#2926 https://github.com/open-telemetry/opentelemetry-dotnet-contrib/pull/2926 introduced the initial HTTP transport components which uses `ReadAsByteArrayAsync` to copy the `HttpResponseMessage.Content` into a byte array. This code path allows an unbounded read of the entire HTTP response message.
Impact
If an application using the OpAMP client is configured to use an OpAMP server that is attacker-controlled (or a network attacker can MitM the connection) and an extremely large body is returned in the response, the application could have its memory exhausted and create a denial-of-service condition.
Mitigation
The application's configured OpAMP server needs to behave maliciously. If the OpAMP server is a well-behaved implementation, response bodies should not be excessively large.
Workarounds
None known.
Remediation
#4116 https://github.com/open-telemetry/opentelemetry-dotnet-contrib/pull/4116 updates the OpAMP client HTTP transport to limit the maximum size of responses to 128KB.
Resources
- #2926
https://github.com/open-telemetry/opentelemetry-dotnet-contrib/pull/2926 - #4116
https://github.com/open-telemetry/opentelemetry-dotnet-contrib/pull/4116 - CWE-789
https://cwe.mitre.org/data/definitions/789.html
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
nugetOpenTelemetry.OpAmp.Client |
Corregida | 0.2.0-alpha.1 | -14 d | 0.11.0-alpha.1 no afectada |
0.2.0-alpha.1Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://nvd.nist.gov/vuln/detail/CVE-2026-42348https://github.com/open-telemetry/opentelemetry-dotnet-contrib/security/advisories/GHSA-w2jh-77fq-7gp8https://github.com/open-telemetry/opentelemetry-dotnet-contrib/pull/4116https://github.com/open-telemetry/opentelemetry-dotnet-contrib/commit/bf1fad4fa298ff451cda0efb0ee9c7a7eb46212ahttps://github.com/open-telemetry/opentelemetry-dotnet-contribLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
