Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
although it appears Equifax is claiming an older CVE struts issue (not patched) for the cause of their breach, Struts dev folks better start explaining cve-2017-9805 and the claims moving around the net that this vuln has been in Struts for past ~9yrs.
Shouldn't you post some SOURCE for those supposed claims?
If the vulnerability has been around (and known) for 9 years shouldn't someone be able to point to an old post that talks about it?
An entity like Equifax relying on FOSS without doing their own due diligence for software they implement can hardly blame the FOSS maker (especially if they're not paying for support). Equifax ought to be able to point to the exact vulnerability and lack of patch before they do this. In my view Equifax is just trying to avoid responsibility by casting aspersions on others.
Interesting to me is that after the reported hack I was able to freeze my credit on TransUnion and Experian online but Equifax told me I'd have to send them snail mail. Equifax should have immediately put all accounts on credit freeze once they discovered the hack. Instead they put up a thing that you have to agree NOT to sue them before they'll even tell you if you were affected.
Ex-Governor Roy Barnes has already announced a class action lawsuit against Equifax and based on what Equifax has done so far I'm apt to cheer him on:
-Had the hack May.
-Learned about it in July.
-Announced it just now in September.
-Trying to scare you into signing away your right to hold them accountable just to be told whether you were affected.
-Requiring snail mail to freeze your account.
Last edited by MensaWater; 09-14-2017 at 03:44 PM.
i would not do anything with Equifax now, doing so will remove some of your rights, which is being challenged.
i also cannot ascertain if existing PIN numbers were breached. and from the info i have now you cannot change the PIN via phone or online, and snail mail will take weeks, possibly months. Equifax are such tards, the PIN # system is trivial !! they just recently changed it to a random() generator !! idiots from A-Z.
in my ~23yr professional security opinion, Equifax should be taken offline immediately, forever. if they wish to re-start selling everyones personal info (thats their biz btw) then they can do it via another company under new leadership.
Last edited by Linux_Kidd; 09-14-2017 at 04:09 PM.
Some group or unfriendly country could create a financial sneak attack. If you were worried about connected electrical grid (except Texas) then you need to be worried about this.
@MensaWater
if you are asking then you are late to the party
I was asking for links that proved a 9 year old bug. The first link you posted specifically has Apache saying there is a difference between a 9 year old flaw that might have only been recently discovered and a bug that has been known for 9 years which was the point I was making.
It goes on to say that the people that originally suggested it was this 9 year old bug have now backtracked and admitted it might have been the March bug that Apache had patched before the May exploit.
None of that explains why Equifax didn't report until September when they say they discovered the issue in July.
I agree that Equifax is just making things worse for themselves by trying to insist that people affected sign away rights just to find out they were affected. As I suggested in my post they should at a minimum freeze all access to affected numbers until everyone has been notified.
I also think that this would be a very good time to start regulating credit reporting agencies, and creating a "credit holder's bill of rights" which includes, for example, a requirement that you must be notified of a negative report against your credit and be permitted to respond before it appears on your record. Likewise, that applying for credit, and other "ordinary" uses of credit, do not negatively affect your score. Credit agencies operate as though they were an impenetrable black box with the sovereign prerogative to do whatever they damn well please ... and not to update their software for nine years even though every other player in the financial industry updates their software and is usually legally required to do so.
If this incident "turned the baleful light of reform" onto the credit reporting industry, I think it would be a very, very good thing that is long, long overdue.
It goes on to say that the people that originally suggested it was this 9 year old bug have now backtracked and admitted it might have been the March bug that Apache had patched before the May exploit.
the backtracking is not about 9805 being a 9yr old bug, it's a backtrack on how Equifax was hacked. we appear to know it was Struts 5638 and not 9805, but that is from https://www.equifaxsecurity2017.com which i am not trusting as of yet.
the claim that 9805 is in code as far back as 9yrs ago still needs to be confirmed yes/no, etc.
but, if 9805 existed at the same time as 5638 then we need some good forensics to get clarity as to what the data floes actually were.
i am also not confident in any way that Equifax is currently secured, lots of things to do with those exploits, etc. who knows what is still inside that has yet to be found. permitted 'bad' egress HTTPS from a server that typically does egress HTTPS may go un-noticed for some time. i see it all too often, "permit tcp 10.10.10.156 any eq 443" !!!
@sundialsvcs - if the govt were involved would it be even worse? we cant even get secured govt systems, look at the mess we had with HIE related to ACA (aka Obama-Care).
Quote:
Originally Posted by frankbell
The Equifax issue is ultimately a management issue.
Management didn't care.
Not that that is an unprecedented phenomenon.
not caring has years in jail, and, having known incompetence as a CISO means the board of directors may be facing jail time. i cant imagine anyone thinking its good to have a BA in Music Composition as the CISO !!
Last edited by Linux_Kidd; 09-16-2017 at 02:24 PM.
I would pretty much hope that ANY flaw found in software has been there since that software was written (at least that part of it)
Nobody -in their right mind- deliberately ADDS flaws later (with one possible exception)
That exception is is a deliberate testing control in that a number of known bugs are introduced before quality testing so that the percentage NOT found will indicate roughly how many REAL bugs have also evaded detection.
Josh Marshall, a journalist whose diligence and thoughtfulness has earned my respect, though I don't necessarily agree with him on everything (there's only one person with whom I agree on everything, and he's typing these words) had a thoughtful article on Equifax and the implications of its (in)actions at his website. He focuses lessons to be learned about financial and business systems and how they (don't) work: http://talkingpointsmemo.com/edblog/...m-with-equifax
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.