| Package | Affected versions | Patched versions |
|---|---|---|
| bbot | ≥ 2.3.1, < 3.0.0 | 3.0.0 |
| bbot | = 3.0.0.0= 3.0.0.1056= 3.0.0.1062= 3.0.0.1064= 3.0.0.1068= 3.0.0.1070= 3.0.0.1079= 3.0.0.1137= 3.0.0.1139= 3.0.0.1141= 3.0.0.1153= 3.0.0.1173= 3.0.0.1184= 3.0.0.1190= 3.0.0.1254= 3.0.0.1271= 3.0.0.1274= 3.0.0.1304= 3.0.0.1313= 3.0.0.1317= 3.0.0.1333= 3.0.0.1343= 3.0.0.1345= 3.0.0.1349= 3.0.0.1386= 3.0.0.1388= 3.0.0.1390= 3.0.0.1401= 3.0.0.1407= 3.0.0.647= 3.0.0.649= 3.0.0.652= 3.0.0.654= 3.0.0.659= 3.0.0.669= 3.0.0.671= 3.0.0.673= 3.0.0.691= 3.0.0.765= 3.0.0.767= 3.0.0.773= 3.0.0.782= 3.0.0.786= 3.0.0.793= 3.0.0.795= 3.0.0.798= 3.0.0.819= 3.0.0.821= 3.0.0.829= 3.0.0.836= 3.0.0.849= 3.0.0.851= 3.0.0.858= 3.0.0.870= 3.0.0.876= 3.0.0.884= 3.0.0.897= 3.0.0.903= 3.0.0.907= 3.0.0.909= 3.0.0.981= 3.0.0.986≥ 2.3.1, ≤ 2.8.6 |
BBOT's unarchive module rejects archives containing symlink entries before extraction, but for zip and 7z archives it failed to detect symlinks whose listing carries a DOS-attribute prefix before the unix mode, as produced by legacy versions of p7zip. Such an archive, downloaded and extracted during a scan (for example via filedownload), bypassed the guard and caused an attacker-controlled symlink to be written into the extraction directory. The effect is limited to planting the symlink (its target is not written through), and only hosts using such a legacy p7zip build are affected; current mainline 7-Zip is not.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free