FreshPorts - VuXML

This page displays vulnerability information about FreeBSD Ports.

The VUXML data was last processed by FreshPorts on 2024-11-23 17:01:17 UTC

List all Vulnerabilities, by package

List all Vulnerabilities, by date

k68

These are the vulnerabilities relating to the commit you have selected:

VuXML ID	Description
af61b271-9e47-4db0-a0f6-29fb032236a3	zookeeper -- Denial Of Service zookeeper developers report: Two four letter word commands "wchp/wchc" are CPU intensive and could cause spike of CPU utilization on Apache ZooKeeper server if abused, which leads to the server unable to serve legitimate client requests. Apache ZooKeeper thru version 3.4.9 and 3.5.2 suffer from this issue, fixed in 3.4.10, 3.5.3, and later. Discovery 2017-10-09 Entry 2017-10-10 zookeeper < 3.4.10 https://lists.apache.org/thread.html/58170aeb7a681d462b7fa31cae81110cbb749d2dc83c5736a0bb8370@%3Cdev.zookeeper.apache.org%3E CVE-2017-5637
2bc376c0-977e-11ee-b4bc-b42e991fc52e	apache -- Apache ZooKeeper: Authorization bypass in SASL Quorum Peer Authentication security@apache.org reports: Authorization Bypass Through User-Controlled Key vulnerability in Apache ZooKeeper. If SASL Quorum Peer authentication is enabled in ZooKeeper (quorum.auth.enableSasl=true), the authorization is done by verifying that the instance part in SASL authentication ID is listed in zoo.cfg server list. The instance part in SASL auth ID is optional and if it's missing, like 'eve@EXAMPLE.COM', the authorization check will be skipped.As a result an arbitrary endpoint could join the cluster and begin propagating counterfeit changes to the leader, essentially giving it complete read-write access to the data tree.Quorum Peer authentication is not enabled by default. Users are recommended to upgrade to version 3.9.1, 3.8.3, 3.7.2, which fixes the issue. Alternately ensure the ensemble election/quorum communication is protected by a firewall as this will mitigate the issue. See the documentation for more details on correct cluster administration. Discovery 2023-10-11 Entry 2023-12-10 zookeeper < 3.7.2 >= 3.8.0 lt 3.8.3 >= 3.9.0 lt 3.9.1 CVE-2023-44981 https://nvd.nist.gov/vuln/detail/CVE-2023-44981

VuXML ID

Description

af61b271-9e47-4db0-a0f6-29fb032236a3

zookeeper -- Denial Of Service

zookeeper developers report:

Two four letter word commands "wchp/wchc" are CPU intensive and could cause spike of CPU utilization on Apache ZooKeeper server if abused, which leads to the server unable to serve legitimate client requests. Apache ZooKeeper thru version 3.4.9 and 3.5.2 suffer from this issue, fixed in 3.4.10, 3.5.3, and later.

Discovery 2017-10-09
Entry 2017-10-10
zookeeper

< 3.4.10

https://lists.apache.org/thread.html/58170aeb7a681d462b7fa31cae81110cbb749d2dc83c5736a0bb8370@%3Cdev.zookeeper.apache.org%3E
CVE-2017-5637

2bc376c0-977e-11ee-b4bc-b42e991fc52e

apache -- Apache ZooKeeper: Authorization bypass in SASL Quorum Peer Authentication

security@apache.org reports:

Authorization Bypass Through User-Controlled Key vulnerability in Apache ZooKeeper. If SASL Quorum Peer authentication is enabled in ZooKeeper (quorum.auth.enableSasl=true), the authorization is done by verifying that the instance part in SASL authentication ID is listed in zoo.cfg server list. The instance part in SASL auth ID is optional and if it's missing, like 'eve@EXAMPLE.COM', the authorization check will be skipped.As a result an arbitrary endpoint could join the cluster and begin propagating counterfeit changes to the leader, essentially giving it complete read-write access to the data tree.Quorum Peer authentication is not enabled by default. Users are recommended to upgrade to version 3.9.1, 3.8.3, 3.7.2, which fixes the issue. Alternately ensure the ensemble election/quorum communication is protected by a firewall as this will mitigate the issue. See the documentation for more details on correct cluster administration.

Discovery 2023-10-11
Entry 2023-12-10
zookeeper

< 3.7.2

>= 3.8.0 lt 3.8.3

>= 3.9.0 lt 3.9.1

CVE-2023-44981
https://nvd.nist.gov/vuln/detail/CVE-2023-44981