A flaw was found in Mercurial before 4.9. It was possible to use symlinks and subrepositories to defeat Mercurial's path-checking logic and write files outside a repository.
{ "availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro", "binaries": [ { "binary_name": "mercurial", "binary_version": "2.8.2-1ubuntu1.4+esm1" }, { "binary_name": "mercurial-common", "binary_version": "2.8.2-1ubuntu1.4+esm1" }, { "binary_name": "mercurial-dbgsym", "binary_version": "2.8.2-1ubuntu1.4+esm1" } ] }
{ "availability": "Available with Ubuntu Pro: https://ubuntu.com/pro", "binaries": [ { "binary_name": "mercurial", "binary_version": "3.7.3-1ubuntu1.2+esm2" }, { "binary_name": "mercurial-common", "binary_version": "3.7.3-1ubuntu1.2+esm2" }, { "binary_name": "mercurial-dbgsym", "binary_version": "3.7.3-1ubuntu1.2+esm2" } ] }
{ "availability": "No subscription required", "binaries": [ { "binary_name": "mercurial", "binary_version": "4.5.3-1ubuntu2.2" }, { "binary_name": "mercurial-common", "binary_version": "4.5.3-1ubuntu2.2" }, { "binary_name": "mercurial-dbgsym", "binary_version": "4.5.3-1ubuntu2.2" } ] }
{ "availability": "Available with Ubuntu Pro: https://ubuntu.com/pro", "binaries": [ { "binary_name": "mercurial", "binary_version": "4.5.3-1ubuntu2.2" }, { "binary_name": "mercurial-common", "binary_version": "4.5.3-1ubuntu2.2" }, { "binary_name": "mercurial-dbgsym", "binary_version": "4.5.3-1ubuntu2.2" } ] }