4 ms·

So the plan is leave this vector open (as it was never found) and just try to secure the file system a bit more... Surly that could leave the same vector open

• drone 14y ago
  There's a good chance that if it's not a previously known vector, they've contact the author of the component with some opportunity to fix it before it's publicized and resulting in attacks from new parties.* * I neither agree nor disagree with zero-day disclosure policies. I'm just noting the possibility that they could be aware of the vector and would rather not share that information yet, for various reasons.
  • dangrossman 14y ago
    If they knew the source of the attack and closed the hole, they'd want to have said so. They don't need to say what the hole is or how they closed it to do that much.
• ZoFreX 14y ago
  Would it be so hard to use a journalling filesystem, snapshot backups, or even throw the site folders into git (not the binary files, obviously!) - then you could view all changes made to the code recently, look for changes in common between the sites, and look for changes only within .php files, outside of times the site was being upgraded by the customer or host?