Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Envoy Gateway Log Injection Vulnerability

Historical advisory saved 24 Oct 2026 13:19:41 UTC. The publisher may have updated it since then. Latest advisory.

osv · GHSA-mf24-chxh-hmvj

Published

### Impact In all Envoy Gateway versions prior to 1.2.7 and 1.3.1 a default Envoy Proxy access log configuration is used. This format is vulnerable to log injection attacks. If the attacker uses a specially crafted user-agent which performs json injection, then he could add and overwrite fields to the access log. Examples of attacks include: - Using following string as user agent : `HELLO-WORLD", "evil-ip": "1.1.1.1", "x-forwarded-for": "1.1.1.1` would lead to setting of new access log properties and overwrite of existing properties. Existing properties such as the value of the X-Forwarded-For header may have importance for security analysis of access logs, and their overwrite can be used to hide malicious activity. - Using the following string as user-agent : `"` which renders an invalid json document. The invalid document may fail to be processed by observability solutions, which would allow attacker to hide malicious activity. ### Patches 1.3.1, 1.2.7 ### Fix Using JSON format as the default format for access logs. The logged document will contain the same key and values as before. Only the order of properties is different inside the logged document. ### Workaround One can overwrite the old text based default format with JSON formatter by setting the following property: "EnvoyProxy.spec.telemetry.[accessLog](https://gateway.envoyproxy.io/v1.3/api/extension_types/#proxyaccesslog)" to ``` settings: - format: type: JSON json: start_time: '%START_TIME%' method: '%REQ(:METHOD)%' x-envoy-origin-path: '%REQ(X-ENVOY-ORIGINAL-PATH?:PATH)%' protocol: '%PROTOCOL%' response_code: '%RESPONSE_CODE%' response_flags: '%RESPONSE_FLAGS%' response_code_details: '%RESPONSE_CODE_DETAILS%' connection_termination_details: '%CONNECTION_TERMINATION_DETAILS%' upstream_transport_failure_reason: '%UPSTREAM_TRANSPORT_FAILURE_REASON%' bytes_received: '%BYTES_RECEIVED%' bytes_sent: '%BYTES_SENT%' duration: '%DURATION%' x-envoy-upstream-service-time: '%RESP(X-ENVOY-UPSTREAM-SERVICE-TIME)%' x-forwarded-for: '%REQ(X-FORWARDED-FOR)%' user-agent: '%REQ(USER-AGENT)%' x-request-id: '%REQ(X-REQUEST-ID)%' :authority: '%REQ(:AUTHORITY)%' upstream_host: '%UPSTREAM_HOST%' upstream_cluster: '%UPSTREAM_CLUSTER%' upstream_local_address: '%UPSTREAM_LOCAL_ADDRESS%' downstream_local_address: '%DOWNSTREAM_LOCAL_ADDRESS%' downstream_remote_address: '%DOWNSTREAM_REMOTE_ADDRESS%' requested_server_name: '%REQUESTED_SERVER_NAME%' route_name: '%ROUTE_NAME%' ``` see API definition [here](https://gateway.envoyproxy.io/v1.3/api/extension_types/#proxyaccesslogformat) ### References _Are there any links users can visit to find out more?_

Source published
6 Mar 2025 19:11:39 UTC
Source modified
10 Sep 2026 03:50:56 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Publisher rating · MODERATE

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 18 Nov 03:30 UTC · 273 of 275 readable · 249 fully read · 20 waiting for GitHub's hourly limit · documentation 454/469 current