A flaw has been found in the way elinks parses smb:// protocol URLs: http://marc.theaimsgroup.com/?l=full-disclosure&m=116355556512780&w=2 This flaw could allow a remote web page to read and write arbitrary files with the permissions of the user running elinks.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2006-0742.html
Hi, I'm looking into fixing this for Fedora Legacy (FC3 & FC4), and I'm curious about the patch used for EL4. Why was the smb protocol disabled completely in configure.in instead of patching smb.c? Was fixing smb.c just too messy? Is it assumed that nobody uses elinks for smb protocol? Thanks for any input.
Maybe more sensitive way is disable only smb commands (smbclient -c), but I think number of users who use smb by elinks is really very small and we also doesn't support this feature in RHEL2.1, RHEL3 and RHEL5 (FC6). So ... It seems it's better disable this dangerous feature at all.
OK, that's what I figured. Thanks for the clarification.
I have added this to the ELinks Bugzilla: http://bugzilla.elinks.cz/show_bug.cgi?id=841