News for hackers. Stuff that matters.
Re:Apache Struts Statement on Equifax Security Breach by matchagaucho on Saturday September 09, 2017 @03:22PM (#15208728)
> It's quite trivial to go from here to execution of arbitrary code.

Code that does what? Dumps all environment vars? OK, maybe that produces a DB2 connection string. Refactor code, re-inject, does the connection work? OK. Refactor code, re-inject and dump all tables. etc...

This attack requires an iterative trial-and-error probing process, typically done behind a proxy for many weeks/months.

From Equifax's PR: "the unauthorized access occurred from mid-May through July 2017.".

That's a reasonable amount of time to probe all systems involved and develop sophisticated code.

Re:Apache Struts Statement on Equifax Security Breach by sasas on Saturday September 09, 2017 @08:17PM (#15209794)
The vulnerabilities have public proof of concept code. You literally get a shell on the machine. I wont link examples here, but they are east to find.
Re:Apache Struts Statement on Equifax Security Breach by solomatov on Saturday September 09, 2017 @03:31PM (#15208771)
>This attack requires an iterative trial-and-error probing process, typically done behind a proxy for many weeks/months.

Of course this attack is quite laborious, but it doesn't require anything special or unique.

Re:Apache Struts Statement on Equifax Security Breach by tetha on Saturday September 09, 2017 @04:04PM (#15208916)
It requires human effort.

For most attackers, it is vastly more efficient to run automated sql/wordpress-vuln/ssh-user scanners dropping bitcoin miners and botnet nodes. Those require zero human effort and self-replicate. That gives you less publicity than a hundred million personal finance records, but it has a much higher success chance and a more reliable income.