Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2024-55886 Overview
CVE-2024-55886 is an authentication bypass vulnerability in OpenSearch Data Prepper, a component that accepts, filters, transforms, enriches, and routes data at scale. The flaw affects the OpenTelemetry Logs source in Data Prepper versions 2.1.0 through 2.10.1. Custom authentication plugins that implement the getHttpAuthenticationService() method skip authentication entirely, letting unauthorized users ingest OpenTelemetry Logs data. The built-in http_basic authentication provider is not affected. The issue is tracked under [CWE-287] Improper Authentication and is fixed in Data Prepper 2.10.2.
Critical Impact
Unauthorized remote actors can inject OpenTelemetry Logs data into Data Prepper pipelines that rely on vulnerable custom GrpcAuthenticationProvider implementations, undermining log integrity and downstream analytics.
Affected Products
- Amazon OpenSearch Data Prepper 2.1.0 through 2.10.1
- Pipelines using the OpenTelemetry Logs source with custom GrpcAuthenticationProvider plugins
- Deployments relying on getHttpAuthenticationService() for authentication enforcement
Discovery Timeline
- 2024-12-12 - CVE-2024-55886 published to NVD
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2024-55886
Vulnerability Analysis
OpenSearch Data Prepper exposes a plugin interface, GrpcAuthenticationProvider, that custom authentication modules implement to protect gRPC sources. The OpenTelemetry Logs source invokes the getAuthenticationInterceptor() method on this provider to enforce authentication on incoming requests. Custom plugins that only implement the alternative getHttpAuthenticationService() method are never consulted during gRPC processing. The OpenTelemetry Logs source therefore accepts requests without validating credentials, allowing unauthenticated log ingestion.
Root Cause
The root cause is a missing authentication enforcement path for custom plugins that extend getHttpAuthenticationService() instead of getAuthenticationInterceptor(). Data Prepper's OpenTelemetry Logs source does not fall back to the HTTP authentication service, resulting in an effectively anonymous endpoint. This maps to [CWE-287] Improper Authentication.
Attack Vector
An attacker with network access to the OpenTelemetry Logs gRPC endpoint can send crafted log records without providing valid credentials. The attack requires a vulnerable custom authentication plugin to be deployed, which limits exploitability to specific configurations. Successful exploitation enables log injection, which can corrupt analytics, trigger misleading alerts, or mask malicious activity in downstream systems.
No verified public proof-of-concept code is available. For additional technical context, consult the GitHub Security Advisory GHSA-725p-63vv-v948.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2024-55886
Indicators of Compromise
- Unexpected spikes in OpenTelemetry Logs ingestion volume on Data Prepper pipelines
- Log records originating from source IP addresses outside expected telemetry sources
- Absence of authentication-related entries in Data Prepper access logs for successful ingestion events
Detection Strategies
- Audit all custom GrpcAuthenticationProvider implementations to identify plugins that implement getHttpAuthenticationService() without getAuthenticationInterceptor()
- Compare log source identifiers against an allowlist of authorized OpenTelemetry collectors
- Review Data Prepper configuration files to enumerate pipelines running the OpenTelemetry Logs source
Monitoring Recommendations
- Enable verbose logging on the Data Prepper OpenTelemetry Logs source to capture client metadata for each request
- Forward Data Prepper access and application logs to a centralized SIEM for correlation with network telemetry
- Alert on ingestion requests that lack expected authentication headers or client certificates
How to Mitigate CVE-2024-55886
Immediate Actions Required
- Upgrade Data Prepper to version 2.10.2 or later, which contains the fix
- Inventory all pipelines using the OpenTelemetry Logs source and identify those relying on custom authentication plugins
- Restrict network access to Data Prepper gRPC endpoints using firewall rules or security groups until patching completes
Patch Information
Amazon released Data Prepper 2.10.2 with a corrected authentication flow for the OpenTelemetry Logs source. The patch ensures custom GrpcAuthenticationProvider plugins are consistently enforced regardless of which authentication method they implement. Refer to the GitHub Security Advisory GHSA-725p-63vv-v948 for release details.
Workarounds
- Switch affected pipelines to the built-in http_basic authentication provider, which is not vulnerable
- Deploy an authentication proxy such as an API gateway or reverse proxy in front of Data Prepper instances running the OpenTelemetry Logs source
- Place Data Prepper endpoints inside a private network segment reachable only by trusted OpenTelemetry collectors
# Example pipeline configuration using the built-in http_basic provider
otel-logs-pipeline:
source:
otel_logs_source:
authentication:
http_basic:
username: "otel-collector"
password: "${OTEL_COLLECTOR_PASSWORD}"
sink:
- opensearch:
hosts: ["https://opensearch:9200"]
index: "otel-logs"
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

