• This thread is just the tip of the iceberg.The people ahead of the curve aren't Googling for answers — they're already in here, having the conversations you haven't found yet. DealerRefresh is free.Get the full picture →
I don't think DealerBuilt was targeted in this at all. This appears to just be negligence on the backup and transfer of the data. Regardless of who found the it, we should be glad it was exposed and is now fixed. People look for vulnerabilities like this all the time.
 
  • Like
Reactions: craigh
I don't think DealerBuilt was targeted in this at all. This appears to just be negligence on the backup and transfer of the data. Regardless of who found the it, we should be glad it was exposed and is now fixed. People look for vulnerabilities like this all the time.

This is exactly how this works.
Servers are automatically scanned and tested for things like this.
They were transferring insecure backups over the default rsync ports between servers.
They didn't make it difficult to find - I've got dozens of servers and those ports get pried at and poked at 100 times a day.
 

✨ AI Highlights

Forum members debate whether a reported data breach at DealerBuilt DMS is legitimate, with initial skepticism giving way to evidence that the breach likely occurred based on technical details and customer confirmation. Key concerns include DealerBuilt's complete lack of public communication about the incident and the automotive press's failure to cover the story despite heightened industry focus on data security. The thread underscores the importance of dealers thoroughly vetting their software vendors' security practices and understanding potential liability exposure.

Replies Views 15 13,295 Started Last Reply