It was discovered that libapreq2 did not properly sanitize the Content-Type field in certain, crafted HTTP requests. An attacker could use this vulnerability to cause libapreq2 to crash.
{
"availability": "No subscription required",
"binaries": [
{
"binary_version": "2.13-7~deb10u1build0.18.04.1",
"binary_name": "libapache2-mod-apreq2"
},
{
"binary_version": "2.13-7~deb10u1build0.18.04.1",
"binary_name": "libapache2-request-perl"
},
{
"binary_version": "2.13-7~deb10u1build0.18.04.1",
"binary_name": "libapreq2-3"
},
{
"binary_version": "2.13-7~deb10u1build0.18.04.1",
"binary_name": "libapreq2-dev"
}
]
}