https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 18 Oct 2026 10:27:49 +0000 https://cve.radiocsirt.org/vuln/bdu:2024-02677 bdu:2024-02677 https://cve.radiocsirt.org/vuln/bdu:2024-02677 https://cve.radiocsirt.org/vuln/cnvd-2024-14758 cnvd-2024-14758 https://cve.radiocsirt.org/vuln/cnvd-2024-14758 https://cve.radiocsirt.org/vuln/euvd-2026-216034 EUVD-2026-216034 https://cve.radiocsirt.org/vuln/euvd-2026-216034 https://cve.radiocsirt.org/vuln/fkie_cve-2022-34321 <p>Improper Authentication vulnerability in Apache Pulsar Proxy allows an attacker to connect to the /proxy-stats endpoint without authentication. The vulnerable endpoint exposes detailed statistics about live connections, along with the capability to modify the logging level of proxied connections without requiring proper authentication credentials.</p> <p>This issue affects Apache Pulsar versions from 2.6.0 to 2.10.5, from 2.11.0 to 2.11.2, from 3.0.0 to 3.0.1, and 3.1.0.</p> <p>The known risks include exposing sensitive information such as connected client IP and unauthorized logging level manipulation which could lead to a denial-of-service condition by significantly increasing the proxy&#39;s logging overhead. When deployed via the Apache Pulsar Helm chart within Kubernetes environments, the actual client IP might not be revealed through the load balancer&#39;s default behavior, which typically obscures the original source IP addresses when externalTrafficPolicy is being configured to &#34;Cluster&#34; by default. The /proxy-stats endpoint contains topic level statistics, however, in the default configuration, the topic level statistics aren&#39;t known to be exposed.</p> <p>2.10 Pulsar Proxy users should upgrade to at least 2.10.6. 2.11 Pulsar Proxy users should upgrade to at least 2.11.3. 3.0 Pulsar Proxy users should upgrade to at least 3.0.2. 3.1 Pulsar Proxy users should upgrade to at least 3.1.1.</p> <p>Users operating versions prior to those listed above should upgrade to the aforementioned patched versions o…</p> <p>Improper Authentication vulnerability in Apache Pulsar Proxy allows an attacker to connect to the /proxy-stats endpoint without authentication. The vulnerable endpoint exposes detailed statistics about live connections, along with the capability to modify the logging level of proxied connections without requiring proper authentication credentials.</p> <p>This issue affects Apache Pulsar versions from 2.6.0 to 2.10.5, from 2.11.0 to 2.11.2, from 3.0.0 to 3.0.1, and 3.1.0.</p> <p>The known risks include exposing sensitive information such as connected client IP and unauthorized logging level manipulation which could lead to a denial-of-service condition by significantly increasing the proxy&#39;s logging overhead. When deployed via the Apache Pulsar Helm chart within Kubernetes environments, the actual client IP might not be revealed through the load balancer&#39;s default behavior, which typically obscures the original source IP addresses when externalTrafficPolicy is being configured to &#34;Cluster&#34; by default. The /proxy-stats endpoint contains topic level statistics, however, in the default configuration, the topic level statistics aren&#39;t known to be exposed.</p> <p>2.10 Pulsar Proxy users should upgrade to at least 2.10.6. 2.11 Pulsar Proxy users should upgrade to at least 2.11.3. 3.0 Pulsar Proxy users should upgrade to at least 3.0.2. 3.1 Pulsar Proxy users should upgrade to at least 3.1.1.</p> <p>Users operating versions prior to those listed above should upgrade to the aforementioned patched versions o…</p> https://cve.radiocsirt.org/vuln/fkie_cve-2022-34321 https://cve.radiocsirt.org/vuln/ghsa-c35h-w8hj-mm55 <p><strong>Affected:</strong> Maven: org.apache.pulsar:pulsar-proxy</p> <p>Improper Authentication vulnerability in Apache Pulsar Proxy allows an attacker to connect to the /proxy-stats endpoint without authentication. The vulnerable endpoint exposes detailed statistics about live connections, along with the capability to modify the logging level of proxied connections without requiring proper authentication credentials.</p> <p>This issue affects Apache Pulsar versions from 2.6.0 to 2.10.5, from 2.11.0 to 2.11.2, from 3.0.0 to 3.0.1, and 3.1.0.</p> <p>The known risks include exposing sensitive information such as connected client IP and unauthorized logging level manipulation which could lead to a denial-of-service condition by significantly increasing the proxy&#39;s logging overhead. When deployed via the Apache Pulsar Helm chart within Kubernetes environments, the actual client IP might not be revealed through the load balancer&#39;s default behavior, which typically obscures the original source IP addresses when externalTrafficPolicy is being configured to &#34;Cluster&#34; by default. The /proxy-stats endpoint contains topic level statistics, however, in the default configuration, the topic level statistics aren&#39;t known to be exposed.</p> <p>2.10 Pulsar Proxy users should upgrade to at least 2.10.6. 2.11 Pulsar Proxy users should upgrade to at least 2.11.3. 3.0 Pulsar Proxy users should upgrade to at least 3.0.2. 3.1 Pulsar Proxy users should upgrade to at least 3.1.1.</p> <p>Users operating versions prior to those listed above should upgrade to the aforementioned patched versions o…</p> <p><strong>Affected:</strong> Maven: org.apache.pulsar:pulsar-proxy</p> <p>Improper Authentication vulnerability in Apache Pulsar Proxy allows an attacker to connect to the /proxy-stats endpoint without authentication. The vulnerable endpoint exposes detailed statistics about live connections, along with the capability to modify the logging level of proxied connections without requiring proper authentication credentials.</p> <p>This issue affects Apache Pulsar versions from 2.6.0 to 2.10.5, from 2.11.0 to 2.11.2, from 3.0.0 to 3.0.1, and 3.1.0.</p> <p>The known risks include exposing sensitive information such as connected client IP and unauthorized logging level manipulation which could lead to a denial-of-service condition by significantly increasing the proxy&#39;s logging overhead. When deployed via the Apache Pulsar Helm chart within Kubernetes environments, the actual client IP might not be revealed through the load balancer&#39;s default behavior, which typically obscures the original source IP addresses when externalTrafficPolicy is being configured to &#34;Cluster&#34; by default. The /proxy-stats endpoint contains topic level statistics, however, in the default configuration, the topic level statistics aren&#39;t known to be exposed.</p> <p>2.10 Pulsar Proxy users should upgrade to at least 2.10.6. 2.11 Pulsar Proxy users should upgrade to at least 2.11.3. 3.0 Pulsar Proxy users should upgrade to at least 3.0.2. 3.1 Pulsar Proxy users should upgrade to at least 3.1.1.</p> <p>Users operating versions prior to those listed above should upgrade to the aforementioned patched versions o…</p> https://cve.radiocsirt.org/vuln/ghsa-c35h-w8hj-mm55 https://cve.radiocsirt.org/vuln/gsd-2022-34321 gsd-2022-34321 https://cve.radiocsirt.org/vuln/gsd-2022-34321 https://cve.radiocsirt.org/vuln/oesa-2026-4329 <p><strong>Affected:</strong> openEuler:24.03-LTS-SP1: pulsar</p> <p>Pulsar is a distributed pub-sub messaging platform with a very flexible messaging model and an intuitive client API. Security Fix(es):</p> <p>Improper Authentication vulnerability in Apache Pulsar Proxy allows an attacker to connect to the /proxy-stats endpoint without authentication. The vulnerable endpoint exposes detailed statistics about live connections, along with the capability to modify the logging level of proxied connections without requiring proper authentication credentials.</p> <p>This issue affects Apache Pulsar versions from 2.6.0 to 2.10.5, from 2.11.0 to 2.11.2, from 3.0.0 to 3.0.1, and 3.1.0.</p> <p>The known risks include exposing sensitive information such as connected client IP and unauthorized logging level manipulation which could lead to a denial-of-service condition by significantly increasing the proxy&amp;apos;s logging overhead. When deployed via the Apache Pulsar Helm chart within Kubernetes environments, the actual client IP might not be revealed through the load balancer&amp;apos;s default behavior, which typically obscures the original source IP addresses when externalTrafficPolicy is being configured to &amp;quot;Cluster&amp;quot; by default. The /proxy-stats endpoint contains topic level statistics, however, in the default configuration, the topic level statistics aren&amp;apos;t known to be exposed.</p> <p>2.10 Pulsar Proxy users should upgrade to at least 2.10.6. 2.11 Pulsar Proxy users should upgrade to at least 2.11.3. 3.0 Pulsar Proxy users should upgrade to at least 3.0.2. 3.…</p> <p><strong>Affected:</strong> openEuler:24.03-LTS-SP1: pulsar</p> <p>Pulsar is a distributed pub-sub messaging platform with a very flexible messaging model and an intuitive client API. Security Fix(es):</p> <p>Improper Authentication vulnerability in Apache Pulsar Proxy allows an attacker to connect to the /proxy-stats endpoint without authentication. The vulnerable endpoint exposes detailed statistics about live connections, along with the capability to modify the logging level of proxied connections without requiring proper authentication credentials.</p> <p>This issue affects Apache Pulsar versions from 2.6.0 to 2.10.5, from 2.11.0 to 2.11.2, from 3.0.0 to 3.0.1, and 3.1.0.</p> <p>The known risks include exposing sensitive information such as connected client IP and unauthorized logging level manipulation which could lead to a denial-of-service condition by significantly increasing the proxy&amp;apos;s logging overhead. When deployed via the Apache Pulsar Helm chart within Kubernetes environments, the actual client IP might not be revealed through the load balancer&amp;apos;s default behavior, which typically obscures the original source IP addresses when externalTrafficPolicy is being configured to &amp;quot;Cluster&amp;quot; by default. The /proxy-stats endpoint contains topic level statistics, however, in the default configuration, the topic level statistics aren&amp;apos;t known to be exposed.</p> <p>2.10 Pulsar Proxy users should upgrade to at least 2.10.6. 2.11 Pulsar Proxy users should upgrade to at least 2.11.3. 3.0 Pulsar Proxy users should upgrade to at least 3.0.2. 3.…</p> https://cve.radiocsirt.org/vuln/oesa-2026-4329