An authenticated user holding cursor termination privileges on one database may incorrectly be permitted to terminate active cursors on a separate database, disrupting ongoing query operations for other users. The behavior stems from an authorization check that does not correctly scope privileges to the appropriate namespace.
{
"binaries": [
{
"binary_version": "1:3.6.3-0ubuntu1.4+esm2",
"binary_name": "mongodb"
},
{
"binary_version": "1:3.6.3-0ubuntu1.4+esm2",
"binary_name": "mongodb-clients"
},
{
"binary_version": "1:3.6.3-0ubuntu1.4+esm2",
"binary_name": "mongodb-server"
},
{
"binary_version": "1:3.6.3-0ubuntu1.4+esm2",
"binary_name": "mongodb-server-core"
}
]
}
{
"binaries": [
{
"binary_version": "1:3.6.9+really3.6.8+90~g8e540c0b6d-0ubuntu5.3+esm1",
"binary_name": "mongodb"
},
{
"binary_version": "1:3.6.9+really3.6.8+90~g8e540c0b6d-0ubuntu5.3+esm1",
"binary_name": "mongodb-clients"
},
{
"binary_version": "1:3.6.9+really3.6.8+90~g8e540c0b6d-0ubuntu5.3+esm1",
"binary_name": "mongodb-server"
},
{
"binary_version": "1:3.6.9+really3.6.8+90~g8e540c0b6d-0ubuntu5.3+esm1",
"binary_name": "mongodb-server-core"
}
]
}