w3m through 0.5.3 does not properly handle temporary files when the ~/.w3m directory is unwritable, which allows a local attacker to craft a symlink attack to overwrite arbitrary files.
{ "availability": "No subscription required", "ubuntu_priority": "low", "binaries": [ { "binary_version": "0.5.3-15ubuntu0.2", "binary_name": "w3m" }, { "binary_version": "0.5.3-15ubuntu0.2", "binary_name": "w3m-dbgsym" }, { "binary_version": "0.5.3-15ubuntu0.2", "binary_name": "w3m-img" }, { "binary_version": "0.5.3-15ubuntu0.2", "binary_name": "w3m-img-dbgsym" } ] }
{ "availability": "No subscription required", "ubuntu_priority": "low", "binaries": [ { "binary_version": "0.5.3-26ubuntu0.2", "binary_name": "w3m" }, { "binary_version": "0.5.3-26ubuntu0.2", "binary_name": "w3m-dbgsym" }, { "binary_version": "0.5.3-26ubuntu0.2", "binary_name": "w3m-img" }, { "binary_version": "0.5.3-26ubuntu0.2", "binary_name": "w3m-img-dbgsym" } ] }