It was discovered that libapreq2 did not properly sanitize the Content-Type field in certain crafted HTTP requests. An attacker could possibly use the vulnerability to cause libapreq2 to crash.
{
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_version": "2.13-3ubuntu2+esm1",
"binary_name": "libapache2-mod-apreq2"
},
{
"binary_version": "2.13-3ubuntu2+esm1",
"binary_name": "libapache2-request-perl"
},
{
"binary_version": "2.13-3ubuntu2+esm1",
"binary_name": "libapreq2-3"
},
{
"binary_version": "2.13-3ubuntu2+esm1",
"binary_name": "libapreq2-dev"
}
]
}
{
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_version": "2.13-4ubuntu2+esm1",
"binary_name": "libapache2-mod-apreq2"
},
{
"binary_version": "2.13-4ubuntu2+esm1",
"binary_name": "libapache2-request-perl"
},
{
"binary_version": "2.13-4ubuntu2+esm1",
"binary_name": "libapreq2-3"
},
{
"binary_version": "2.13-4ubuntu2+esm1",
"binary_name": "libapreq2-dev"
}
]
}