Vulnerability database · updated every 15 minutes
New vulnerabilities in the software websites run.
CVEs and security advisories for WordPress, its plugins and themes, npm, PyPI and the servers behind websites, merged from NVD, the CVE Program, GitHub, OSV.dev and WPVulnerability, with CISA's list of the ones attackers exploit.
- Tracked
- 55,388
- Published in 7 days
- 1,884
- Critical in 30 days
- 489
- Actively exploited
- 542
Results for “Envoy”
132 vulnerabilities- High 7.5
CVE-2021-32780 · Envoy
Envoy is an open source L7 proxy and communication bus designed for large modern service oriented architectures. In affected versions Envoy transitions a H/2 connection to the CLOSED state when it receives a GOAWAY frame without any streams outstanding. The connection state is transitioned to DRAINING when it receives a SETTING frame with the SETTINGS_MAX_CONCURRENT_STREAMS parameter set to 0.…
Published 24 Aug 2021 · Fixed in 1.18.4 · NVD - High 8.3
CVE-2021-32777 · Envoy
Envoy is an open source L7 proxy and communication bus designed for large modern service oriented architectures. In affected versions when ext-authz extension is sending request headers to the external authorization service it must merge multiple value headers according to the HTTP spec. However, only the last header value is sent. This may allow specifically crafted requests to bypass…
Published 24 Aug 2021 · Fixed in 1.16.5, 1.17.4, 1.18.4 · NVD - High 7.5
CVE-2021-32781 · Envoy
Continued processing of requests after locally generated response
Published 24 Aug 2021 · Fixed in 1.16.5, 1.17.4, 1.18.4 · NVD, Project advisories (GitHub) - High 7.5
CVE-2021-32778 · Envoy
Excessive CPU utilization when closing HTTP/2 streams
Published 24 Aug 2021 · Fixed in 1.16.5, 1.17.4, 1.18.4 · NVD, Project advisories (GitHub) - High 8.3
CVE-2021-32779 · Envoy
Incorrectly handling of URI '#fragment' element as part of the path element
Published 24 Aug 2021 · Fixed in 1.16.5, 1.17.4, 1.18.4 · NVD, Project advisories (GitHub) - High 8.3
CVE-2021-29492 · Envoy
Envoy is a cloud-native edge/middle/service proxy. Envoy does not decode escaped slash sequences `%2F` and `%5C` in HTTP URL paths in versions 1.18.2 and before. A remote attacker may craft a path with escaped slashes, e.g. `/something%2F..%2Fadmin`, to bypass access control, e.g. a block on `/admin`. A backend server could then decode slash sequences and normalize path and provide an attacker…
Published 28 May 2021 · Fixed in 1.16.4, 1.17.3, 1.18.3 · NVD - High 7.5
CVE-2021-29258 · Envoy
An issue was discovered in Envoy 1.14.0. There is a remotely exploitable crash for HTTP2 Metadata, because an empty METADATA map triggers a Reachable Assertion.
Published 20 May 2021 · NVD - High 7.5
CVE-2021-28683 · Envoy
An issue was discovered in Envoy through 1.71.1. There is a remotely exploitable NULL pointer dereference and crash in TLS when an unknown TLS alert code is received.
Published 20 May 2021 · NVD - High 7.5
CVE-2021-28682 · Envoy
An issue was discovered in Envoy through 1.71.1. There is a remotely exploitable integer overflow in which a very large grpc-timeout value leads to unexpected timeout calculations.
Published 20 May 2021 · NVD - High 8.2
CVE-2021-21378 · Envoy
Envoy is a cloud-native high-performance edge/middle/service proxy. In Envoy version 1.17.0 an attacker can bypass authentication by presenting a JWT token with an issuer that is not in the provider list when Envoy's JWT Authentication filter is configured with the `allow_missing` requirement under `requires_any` due to a mistake in implementation. Envoy's JWT Authentication filter can be…
Published 11 Mar 2021 · NVD - High 7.5
CVE-2020-35471 · Envoy
Envoy before 1.16.1 mishandles dropped and truncated datagrams, as demonstrated by a segmentation fault for a UDP packet size larger than 1500.
Published 15 Dec 2020 · Fixed in 1.16.1 · NVD - High 8.8
CVE-2020-35470 · Envoy
Envoy before 1.16.1 logs an incorrect downstream address because it considers only the directly connected peer, not the information in the proxy protocol header. This affects situations with tcp-proxy as the network filter (not HTTP filters).
Published 15 Dec 2020 · Fixed in 1.16.1 · NVD - High 7.5
CVE-2020-25018 · Envoy
Envoy master between 2d69e30 and 3b5acb2 may fail to parse request URL that requires host canonicalization.
Published 1 Oct 2020 · Fixed in 3b5acb2 · NVD - High 8.3
CVE-2020-25017 · Envoy
Envoy through 1.15.0 only considers the first value when multiple header values are present for some HTTP headers. Envoy’s setCopy() header map API does not replace all existing occurences of a non-inline header.
Published 1 Oct 2020 · Fixed in 1.13.4, 1.14.4, 1.15.1 · NVD - Medium 5.4
CVE-2020-15104 · Envoy
In Envoy before versions 1.12.6, 1.13.4, 1.14.4, and 1.15.0 when validating TLS certificates, Envoy would incorrectly allow a wildcard DNS Subject Alternative Name apply to multiple subdomains. For example, with a SAN of *.example.com, Envoy would incorrectly allow nested.subdomain.example.com, when it should only allow subdomain.example.com. This defect applies to both validating a client TLS…
Published 14 Jul 2020 · Fixed in 1.12.6, 1.13.4, 1.14.4 · NVD - High 7.5
CVE-2020-8663 · Envoy
Envoy version 1.14.2, 1.13.2, 1.12.4 or earlier may exhaust file descriptors and/or memory when accepting too many connections.
Published 1 Jul 2020 · NVD - High 7.5
CVE-2020-12605 · Envoy
Envoy version 1.14.2, 1.13.2, 1.12.4 or earlier may consume excessive amounts of memory when processing HTTP/1.1 headers with long field names or requests with long URLs.
Published 1 Jul 2020 · NVD - High 7.5
CVE-2020-12604 · Envoy
Envoy version 1.14.2, 1.13.2, 1.12.4 or earlier is susceptible to increased memory usage in the case where an HTTP/2 client requests a large payload but does not send enough window updates to consume the entire stream and does not reset the stream.
Published 1 Jul 2020 · NVD - High 7.5
CVE-2020-12603 · Envoy
Envoy version 1.14.2, 1.13.2, 1.12.4 or earlier may consume excessive amounts of memory when proxying HTTP/2 requests or responses with many small (i.e. 1 byte) data frames.
Published 1 Jul 2020 · NVD - Low 3.1
CVE-2020-11767 · Envoy
Istio through 1.5.1 and Envoy through 1.14.1 have a data-leak issue. If there is a TCP connection (negotiated with SNI over HTTPS) to *.example.com, a request for a domain concurrently configured explicitly (e.g., abc.example.com) is sent to the server(s) listening behind *.example.com. The outcome should instead be 421 Misdirected Request. Imagine a shared caching forward proxy re-using an…
Published 15 Apr 2020 · NVD - Medium 5.3
CVE-2020-8660 · Envoy
CNCF Envoy through 1.13.0 TLS inspector bypass. TLS inspector could have been bypassed (not recognized as a TLS client) by a client using only TLS 1.3. Because TLS extensions (SNI, ALPN) were not inspected, those connections might have been matched to a wrong filter chain, possibly bypassing some security restrictions in the process.
Published 4 Mar 2020 · Fixed in 1.12.3, 1.13.1 · NVD - Medium 5.3
CVE-2020-8664 · Envoy
CNCF Envoy through 1.13.0 has incorrect Access Control when using SDS with Combined Validation Context. Using the same secret (e.g. trusted CA) across many resources together with the combined validation context could lead to the “static” part of the validation context to be not applied, even though it was visible in the active config dump.
Published 4 Mar 2020 · NVD - High 7.5
CVE-2020-8661 · Envoy
CNCF Envoy through 1.13.0 may consume excessive amounts of memory when responding internally to pipelined requests.
Published 4 Mar 2020 · NVD - High 7.5
CVE-2020-8659 · Envoy
CNCF Envoy through 1.13.0 may consume excessive amounts of memory when proxying HTTP/1.1 requests or responses with many small (i.e. 1 byte) chunks.
Published 4 Mar 2020 · NVD - High 7.5
CVE-2019-18838 · Envoy
An issue was discovered in Envoy 1.12.0. Upon receipt of a malformed HTTP request without a Host header, it sends an internally generated "Invalid request" response. This internally generated response is dispatched through the configured encoder filter chain before being sent to the client. An encoder filter that invokes route manager APIs that access a request's Host header causes a NULL…
Published 13 Dec 2019 · NVD - Critical 9.8
CVE-2019-18802 · Envoy
An issue was discovered in Envoy 1.12.0. An untrusted remote client may send an HTTP header (such as Host) with whitespace after the header content. Envoy will treat "header-value " as a different string from "header-value" so for example with the Host header "example.com " one could bypass "example.com" matchers.
Published 13 Dec 2019 · NVD - Critical 9.8
CVE-2019-18801 · Envoy
An issue was discovered in Envoy 1.12.0. An untrusted remote client may send HTTP/2 requests that write to the heap outside of the request buffers when the upstream is HTTP/1. This may be used to corrupt nearby heap contents (leading to a query-of-death scenario) or may be used to bypass Envoy's access control mechanisms such as path based routing. An attacker can also modify requests from other…
Published 13 Dec 2019 · NVD - High 7.5
CVE-2019-18836 · Envoy
Envoy 1.12.0 allows a remote denial of service because of resource loops, as demonstrated by a single idle TCP connection being able to keep a worker thread in an infinite busy loop when continue_on_listener_filters_timeout is used."
Published 11 Nov 2019 · NVD - High 7.5
CVE-2019-15226 · Envoy
Upon receiving each incoming request header data, Envoy will iterate over existing request headers to verify that the total size of the headers stays below a maximum limit. The implementation in versions 1.10.0 through 1.11.1 for HTTP/1.x traffic and all versions of Envoy for HTTP/2 traffic had O(n^2) performance characteristics. A remote attacker may craft a request that stays below the maximum…
Published 9 Oct 2019 · NVD - High 7.5
CVE-2019-15225 · Envoy
In Envoy through 1.11.1, users may configure a route to match incoming path headers via the libstdc++ regular expression implementation. A remote attacker may send a request with a very long URI to result in a denial of service (memory consumption). This is a related issue to CVE-2019-14993.
Published 19 Aug 2019 · NVD - Critical 10.0
CVE-2019-9901 · Envoy
Envoy 1.9.0 and before does not normalize HTTP URL paths. A remote attacker may craft a relative path, e.g., something/../admin, to bypass access control, e.g., a block on /admin. A backend server could then interpret the non-normalized path and provide an attacker access beyond the scope provided for by the access control policy.
Published 25 Apr 2019 · NVD - High 8.3
CVE-2019-9900 · Envoy
When parsing HTTP/1.x header values, Envoy 1.9.0 and before does not reject embedded zero characters (NUL, ASCII 0x0). This allows remote attackers crafting header values containing embedded NUL characters to potentially bypass header matching rules, gaining access to unauthorized resources.
Published 25 Apr 2019 · NVD
Where it comes from
The list holds every advisory UpHeron reads for the software it watches: WordPress and every plugin and theme its plugin reports, the packages in monitored repositories and manifests, and the servers and frameworks found on monitored websites. One vulnerability from several sources is one entry, under its CVE.
- NVD, the US National Vulnerability Database. This product uses the NVD API but is not endorsed or certified by the NVD.
- New and changed records of the CVE Program, read every 15 minutes, so a rating or fix added after a CVE is published reaches the list, and its alerts, within the hour. CVE content © 1999–2026 The MITRE Corporation, used under the CVE terms of use; CVE® is a registered trademark of The MITRE Corporation.
- OSV.dev, with the GitHub Advisory Database (CC BY 4.0).
- WPVulnerability (CC0) for WordPress plugins and themes, and WordPress's own security advisories.
- Node.js's own security release posts, read every 15 minutes, which name its vulnerabilities the day they are fixed, days before their CVE records.
- The security advisories projects publish on GitHub, and the CVEs libraries such as Brotli name in their release notes, which also count for the runtimes that bundle them.
- CISA's Known Exploited Vulnerabilities catalog.
Each day's new ones, grouped, and every critical one as soon as we find it: on the blog.
Run WordPress? The UpHeron plugin alerts you the day one of these affects your own site.