20

This chat message is an example of the bug. It looks like this in regular chat:

"Here's the essay: Tropes, Facts and Empiricism by Daryn Lehoux"

That link points to:

http://web.archive.org/web/20080409050311/http://personalpages.manchester.ac.uk/staff/daryn.lehoux/Tropes.pdf

In the transcript, it looks like this:

"Here's the essay: {a plaintext URL with some broken HTML} Tropes, Facts and Empiricism by Daryn Lehoux"

That link points to:

http://web.archive.org/web/20080409050311/%3Ca%20href=

... which doesn't work so well! Could this be fixed? I'm not sure if this impacts links to elsewhere.

  • 1
    Looks like the double http:// is the culprit, not sure it's a valid URL. If it's invalid URL I'd say this is by design, and the bug in in the web archive site itself generating invalid links. (Which might be working only due to merciful browsers not enforcing URL rules) – ShaWiz Jan 14 '15 at 7:28
  • 4
    @ShadowWizard: the URL is kind-off valid; colons are reserved characters and should be represented by %3A instead, but in practice browsers just support the unescaped colon in the path section of a URL. Which is why regular chat supports Wayback Engine urls, and the transcript should just be fixed. – Martijn Pieters Jan 14 '15 at 8:27
  • It would be good to get some come-back on this. Wayback Machine links are often used to fix link-rot, and if they are rendered "in-chat" correctly, it is passing strange that they are rendered "in-transcript" incorrectly. – Dɑvïd Aug 30 '15 at 16:12
  • 1
    @Davïd You have more than enough rep to place a bounty, rather than pointless edits to bump a question. It also wouldn't be so bad if you had 2k and not shoved this into the review queue. You are essentially asking reviewers to authorise a bump, not a useful edit. See here: meta.stackexchange.com/a/4409/230506 :) – James Aug 30 '15 at 18:44
  • Thanks for suggestions, @James - bounty never occurred to me (obviously), but could do, I suppose. And I am a <2K user here, so edits (ok, not the most meaningful, but I think it is "better"!) were my recourse. Will know better next time! – Dɑvïd Aug 30 '15 at 19:22
  • The bug is still there. – vaultah Dec 20 '15 at 7:49
  • 1
    Starboards are affected too. – vaultah Dec 20 '15 at 8:02
8
+50

I'm not sure if this impacts links to elsewhere.

Yeah, it does. In fact this bug could be used to exploit an XSS vulnerability :(

Thanks to Gothdo for responsibly disclosing the vulnerability to us, and thanks to ArtOfCode for putting a bounty on this question – I wouldn't be surprised if the bounty was what made Gothdo aware of the issue :)

And of course thanks to you for writing this in the first place.

It's fixed now.

  • 1
    Also thanks to Ferrybig for helping to work the bug out with Gothdo. – ArtOfCode May 12 '16 at 7:48
  • 2
    I made Gothdo aware of it because he passed by while I was trying to exploid it... chat.stackoverflow.com/rooms/111569/xss-test – Ferrybig May 12 '16 at 7:49
  • 1
    Note to self: to have a bug fixed, find how it can be exploited... – ShaWiz May 12 '16 at 8:59
  • There were 2 bounties... :( Anyway, great to see it fixed, especially knowing it was a vulnerability. Cheers Balpha. – vaultah Jun 19 '16 at 20:53

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .