News for hackers. Stuff that matters.
Re:Hardcoded Password Found in Cisco Software by Cyph0n on Friday March 09, 2018 @11:18AM (#16552766)
From my understanding, Cisco has been taking security very seriously ever since the Snowden leaks.

They essentially have an entire team dedicated to designing and implementing security measures for their devices. However, the focus seems to be on hardware and low-level security. I don't know if they have an active high-level software security team.

Re:Hardcoded Password Found in Cisco Software by txcwpalpha on Friday March 09, 2018 @12:29PM (#16553279)
As a security consultant, it makes me sad that the criteria for "taking security seriously" is as low as just "having an entire team dedicated to ... security".

Every company should have a team (or depending on size, at least a person) dedicated to the security of software and infrastructure. Even the most traditionally slow-moving companies these days have security teams. If you do not have this, you are behind and are laughably unprepared for the modern age. I wish the public would start recognizing this and publicly shaming companies that don't take security seriously.

Re:Hardcoded Password Found in Cisco Software by brianwawok on Friday March 09, 2018 @01:21PM (#16553681)
> Every company should have a team (or depending on size, at least a person) dedicated to the security of software and infrastructure.

Two competitors in a space. One has 3 developers and 1 security guy, the other has 4 developers.

In 99/100 outcomes, all else being equal, the 4 developer guy will add more features and outpace the other team and win the market.

Security is an overhead and a drag on company resources.. until it's not.

But how many startups fail due to lack of a security team? I cannot think of any from my RL network. I am sure some exist... but otherwise, this is the same as most "safety" measures... unimportant until it is really important.

Re:Hardcoded Password Found in Cisco Software by bproven on Friday March 09, 2018 @02:31PM (#16554246)
Mainly b/c there are no real downsides/penalties to leaking data (or PII) - you say "sorry" and just move on. Sometimes with an increased stock price - see Equifax :(
Re:Hardcoded Password Found in Cisco Software by reaperducer on Friday March 09, 2018 @03:43PM (#16554843)
Depends on the industry. In some heavily-regulated industries, there are huge fines at stake for leaking information.

Look at healthcare. If information leaks, it has to be reported to the feds within 24 hours of initial discovery. Not C-level finding out, but whatever low-level employee finds it. Even if it's one person. If it's more than around 10 people, there's a federal requirement to report it to the local media.

Re:Hardcoded Password Found in Cisco Software by bussierem on Friday March 09, 2018 @03:56PM (#16554962)
>In some heavily-regulated industries

I think the fact that this doesn't apply to "the people storing our credit and SSN information" is just about the apex of stupidity.

Re:Hardcoded Password Found in Cisco Software by txcwpalpha on Friday March 09, 2018 @11:17PM (#16557066)
I used to work specifically in the healthcare space doing cleanup work for companies that had been recently breached. I think "huge fines" is quite an overstatement. The largest HIPAA fine in history for a data breach was for the Anthem hack, which was a leak of ~80 million records and Anthem was fined $115 million. That's no small number, but at the end of the day it's still only less than 5% of their yearly net income. And Anthem is a huge outlier: the second largest HIPAA fine in history was only ~$6 million. It's not exactly a huge deterrent for companies that want to ignore security.

In terms of the public exposure, you'd probably be surprised at how many healthcare insurers/providers have data breaches but you never hear about them because these companies know how/when to report it so that it ends up nothing more than a footnote on the back page of the local paper.

Re:Hardcoded Password Found in Cisco Software by derefr on Friday March 09, 2018 @02:43PM (#16554344)
> But how many startups fail due to lack of a security team?

Crypto exchange startups, for a big, glaring example. They’re an exception in a lot of ways, though.

Re:Hardcoded Password Found in Cisco Software by nevir on Friday March 09, 2018 @03:05PM (#16554542)
They're also a category where security is inherently a user-visible feature of their products (and as such, it _should_ be easier to justify security engineers)
Re:Hardcoded Password Found in Cisco Software by golergka on Saturday March 10, 2018 @05:39AM (#16557982)
I thought that there was a non zero probability that they are "hacking" themselves, simply taking customers money and inventing excuses for it.
Re:Hardcoded Password Found in Cisco Software by kbenson on Friday March 09, 2018 @04:19PM (#16555136)
> In 99/100 outcomes

In other news, in 99/100 occurrences of the phrase "99 times out of 100" the person stating it is pulling numbers out of their ass to sound authoritative.

If you think the vast majority of the time the extra developer helps that company succeed and outperform the other company, then perhaps you should start with "I think the vast majority of the time..." instead of making up magical numbers. Sure, we all know the numbers are bullshit, but that's not excuse where there are perfectly normal ways to express what you mean that don't masquerade as fact.

> Security is an overhead and a drag on company resources.. until it's not.

And sometimes that "until it's not" could be from the very beginning, if it's used for market differentiation. As soon a you talk about competition and businesses it becomes about a whole lot more than technical merit and features. Things like current market position, advertising, strategic partnerships, etc start having an impact, and sometimes it's a large one.

Re:Hardcoded Password Found in Cisco Software by brianwawok on Friday March 09, 2018 @06:00PM (#16555792)
> In other news, in 99/100 occurrences of the phrase "99 times out of 100" the person stating it is pulling numbers out of their ass to sound authoritative.

I can use whatever writing style I want to. If you don't like it, read another post.

Re:Hardcoded Password Found in Cisco Software by kbenson on Friday March 09, 2018 @06:47PM (#16556100)
Sure you can. And I'll free to call out when you are making factual assertions that aren't facts. In the same vein, you're free to ignore my comment.

I'll concede my original comment might have come across as a bit more harsh than intended, but I think the point stands. If you're trying to prove a point or provide information in a discussion, don't use loose and hyperbolic terminology without expecting to be called out on it.

Re:Hardcoded Password Found in Cisco Software by tinymollusk on Saturday March 10, 2018 @11:58AM (#16559216)
Doesn't his "99/100" give us a much better idea of his confidence in his own knowledge, compared to something more vague like "usually" or "the vast majority of the time"?

I ask because I've been studying how to make better decisions, and one of the techniques is to use numbers instead of the easily misinterpreted words. The famous example is the Bay of Pigs decision -- Kennedy was told the invasion plans had a "fair" chance at succeeding. The advisor was later interviewed and said that he meant 3-1 against as "fair odds", which could easily have changed Kennedy's decision.

Re:Hardcoded Password Found in Cisco Software by kbenson on Saturday March 10, 2018 @03:28PM (#16559992)
> Doesn't his "99/100" give us a much better idea of his confidence in his own knowledge, compared to something more vague like "usually" or "the vast majority of the time"?

Sure, it gives an idea of confidence, but we haven't established that confidence as worth anything yet, and we're being fed numbers to add an air of legitimacy to a statement which doesn't really have any otherwise. Unless someone has actually examined 100 cases, it's just bluster. It's like saying "oh, that never happens" to discount an argument entirely. It's not helpful to a real discussion.

> The advisor was later interviewed and said that he meant 3-1 against as "fair odds", which could easily have changed Kennedy's decision.

The adviser was likely also someone with previously established expertise in this area, which means that opinion might be worth something without supporting evidence. Additionally, giving actual predicted odds is different than falling back on on a colloquialism that almost never literally means 99 times out of 100 or 99%, but instead is meant to convey "almost always", and using terminology like that in a conversation without any supporting evidence isn't useful.

Re:Hardcoded Password Found in Cisco Software by tinymollusk on Saturday March 10, 2018 @07:45PM (#16561006)
I agree about this particular comment -- your interpretation is likely correct. I was just trying to connect it larger, to the decision making skills that I'm working on (and thought might be interesting to a HN audience).

FWIW, the Pigs incident is widely cited as an example within this sphere. It has nothing to do with whether the advisor was previously skilled -- it has more to do with thinking about how people understand and use the information I communicate. (and that using numbers instead of words seems to be considered "best practice" in the decision making community).

Re:Hardcoded Password Found in Cisco Software by foo101 on Friday March 09, 2018 @09:20PM (#16556734)
> I can use whatever writing style I want to. If you don't like it, read another post.

We can refute whichever post we want to. If you don't like it, read another post.

Re:Hardcoded Password Found in Cisco Software by cookiecaper on Friday March 09, 2018 @03:20PM (#16554653)
I'm going to disagree on the basis that segmenting your security personnel creates a lot of difficult social dynamics. However the model is structured, "security" becomes a pain point, and no one wants to see the security guy coming around the corner.

The default interpretation (which is basically the only one that counts) is that this guy is coming around, tearing down _your_ work, and making you look bad in front of everyone, and what does he even know about this thing?

Some people will chicken out, not press the matter, and then the "security people" are just the fall guys, unable to do anything other than take the blame for the other peoples' screw-ups. In my experience, a lot of internal security people end up stuck in that position whether they're trying to fight the good fight or not.

The dynamic is similar to the corrosive POV that sees "dev" and "ops" as orthogonal concerns to segment out, and we all know how well that's gone over. Anyone looking forward to hearing all about "DevSec" in the next 10-15 years, once some startup finds a way to put a cute icon on it and gets a big pile of investor money to burn (cf. Docker)?

Rather than create a tense segmentation, it's better to just hire competent developers who know security well from the get-go. Maybe they can rotate weeks doing security reviews or something like that.

I don't know, I don't really have a good solution. I just know that making someone the enemy by labeling them "security personnel, here to block your deploys, tell you you're doing your job wrong, and generally just embarrass you in front of your peers and superiors" is not going to help much.

Re:Hardcoded Password Found in Cisco Software by Cyph0n on Friday March 09, 2018 @12:54PM (#16553500)
I agree, but I think you overestimate: (1) how many companies actually care about security and (2) how recent this security-focused movement among large companies is.

Furthermore, Cisco deals with security problems that few other companies worry about, such as the wide-scale availability of counterfeit devices and convincing foreign customers that their devices are backdoor-free.

Re:Hardcoded Password Found in Cisco Software by qubex on Friday March 09, 2018 @01:28PM (#16553732)
(3)What small firms’ margins of contribution allow, given the competition in their markets.

I for example run a family business that operates in the paint sector in Italy, and you’d be horrified by how compressed margins are (and have become over the past five years of debt crisis and economic recession).

There’s always this aura that a rational firm can arbitrarily add structural (HR) costs to defer some nebulous, future “risk”, but in my experience this is not the case (anymore). Competition is so hardscrabble and survival is such a luxury that pretty much everybody is not only willing but obliged to skimp on everything. Being “with the times” simply isn’t an option, sadly.

Re:Hardcoded Password Found in Cisco Software by ggg9990 on Friday March 09, 2018 @05:25PM (#16555566)
Companies won’t take security seriously until 1) customers demand methods of evaluating the security of a company and making purchasing decisions accordingly — “size of security team” doesn’t count, and 2) sufficiently punishing companies that cause user harm through security failures, i.e. forcibly liquidating Equifax and confiscating all senior executives’ assets including their house.
Re:Hardcoded Password Found in Cisco Software by caymanjim on Friday March 09, 2018 @01:51PM (#16553909)
In a large company, a company with sufficiently-sensitive data (where loss is a legal matter), or a company with a lot of money to lose (financial processing), having a dedicated security team might make sense and might be worth the money, but in most situations, I think it does more harm than good. Security teams rarely know how applications work, so their approach to security is heavy-handed and provides a false sense of protection. It's more important to instill everyone with security-minded philosophy, so that applications and systems are designed with security in mind from the beginning.

Firewalls, packet inspection, virus scanning, and the like would all be completely unnecessary if code was written securely and if human beings behaved properly. Of course these things don't happen, and of course firewalls and scans and the like are common-sense protections, but most data loss is caused by poorly-designed applications which run in very secure environments. Dedicated security teams simply aren't in a position to identify and solve problems like buffer overruns or SQL injection.

Re:Hardcoded Password Found in Cisco Software by unethical_ban on Friday March 09, 2018 @11:02PM (#16557033)
This whole post reeks of developer arrogance.

>Security teams rarely know how applications work, so their approach to security is heavy-handed and provides a false sense of protection.

Yes, sometimes there are overly bureaucratic processes in place, but as a security guy, do you know how many times we see devs self-SQL injecting themselves on a webpage? How many times they ask if their service needs to be in the DVZ? (What the fuck is that; I think they mean DMZ)? Or Why it's a problem that they're asking why they can't have "The Internet" when I ask what services their server needs externally?

Don't act like devs (or even IT Ops as a whole) has their shit together. They're at LEAST as security-crippled as security EVER is over-paranoid.

And as for this...

>Firewalls, packet inspection, virus scanning, and the like would all be completely unnecessary if code was written securely and if human beings behaved properly.

First, code will never be written completely securely; second, security is a spectrum of mitigation therefore ACLS/firewalls/scanning will ALWAYS be necessary; third, humans NEVER behave properly, inside or out therefore security will always be in business.

Re:Hardcoded Password Found in Cisco Software by pbhjpbhj on Friday March 09, 2018 @03:02PM (#16554519)
>Security teams rarely know how applications work, //

I'm amazed if anyone working in a computer security role doesn't know about SQL injection attacks and their mitigations. You'll be telling me they don't know about salting passwords next??

Re:Hardcoded Password Found in Cisco Software by taway1929293 on Friday March 09, 2018 @04:41PM (#16555297)
Where I work, yes, the security teams don't know how applications work. we have a dedicated security team - they run nessus scans for compliance and network scans and hand them to managers and executives who hand them to us. they explicitly don't touch the code - a senior guy has declared that he's not responsible on that level, that he's 'no coder' in response to a shell injection vulnerability. so he knows 'about' salting passwords but he probably couldn't verify if they are salted or not.

To me it's left the impressions that 1) security is mostly theater and 2) 'security engineer' is a meaningless title - it can mean anything from 'runs scans' to 'network administrator' to 'penetration tester' to 'good engineer'. unfortunately my default attitude towards the title has been "i'm probably dealing with a charlatan"

Re:Hardcoded Password Found in Cisco Software by phil21 on Friday March 09, 2018 @10:11PM (#16556882)
Yep. The vast majority of "security" folks I've worked with could be described as "compliance" folks instead.

Almost nothing is done for actual real infosec, and in many cases their existence actually is a step backwards.

A real security minded company (and I've worked for some) don't have such a silly thing. Everyone is considered part of the security "team" since that's the only way secure services and software actually get built.

Hiring some random dude to run halfass tools against hosts and generate reports is simply checking a compliance box and only serves to act as a CYA for the organization and more importantly it's officers. Almost no one actually cares about real data security, in my experience.

Re:Hardcoded Password Found in Cisco Software by eftychis on Friday March 09, 2018 @07:26PM (#16556281)
Calling this security engineering is a misnomer. Yes, I agree the way you describe it this is pure theater.

I take a bit of a long position, please bear with me:

A lot of engineering is plagued by the notion of theater, forced either by outer or inner (see management) pressure to project an image. Examples: "Everything you see is rendered online", "our investing plan is done by this awesome bot" etc. With security really a lot of times it is hard for people to see the incentive. Loss is hard to quantify for people and then there is the extreme optimism. "Oh we are using TLS and we have our data on AWS, we do not need anything else." It is a field, that is hard to quantify that focuses on rare events.

And then consumers just don't care about non-tangible things like their data till it's too late. What happened to Equifax? If Equifax had lost directly an equal amount of money to the damages it will/has caused with the data loss, response of the public would be more drastic and there would be civil charges at least.

Same for Trustico. A guy decided it is ok to send a crazy amount of secrets over email. Then people realize the guys expose the freaking shell and root. And now Trustico is back in business (still unbelievable to me...). Thus companies have little pressure to do the job right. And companies tend to satisfy the minimum necessary requirements.

A final reason also: too little supply. This field has a lot of specialization and there is a bunch of theory and skills required. And on top of that you need to have a good understanding and skills from the other fields you touch (e.g. linking, compilers, web development, distributed systems,...)

Similarly, to be a graphics engineer you need to know some computational geometry and then a bunch of extra stuff depending on your specialty. I think it is hard for someone to pose as a games engine engineer and have no idea about convex hull operations. However, due to the reasons above a person can pose as a security oriented engineer and say a couple of hot words and get a job in some companies. And from experience management is filled with people like "What why aren't we encrypting passwords?" or "We need to have an option for people to opt out during clientHello and just use HTTP."

Regarding your senior guy: He is not a security engineer or whatever. The way you describe the situation and taking a positive vantage point, I think the management had to sell to some outsider that they care about security and hired a penetration tester maybe gave him a title that could as well be "Lord of the Stars and Black Holes" and went on with their lives. Why? Because they are not accountable regarding this view of the product.

It's hard to bullshit people about an app that is not working. It is easy to bullshit people about an app that is barely functional and sends their data to the pockets of third parties.

From personal experience that is not the case for some serious companies. And there are some extremely good security engineers/cryptographers/... engineers out there.

Re:Hardcoded Password Found in Cisco Software by candiodari on Monday March 12, 2018 @01:53AM (#16566422)
Of course, that is trivial superficial stuff. It's akin to checking if the door of a car is open.

Should it be done ? Perhaps (assuming you're using SQL at all), but let's not pretend an app is secure just because an attempt at SQL injection fails.

Re:Hardcoded Password Found in Cisco Software by user5994461 on Friday March 09, 2018 @03:03PM (#16554523)
>>> Dedicated security teams simply aren't in a position to identify and solve problems like buffer overruns or SQL injection.

Yes they are. That's exactly two of their purpose.

You'd be amazed what an automatic scanner and a manual edit of the service url "/log?name=/etc/password" can uncover.

Re:Hardcoded Password Found in Cisco Software by ploxiln on Friday March 09, 2018 @11:31AM (#16552855)
The thing about security is, it does not work well to try to just add it "on top". You have to overhaul the existing teams and processes, to basically be mindful, to think about this stuff and care.

Just enumerating all the stuff you need to not do (e.g. "don't call system() with user input") is inefficient and not completely effective. In my opinion. "Scans" turn up a bunch of false positives and false negatives.

Re:Hardcoded Password Found in Cisco Software by dmlorenzetti on Friday March 09, 2018 @01:27PM (#16553722)
There's a new-ish book, "Secure by Design", that makes this point -- and shows ways for ordinary devs to design for security without explicitly thinking about security.

I really like this book so far (it's still in the early access stage of writing).

https://www.manning.com/books/secure-by-design

Re:Hardcoded Password Found in Cisco Software by Cyph0n on Friday March 09, 2018 @11:58AM (#16553045)
> You have to overhaul the existing teams and processes, to basically be mindful, to think about this stuff and care.

Right, but this team is not only improving current devices, but also designing the next iteration of Cisco products with a focus on security.

Re:Hardcoded Password Found in Cisco Software by athenot on Friday March 09, 2018 @01:15PM (#16553620)
We do. :)

More importantly, there's also a Secure Development Lifecycle process that basically involves everyone. Security is not an "after the fact" feature that gets bolted on right before market time, it's a requirement for any project or feature and starts at design time, and gets evaluated several times during the development of the product (and after it's released).

https://www.cisco.com/c/en/us/about/security-center/security...

Re:Hardcoded Password Found in Cisco Software by adrianN on Friday March 09, 2018 @02:15PM (#16554106)
Then how does a hardcoded password make it to the customer?
Re:Hardcoded Password Found in Cisco Software by haloux on Friday March 09, 2018 @10:46PM (#16556985)
Good one. But honestly, what kind of answer are you honestly seeking here?
Re:Hardcoded Password Found in Cisco Software by frankharv on Friday March 09, 2018 @02:48PM (#16554392)
They are a USA company so maybe a National Security Letter or a FISA court order.

The USA now has secret court systems and all USA companies are bound by them.

Re:Hardcoded Password Found in Cisco Software by Kadin on Friday March 09, 2018 @03:23PM (#16554673)
That's a pretty asinine way to add a backdoor. I think we can give the intelligence community more credit than that.

Plus, if you're an intelligence agency, the ideal backdoor is one you can use, and only you can use -- one that other adversaries can't take advantage of even if they know it's there. A hardcoded password is the opposite of that; once its existence leaks out, which it invariably will, it's open to everyone.

Having a developer modify some crypto code in a subtle way that happens to reduce the effectiveness of the system such that it becomes marginally more vulnerable to a certain type of obscure cryptanalysis, preferably very resource-intensive analysis that only you can perform, is the direction I'd try for...

Re:Hardcoded Password Found in Cisco Software by stordoff on Friday March 09, 2018 @06:03PM (#16555814)
If a intelligence service is adding the backdoor themselves, or the company is willingly working with them, sure, but I can imagine a scenario where a court orders them to provide access but does not specify the technical means. In that case, the company isn't particularly incentivised to make a subtle/NOBUS backdoor.

I'd also wonder about it being a case of deniability - a hardcoded password can be written off as a development/debug oversight, whereas a more structured backdoor/deliberate vulnerability to cryptoanalysis is harder to explain away if found.

Re:Hardcoded Password Found in Cisco Software by ceejayoz on Friday March 09, 2018 @12:41PM (#16553396)
> They essentially have an entire team dedicated to designing and implementing security measures for their devices.

Isn't that the absolute barest minimum for a corporation of that size and infrastructural importance?

Re:Hardcoded Password Found in Cisco Software by Cyph0n on Friday March 09, 2018 @12:50PM (#16553460)
In this day and age? Other than your occasional Google or Apple, I don't think so.
Re:Hardcoded Password Found in Cisco Software by logicallee on Friday March 09, 2018 @01:20PM (#16553667)
>>>> They essentially have an entire team dedicated to designing and implementing security measures for their devices.

>>Isn't that the absolute barest minimum for a corporation of that size and infrastructural importance?

>Other than your occasional Google or Apple, I don't think so.

Cisco is a $218.62B company (about 24% size of Apple by market cap, 27% of Google by market cap) which is a "Networking hardware company". (As opposed to, say, McDonald's.)

I'd say it definitely qualfiies as your "occasional Google or Apple" in terms of "size and infrastructural importance."

Re:Hardcoded Password Found in Cisco Software by Cyph0n on Friday March 09, 2018 @01:36PM (#16553802)
I was not talking about "size" at all. I was referring to Google and Apple as examples/outliers of companies that put a huge emphasis on security in practice.
Re:Hardcoded Password Found in Cisco Software by haloux on Friday March 09, 2018 @10:44PM (#16556979)
I’d beg to differ. Even in the silicon forest, I frequently come across firms with entirely dedicated Appsec and Infosec departments. Most dev shops out here have them and I’d be comfortable extrapolating that to SV and old money NY/CHI/LA and Austin based on my consulting experience.

All of this is, of course, anecdotal but it’s a tad more than a blanket refutation.

Re:Hardcoded Password Found in Cisco Software by thathappened on Sunday March 11, 2018 @12:29PM (#16563586)
My understanding is any government vendor has to let said government at least audit the source if not provide it to allow then to modify for the equipment they purchase.

With that said , if they also control the land it's being shipped through I recall pictures of nsa intercepting Cisco boxes to update FW.

So really it's a matter of which government you want spying on you and whether you keep MGMT private or not.

Re:Hardcoded Password Found in Cisco Software by TaylorAlexander on Friday March 09, 2018 @01:24PM (#16553700)
Google (Actually X/Alphabet) started an entire company focused on computer security. They would have whole departments dedicated to this, rather than teams. But I get that maybe this is a semantic issue.

https://www.theverge.com/2018/1/24/16929320/google-x-cyberse...