[Tickets #5892] Re: Linked attachment feature vulnerability

[bugs at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=5892
-----------------------------------------------------------------------
 Ticket             | 5892
 Updated By         | joao_mauricio at clix.pt
 Summary            | Linked attachment feature vulnerability
 Queue              | IMP
 Version            | HEAD
 Type               | Bug
 State              | Feedback
 Priority           | 2. Medium
 Owners             | 
-----------------------------------------------------------------------


joao_mauricio at clix.pt (2007-11-17 09:54) wrote:

Well... now i've realized that the solution i mentioned earlier isn't
possible too, cause: first the script retrives the file and next the jar:
protocol acts. So.. I think that a good solution is to put a secure id in
the attachment's URL, for each rcpt of the attachment. That way, no one
(except the rcpt) would know the path to the file and the XSS attack won't
be possible.