Advertisement
Guest User

Untitled

a guest
Sep 10th, 2011
863
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.02 KB | None | 0 0
  1. -----BEGIN PGP SIGNED MESSAGE-----
  2. Hash: SHA256
  3.  
  4. On September 3, an attacker used a 0-day exploit in SMF to gain administrative access to the forum. This went unnoticed until September 9, when he inserted some annoying JavaScript into all pages. The forum was at this point shut down.
  5.  
  6. The attacker was capable of running arbitrary PHP code, and he could have therefore copied all password hashes and read all personal messages. He also could have done all of the things that admins can normally do, such as editing/deleting/moving posts.
  7.  
  8. Passwords
  9.  
  10. It is not known for sure that the attacker copied any password hashes, but it should be assumed that he did.
  11.  
  12. SMF hashes passwords with SHA-1 and salts the hash with your (lowercase) username. This is unfortunately not an incredibly secure way of hashing passwords.
  13.  
  14. The password you used on the forum should be assumed to already be compromised if your password had:
  15. - - Less than 16 characters, numbers only
  16. - - Less than 12 characters, lowercase only
  17. - - Less than 11 characters, lowercase+numeric
  18. - - Less than 10 characters, lowercase+uppercase
  19. - - Less than 9 characters, lowercase+uppercase+numbers
  20. - - Less than 8 characters, all standard characters
  21.  
  22. If you have only 2-3 more characters than what I listed above, then you should assume that your password will be compromised at some point in the future.
  23.  
  24. No matter how strong your password was, it is a good idea to change your password here and wherever else you used it.
  25.  
  26. Database state
  27.  
  28. Backups exist of the previous database state, but it has been decided to continue with the latest state to avoid losing thousands of posts. If you notice that any posts are missing or changed, let me know.
  29.  
  30. Also, it's possible that the attacker took control of some accounts. If you are being impersonated, email me and I'll reset your password to its previous value.
  31.  
  32. More attack info
  33.  
  34. The attacker first paid for a donator account so he could change his displayed username. The displayed username field is not escaped properly, so he was able to inject SQL from there. He took over Satoshi's account, and from Satoshi's administrative interface he was able to inject arbitrary PHP code by modifying the style template.
  35.  
  36. The attacker probably used these user accounts, though his level of access would allow him to forge this data:
  37. brad
  38. EconomicOracle
  39. Economic Oracle
  40. SwimsuitPaul
  41. BitcoinsInMyLoins
  42.  
  43. He probably used these IP addresses:
  44. 74.242.208.159
  45. 74.242.205.69
  46. 152.14.219.223
  47. 152.14.247.62
  48. 74.242.205.161
  49. 74.242.206.245
  50. 74.242.208.159
  51. 74.242.235.132
  52. 98.69.157.69
  53. 98.69.160.187
  54. 41.125.48.26
  55. 150.206.212.72
  56.  
  57. (Thanks to Mark Karpeles for finding most of this info.)
  58.  
  59. Change of hosting
  60.  
  61. Mark Karpeles is now hosting the forum's server. The forum is still owned by Sirius, as it has always been. There will be no policy changes.
  62. -----BEGIN PGP SIGNATURE-----
  63.  
  64. iF4EAREIAAYFAk5sOu8ACgkQxlVWk9q1kecpeQD+Ok4b8vWzyy8SCBUYCysgxR+5
  65. UFWdF/JQhRTzR9bKEZoA+gJcvye7Im5+KQ+QU05MjQ8NtasqlGMwMUhuC+xk3o65
  66. =zHzG
  67. -----END PGP SIGNATURE-----
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement