Kea configuration and API directives can be used to load a malicious hook library. Many common configurations run Kea as root, leave the API entry points unsecured by default, and/or place the control sockets in insecure paths. This issue affects Kea versions 2.4.0 through 2.4.1, 2.6.0 through 2.6.2, and 2.7.0 through 2.7.8.
{
"binaries": [
{
"binary_name": "kea",
"binary_version": "2.4.1-3ubuntu0.1"
},
{
"binary_name": "kea-admin",
"binary_version": "2.4.1-3ubuntu0.1"
},
{
"binary_name": "kea-common",
"binary_version": "2.4.1-3ubuntu0.1"
},
{
"binary_name": "kea-ctrl-agent",
"binary_version": "2.4.1-3ubuntu0.1"
},
{
"binary_name": "kea-dev",
"binary_version": "2.4.1-3ubuntu0.1"
},
{
"binary_name": "kea-dhcp-ddns-server",
"binary_version": "2.4.1-3ubuntu0.1"
},
{
"binary_name": "kea-dhcp4-server",
"binary_version": "2.4.1-3ubuntu0.1"
},
{
"binary_name": "kea-dhcp6-server",
"binary_version": "2.4.1-3ubuntu0.1"
},
{
"binary_name": "python3-kea-connector",
"binary_version": "2.4.1-3ubuntu0.1"
}
]
}