Pastebin launched a little side project called VERYVIRAL.com, check it out ;-) Want more features on Pastebin? Sign Up, it's FREE!
Guest

Firefox security bug (proxy-bypass) in current TBBs

By: a guest on May 2nd, 2012  |  syntax: None  |  size: 4.26 KB  |  views: 879  |  expires: Never
download  |  raw  |  embed  |  report abuse  |  print
Text below is selected. Please press Ctrl+C to copy to your clipboard. (⌘+C on Mac)
  1. Firefox security bug (proxy-bypass) in current TBBs
  2.  
  3. https://blog.torproject.org/blog/firefox-security-bug-proxy-bypass-current-tbbs
  4.  
  5. "A user has discovered a severe security bug in Firefox related to websockets bypassing the SOCKS proxy DNS configuration. This means when connecting to a websocket service, your Firefox will query your local DNS resolver, rather than only communicating through its proxy (Tor) as it is configured to do. This bug is present in current Tor Browser Bundles (2.2.35-9 on Windows; 2.2.35-10 on MacOS and Linux).
  6.  
  7. To fix this dns leak/security hole, follow these steps:
  8.  
  9.     Type “about:config” (without the quotes) into the Firefox URL bar. Press Enter.
  10.     Type “websocket” (again, without the quotes) into the search bar that appears below "about:config".
  11.     Double-click on “network.websocket.enabled”. That line should now show “false” in the ‘Value’ column.
  12.  
  13. See Tor bug 5741 for more details.
  14. (https://bugs.torproject.org/5741)
  15. We are currently working on new bundles with a better fix."
  16. ----------------------------
  17. Anonymous comments:
  18. ----------------------------
  19. On May 2nd, 2012 Anonymous said:
  20.  
  21. Oh dear :(
  22.  
  23. Does anyone know if IP addresses leaked to Twitter when (through NoScript) I enabled javascript for that site?
  24.  
  25. If yes, I may be in trouble.
  26. ----------------------------
  27. On May 2nd, 2012 Anonymous said:
  28.  
  29. @anon, AFAIK Twitter does not use web sockets, so even if you enabled Javascript on Twitter it should not be an issue. I could be wrong or there could be other issues.
  30. ----------------------------
  31. On May 2nd, 2012 Anonymous said:
  32.  
  33. Theoretically, an exit node can embed a websocket into your traffic stream if you are using HTTP.
  34. ----------------------------
  35. On May 2nd, 2012 Anonymous said:
  36.  
  37. As long as you weren't doing anything illegal in the United States you should be fine. Tor has never been about hiding illegal activity. And since Twitter is in the US and doesn't respond to foreign court orders… well…
  38. ----------------------------
  39. On May 2nd, 2012 Anonymous said:
  40.  
  41. Ah right, maybe Anonymous "Oh dear" is a fucking communist, or even a dirty whistle blower like Maning! Brave, law abide citizens haven't got anything, that must be hidden, so maybe you want to forbid TOR, Mr. McCarthy?
  42. ----------------------------
  43. On May 2nd, 2012 Anonymous said:
  44.  
  45. Oh great, so all my Pastebins are belong to the Feds?
  46. ----------------------------
  47.  
  48. THE DRAMA CONTINUES...
  49.  
  50. TBB proxy bypass: Some DNS requests not going through Tor
  51. Ticket #5741 (closed defect: fixed)
  52. https://trac.torproject.org/projects/tor/ticket/5741
  53.  
  54. "This is not the first time some rarely triggered bug in Firefox causes Tor to be bypassed, and certainly will not be the last one. Since these bugs have a very high security impact I propose they are guarded against. How about running Firefox inside some kind of firewall that drops all network packets not going to Tor?"
  55. ----------------------------
  56. Comments:
  57. ----------------------------
  58. by mikeperry
  59.  
  60. Good catch Robert. Disabling about:config pref network.websocket.enabled prevents it from happening for me... I'm now grepping through the Firefox WebSocket code looking for the issue..
  61.  
  62. ----------------------------
  63. by mikeperry
  64.  
  65. This is fixed and pushed to all TBB branches. I fixed it by blocking all DNS requests while socks_remote_dns is enabled, so we don't end up with this showing up in new components in the future.
  66.  
  67. Interested folks can review the patch here:  https://gitweb.torproject.org/torbrowser.git/blob/maint-2.2:/src/current-patches/firefox/0018-Prevent-WebSocket-DNS-leak.patch
  68. ----------------------------
  69. Additional Reference:
  70.  
  71. [tor-talk] Firefox security bug (proxy-bypass) in current TBBs
  72.  
  73. Robert Ransom rransom.8774 at gmail.com
  74. Wed May 2 22:43:52 UTC 2012
  75.  
  76. See https://blog.torproject.org/blog/firefox-security-bug-proxy-bypass-current-tbbs
  77. for the security advisory.
  78.  
  79. Robert Ransom
  80.  
  81. https://lists.torproject.org/pipermail/tor-talk/2012-May/024123.html
  82. ----------------------------
  83. Another version of TBB, another bug. IMO, they should mark all releases of TBB as ALPHA!
  84.  
  85. At the time of this bug report collection and passing the news onto others, there have not been any new release of TBB versions to fix this bug on their download pages, but it'll come.