https://db.gcve.eu/sightings/feed 2026-06-06T15:15:53.657466+00:00 Vulnerability-Lookup info@gcve.eu python-feedgen Contains only the most 10 recent sightings. https://db.gcve.eu/sighting/2dbcdb93-68a4-4704-8d27-1e5163a86d35/export 2026-06-06T15:15:53.987850+00:00 cedric https://db.gcve.eu/user/cedric {"uuid": "2dbcdb93-68a4-4704-8d27-1e5163a86d35", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2021-32772", "type": "seen", "source": "https://t.me/cibsecurity/26748", "content": "\u203c CVE-2021-32772 \u203c\n\nPoddycast is a podcast app made with Electron. Prior to version 0.8.1, an attacker can create a podcast or episode with malicious characters and execute commands on the client machine. The application does not clean the HTML characters of the podcast information obtained from the Feed, which allows the injection of HTML and JS code (cross-site scripting). Being an application made in electron, cross-site scripting can be scaled to remote code execution, making it possible to execute commands on the machine where the application is running. The vulnerability is patched in Poddycast version 0.8.1.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-08-03T18:28:04.000000Z"} 2021-08-03T18:28:04+00:00 https://db.gcve.eu/sighting/e3b35a79-aec5-427d-a76c-d51ba143b4b1/export 2026-06-06T15:15:53.987791+00:00 cedric https://db.gcve.eu/user/cedric {"uuid": "e3b35a79-aec5-427d-a76c-d51ba143b4b1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2021-32777", "type": "seen", "source": "https://t.me/cibsecurity/27847", "content": "\u203c CVE-2021-32777 \u203c\n\nEnvoy 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 authorization. Attackers may be able to escalate privileges when using ext-authz extension or back end service that uses multiple value headers for authorization. A specifically constructed request may be delivered by an untrusted downstream peer in the presence of ext-authz extension. Envoy versions 1.19.1, 1.18.4, 1.17.4, 1.16.5 contain fixes to the ext-authz extension to correctly merge multiple request header values, when sending request for authorization.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-08-25T00:23:28.000000Z"} 2021-08-25T00:23:28+00:00 https://db.gcve.eu/sighting/221b3e14-37ea-4a80-843f-d47ed3cafd0e/export 2026-06-06T15:15:53.987727+00:00 cedric https://db.gcve.eu/user/cedric {"uuid": "221b3e14-37ea-4a80-843f-d47ed3cafd0e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2021-32779", "type": "seen", "source": "https://t.me/cibsecurity/27848", "content": "\u203c CVE-2021-32779 \u203c\n\nEnvoy is an open source L7 proxy and communication bus designed for large modern service oriented architectures. In affected versions envoy incorrectly handled a URI '#fragment' element as part of the path element. Envoy is configured with an RBAC filter for authorization or similar mechanism with an explicit case of a final \"/admin\" path element, or is using a negative assertion with final path element of \"/admin\". The client sends request to \"/app1/admin#foo\". In Envoy prior to 1.18.0, or 1.18.0+ configured with path_normalization=false. Envoy treats fragment as a suffix of the query string when present, or as a suffix of the path when query string is absent, so it evaluates the final path element as \"/admin#foo\" and mismatches with the configured \"/admin\" path element. In Envoy 1.18.0+ configured with path_normalization=true. Envoy transforms this to /app1/admin%23foo and mismatches with the configured /admin prefix. The resulting URI is sent to the next server-agent with the offending \"#foo\" fragment which violates RFC3986 or with the nonsensical \"%23foo\" text appended. A specifically constructed request with URI containing '#fragment' element delivered by an untrusted client in the presence of path based request authorization resulting in escalation of Privileges when path based request authorization extensions. Envoy versions 1.19.1, 1.18.4, 1.17.4, 1.16.5 contain fixes that removes fragment from URI path in incoming requests.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-08-25T00:23:30.000000Z"} 2021-08-25T00:23:30+00:00 https://db.gcve.eu/sighting/49f982d4-d6a2-4e9d-8821-5bc529775401/export 2026-06-06T15:15:53.987668+00:00 cedric https://db.gcve.eu/user/cedric {"uuid": "49f982d4-d6a2-4e9d-8821-5bc529775401", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2021-32778", "type": "seen", "source": "https://t.me/cibsecurity/27851", "content": "\u203c CVE-2021-32778 \u203c\n\nEnvoy is an open source L7 proxy and communication bus designed for large modern service oriented architectures. In affected versions envoy\u00e2\u20ac\u2122s procedure for resetting a HTTP/2 stream has O(N^2) complexity, leading to high CPU utilization when a large number of streams are reset. Deployments are susceptible to Denial of Service when Envoy is configured with high limit on H/2 concurrent streams. An attacker wishing to exploit this vulnerability would require a client opening and closing a large number of H/2 streams. Envoy versions 1.19.1, 1.18.4, 1.17.4, 1.16.5 contain fixes to reduce time complexity of resetting HTTP/2 streams. As a workaround users may limit the number of simultaneous HTTP/2 dreams for upstream and downstream peers to a low number, i.e. 100.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-08-25T00:23:34.000000Z"} 2021-08-25T00:23:34+00:00 https://db.gcve.eu/sighting/e55e8fa1-a564-4a40-b233-0b7f2e83de47/export 2026-06-06T15:15:53.987611+00:00 cedric https://db.gcve.eu/user/cedric {"uuid": "e55e8fa1-a564-4a40-b233-0b7f2e83de47", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2021-32777", "type": "seen", "source": "https://t.me/cibsecurity/28639", "content": "\u203c CVE-2021-39206 \u203c\n\nPomerium is an open source identity-aware access proxy. Envoy, which Pomerium is based on, contains two authorization related vulnerabilities CVE-2021-32777 and CVE-2021-32779. This may lead to incorrect routing or authorization policy decisions. With specially crafted requests, incorrect authorization or routing decisions may be made by Pomerium. Pomerium v0.14.8 and v0.15.1 contain an upgraded envoy binary with these vulnerabilities patched. This issue can only be triggered when using path prefix based policy. Removing any such policies should provide mitigation.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-09-10T02:29:59.000000Z"} 2021-09-10T02:29:59+00:00 https://db.gcve.eu/sighting/6b7446aa-5d43-45bc-8c7e-02582fc7be22/export 2026-06-06T15:15:53.987528+00:00 cedric https://db.gcve.eu/user/cedric {"uuid": "6b7446aa-5d43-45bc-8c7e-02582fc7be22", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2021-32779", "type": "seen", "source": "https://t.me/cibsecurity/28639", "content": "\u203c CVE-2021-39206 \u203c\n\nPomerium is an open source identity-aware access proxy. Envoy, which Pomerium is based on, contains two authorization related vulnerabilities CVE-2021-32777 and CVE-2021-32779. This may lead to incorrect routing or authorization policy decisions. With specially crafted requests, incorrect authorization or routing decisions may be made by Pomerium. Pomerium v0.14.8 and v0.15.1 contain an upgraded envoy binary with these vulnerabilities patched. This issue can only be triggered when using path prefix based policy. Removing any such policies should provide mitigation.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-09-10T02:29:59.000000Z"} 2021-09-10T02:29:59+00:00 https://db.gcve.eu/sighting/dd43b676-787d-46c3-bdd5-bcd7a3432c2b/export 2026-06-06T15:15:53.986096+00:00 cedric https://db.gcve.eu/user/cedric {"uuid": "dd43b676-787d-46c3-bdd5-bcd7a3432c2b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2021-32771", "type": "seen", "source": "https://t.me/cibsecurity/47595", "content": "\u203c CVE-2021-32771 \u203c\n\nContiki-NG is an open-source, cross-platform operating system for IoT devices. In affected versions it is possible to cause a buffer overflow when copying an IPv6 address prefix in the RPL-Classic implementation in Contiki-NG. In order to trigger the vulnerability, the Contiki-NG system must have joined an RPL DODAG. After that, an attacker can send a DAO packet with a Target option that contains a prefix length larger than 128 bits. The problem was fixed after the release of Contiki-NG 4.7. Users unable to upgrade may apply the patch in Contiki-NG PR #1615.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-08-05T00:19:59.000000Z"} 2022-08-05T00:19:59+00:00