An issue in MongoDB Server could allow an authenticated user with direct network access to a shard to improperly commit or abort an in-progress prepared transaction, bypassing the intended transaction coordination process. This could result in cross-shard data inconsistency, cluster clock corruption, and violation of transaction atomicity guarantees.
{
"binaries": [
{
"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",
"binary_version": "1:3.6.3-0ubuntu1.4+esm2"
}
]
}
{
"binaries": [
{
"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",
"binary_version": "1:3.6.9+really3.6.8+90~g8e540c0b6d-0ubuntu5.3+esm1"
}
]
}