Advertisement
Guest User

Untitled

a guest
Aug 31st, 2011
36,609
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.12 KB | None | 0 0
  1. ---------- Forwarded message ----------
  2. From: J.H. <[email protected]>
  3. Date: 2011/8/29
  4. Subject: [kernel.org users] [KORG] Master back-end break-in
  5.  
  6.  
  7. -----BEGIN PGP SIGNED MESSAGE-----
  8. Hash: SHA1
  9.  
  10. Afternoon Everyone,
  11.  
  12. As you can guess from the subject line, I've not had what many would
  13. consider a "good" day. Earlier today discovered a trojan existing on
  14. HPA's personal colo machine, as well as hera. Upon some investigation
  15. there are a couple of kernel.org boxes, specifically hera and odin1,
  16. with potential pre-cursors on demeter2, zeus1 and zeus2, that have been
  17. hit by this.
  18.  
  19. As it stands right now, HPA is working on cleaning his box, and
  20. I'm working on hera (odin1 and zeus1 are out of rotation still for other
  21. reasons), mainly so that if one of us finds something of interest, we
  22. can deal with it and compare notes on the other box.
  23.  
  24. Points of interest:
  25.  
  26. - - Break-in seems to have initially occurred no later than August 12th
  27.  
  28. - - Files belonging to ssh (openssh, openssh-server and openssh-clients)
  29. were modified and running live. These have been uninstalled and
  30. removed, all processes were killed and known good copies were
  31. reinstalled. That said all users may wish to consider taking this
  32. opportunity to change their passwords and update ssh keys (particularly
  33. if you had an ssh private key on hera). This seems to have occurred on
  34. or around August 19th.
  35.  
  36. - - A trojan startup file was added to rc3.d
  37.  
  38. - - User interactions were logged, as well as some exploit code. We have
  39. retained this for now.
  40.  
  41. - - Trojan initially discovered due to the Xnest /dev/mem error message
  42. w/o Xnest installed; have been seen on other systems. It is unclear if
  43. systems that exhibit this message are susceptible, compromised or not.
  44. If you see this, and you don't have Xnest installed, please investigate.
  45.  
  46. - - It *appears* that 3.1-rc2 might have blocked the exploit injector, we
  47. don't know if this is intentional or a side affect of another bugfix or
  48. change.
  49.  
  50. - - System is being verified from backups, signatures, etc. As of right
  51. now things look correct, however we may take the system down soon to do
  52. a full reinstall and for more invasive checking.
  53.  
  54. - - As a precaution a number of packages have been removed from the
  55. system, if something was removed that you were using please let us know
  56. so we can put it back.
  57.  
  58. - - At this time we do not know the vector that was used to get into the
  59. systems, but the attackers had gained root access level privileges.
  60.  
  61. That's what we know right now, some of the recent instabilities may have
  62. been caused by these intrusions, and we are looking into everything.
  63.  
  64. If you are on the box, keep an eye out, and if you see something please
  65. let us know immediately.
  66.  
  67. Beyond that, verify your git trees and make sure things are correct.
  68.  
  69. - - John 'Warthog9' Hawley
  70. Chief Kernel.org Administrator
  71. -----BEGIN PGP SIGNATURE-----
  72. Version: GnuPG v1.4.11 (GNU/Linux)
  73. Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
  74.  
  75. iEYEARECAAYFAk5a5U0ACgkQ/E3kyWU9dif+1ACfYPlgq/keFrFO77AmQVduKGwx
  76. TAcAnRAu6nHt74+5aC+fPeb8aT0hcy2K
  77. =Semd
  78. -----END PGP SIGNATURE-----
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement