4 ms·

Yes, it's a Redis vulnerability (caused by bad config on our part) in one container where the firewall was down. Strange thing if we run 'top' from the main ho

by gopi_ar 10y ago

Yes, it's a Redis vulnerability (caused by bad config on our part) in one container where the firewall was down. Strange thing if we run 'top' from the main host, all containers running redis say 'statd' as their user; inside the container the user showed 'redis'. We removed nfs and all related files, and now it shows a user ID number. Is this something we should worry about?

alexginzburg 10y ago
Could you elaborate what redis configuration could've caused this?
- edifus 10y ago
  http://antirez.com/news/96 http://antirez.com/news/96
- gopi_ar 10y ago
  Here you go: https://kevinchen.co/blog/postmortem-server-compromised/ https://kevinchen.co/blog/postmortem-server-compromised/
- eminkel 10y ago
  FYI: Default redis install has since fixed this vulnerability.