Discussion Locked

Should We Be Legally Obligated to Fix Vulnerabilities?

0 helpful
26 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

http://www.eweek.com/article2/0%2C1895%2C2194578%2C00.asp

I got this in my email this morning, and was totally expecting the read to be yes. You should be legally obligated to fix vulnerabilities. But as I read this, I swear to god my impression of the people being interviewed was eh. Depends, is it worth the trouble.

[i]By itself, a given vulnerability doesn't mean anything. It has to be evaluated in the context of a broader IT environment, and of the broader business, and only then can you make an informed decision as to whether or not it is a critical, code-red vulnerability. But without context, nobody can tell what the impact of vulnerability is. It could be that the Web application doesn't touch the database, or it could be that even if a program is subject to a SQL injection, it might not create a risk for the database. [/i]

??????????????????? Who the hell is making decisions like this. Do they know what they are talking about? Do they know the total structure of the online application? Do they know that this injection for sure will not allow root access to the machine through some vulnerability of the os they know NOTHING about.

Sorry, I think that was a terrible statement. And my impression of the whole article was they had the same attitude. Which, I think is why we have so many problems right now.

Ok, not enough coffee. Just woke up. Running around trying to read that and also get ready for work. I'm done with my rant. They are probably right(god, I hope I never work for them). I'm probably wrong. Thats why I'm still the grunt and they are the overpaid suits that walk two feet above the ground because they are god like in their knowledge and wisdom.

Dan

26 replies

by Former member

maybe it's just my old brain. No, not all vulnerabilities are "critical" if that's what you are protesting. That's why they are rated. And yes, in the context of one's network architecture and security mitigations already in place, you can forgo a lot of patching. If you have network firewalls and Intrusion Prevention Systems in place that already block/deny a lot of this stuff, there's no reason to panic and apply all patches immediately.

by danlm

Your correct, not all vunerabilties are critical. But they should not be ignored. Everything has a priority, but even things with low priorities are done at one time or another.

My take on that artcile was:
1). Should we be legally obligated to fix them?
- Yes, we should in my oppinion. Both small and large vulnerabilities. You take care of the critical ones first, but you also fix the small ones as a follow up.
2). I had the impression from the article that some of the individuals did not think all vulnerabilities needed addressing at all. I totally disagree with that.

Dan

by Former member

Sometimes patches cause more problems than they fix. And as I stated before, it depends on your security defenses as well. If the risk is low-to-nil, then there's no need to patch. For example, if there's a port 445 exploit out in the wild, and I have that port blocked on all firewalls, what would be the danger of not applying the patch? What if the vulnerability is just a DoS or escalation of privileges? What if it requires admin access? You have to apply patches based on assessed risk. If you're worried about hackers getting in and what-not, you can believe they would not be using public exploits, but rather their own or other un-published code.

by jaqui

that twit needs to be included in that section of the herd [ human race ] that needs to be "thinned down" [ chlorine in the gene pool ]

are you gonna pay for the bullets?

by Former member

I support the position that we as developers should be required not only to fix vulnerabilities but also to produce bug free products.

I further support that there should be legal penalties for not repairing products ranging from fines and recall to disbanding software houses.

by tony hopkinson

the EULA, it would seem we aren't.

In fact seeing as I out of teh goodness of my heart for a negligible cost have leased you this software, stop being so damned ungrateful.
:d

On a more serious note software houses would go out of business if they were legaly required to sell you stuff that both worked and didn't break anything else.

I'd love to see some of the big boy's faces if this got regulated. It would make that photo of the tobacco barons, after they were deemed liable for health problems look like they'd just dropped their keys on the floor.

Hmmm 'health warning on the shrink wrap.

This software can seriously damage your business.

:d

by absolutely

If you buy a door with lock & key included at Home Depot, and the lock mechanism opens for any thin flat piece of metal, regardless of the shape of the grooves cut into the "key", the words "lock" & "key" are obviously misnomers, and hundreds of years of legal precedent establish the sale of such as fraud.

If you buy a door and an experienced locksmith is able to pick the lock, tough luck. Their job is to know how to do that, and I don't believe "absolute inaccessibility to all" is reasonably implied, either in the case of the door or of software. But, we should also not be vulnerable to "script kiddies", ie amateur thieves.

I think the situation of the software industry is more analogous to the former than to the latter.

[i]"The presence of a vulnerability may or may not mean anything. That's especially true for Web vulnerabilities because the Web applications are incredibly complex. A vulnerability at one level in an application may mean nothing. The actual risk of data loss from that vulnerability is nil, based on how that application has been constructed.

"For example, if what you're trying to protect against is customer data being stolen from a database, you could try to achieve that by doing a code review of all your Web apps. You could try to achieve it by deploying a lot of firewalls and IDSs [intruder detection systems]. You could try to take down all your wireless networks. You could try to achieve that by inspecting security at the other end of VPN connections, if you're worried about people coming into partner network?a very legitimate concern."[/i]

Because of the [b]complexity[/b] of web applications, he recommends ignoring vulnerabilities in them, but suggests instead a lot of products that he'd like to sell you, in the professional role for which he was interviewed in the first place. In other words, it's his job to emit such nonsense. Nothing to see there. Move along.

by danlm

Then your product should not allow access to the residence. Ie, if I sell a product that allows lookups of a catalog of products... This product should not allow lookups of personal accounts or access to the root account.

Dan

by absolutely

OK, so by that analogy, when we're talking about buying a computer we're talking about purchasing an entire house, not just a door, or a window. Anyway, there are openings, by design. They let us exchange information with other computers. Maybe it would be best to keep personal information, from financial data to reall names, off computers that are connected to the Internet, until programmers do implement controlled access as secure as you and I want it.

by danlm

If the vulnerability resides at the os, then the os developers should correct it and bare the cost of those corrections.

If a vulnerbility is created in an application due to a lower level vulnerability(ie, the os). Then I say the os developers should be responsibile.

if it is an application vulnerability, then the cost should reside with the vendor that supplied the application.

Why do you ask? Am I missing where you were trying to go with this question????

Dan

by tonythetiger

I don't think that ANY OS or software is bulletproof, only that some bullets aren't yet discovered. I can see making writers responsible for repairing vulnerabilities that were (or should have been) known at the time of writing, but how can you program against something that hasn't yet been invented?

[i]If the vulnerability resides at the os, then the os developers should correct it and bare the cost of those corrections.[/i]

For how long?

by Former member

I'd like to see your "bug-free" software. That and the pig you flew in on...

by Former member

Q, I agree that there is really no such thing as bug free software - at the design and development stage. I also agree that it is difficult to test for all things that a user may do, as an example, I can crash many, if not most programs by starting them and then shutting them down before they fully load. The s**tty part is that much of the time this leaves the process running without the app and creates a security hole.

But the fact that I can do this, or that I believe that software should be as bug free as possible and that software houses should be responsible for all damage caused by mis- behaving apps does not negate your or my responsibility to produce as bug free software as possible.

How to minimize bugs? There are many different philosophies on this. How about for starters, do not just test end points, do some random testing as well. Second, how about 90 percent testing.

Now get over the Risk-Driven scheduling presented by Micro Soft in the manual that came with Visual Studio 6.0. In case you are not familiar with it, the manual is titled "Visual Studio: Developing For the Enterprise" and the pages I am referring to are 45 - 47.

Now, grow up and learn that there are divergent opinions in software development and also accept that your f**k-up could cost some company millions.

Now, let us discuss flying pigs.

by Former member

Risk-driven analysis of security risk comes straight from the IT Security discipline, something I think you're not really into. In fact, I'm sure you can find it in any CISSP manual. Or you can just ask your local CSO if you have one.

LOL! Now now now no use in getting uptight about the whole issue here. Do you think you are the first person to bring up "minimizing bugs"? What company today does NOT want bugs in their software? Do you have any idea how much it costs to monitor and fix these bugs? So I imagine you have the magical elixar that will cure all bugs eh? The real world dictates that bugs will happen. Blame it on economics, outsourcing, crappy programmers, features, bad drivers, bad OS, bad handlers, poorly written dlls....whatever! The list is ENDLESS!

by Former member

that you used in the above post.

I believe that you are incorrect in your assumption of where Risk-Driven analysis comes from. Check further back, you may find that the text I referred to predates the organization that you mentioned. The reason I say this is that I still have the copies of the manuals that came with VS 5.0 and there is reference to creating bug-free software.

I agree with your assessment of why there are bugs. However, I intensely disagree that bugs that are known should be released; and this is just what a software house does to get a leg up on the competition. It is just plain wrong and dishonest.

Now, I became upset because you engaged in a personal attack on me. I take personal attacks... well, personally. You can pretty much say anything to me or call me anything and I will not take it personally unless it is an attack. In fact, I will listen to you and often investigate what you say. Further, if I am wrong, I will openly admit it. While I screw up, I have no shame in my game.
:)

by tony hopkinson

was inefficient and ineffective.

I favour decoupled designs, unit testing and good test cases myself, oh and crossed fingers.

Bug free software.

It worked on my machine and does what I thought you said you said you wanted. :D

Mistakes are necessary, otherwise we could never improve, or occasionally get lucky with a different solution.

OK hands up who's been forced to leave a bug in their app, because the users thought it was a feature?

by Former member

Tony, in my experience, random testing is inefficient. The one thing it can do that we have a hard time doing is to present unpredictable input. I presented it only because we can not predict just what a user will do. I had a class in which I had to test a test case; I failed every test of a test case with random testing. On the other hand, the case I was testing had to be rewritten because the random testing exposed bugs in the test case.

I favor pretty much what you do, but I realize that not all coders write programs the same way.

by Former member

>"If you're worried about hackers getting in and what-not, you can believe they would not be using public exploits, but rather their own or other un-published code."

You need to have a re-think.

by Former member

Really. Security is my current discipline. Engage. I don't deny automated bots and script kiddies will use only what's available and maybe SOME underground code, but many if not most professional hackers will use their own exploits and tools they keep to themselves.

by Former member

Since about 1985 when I attended Utah State University. The question I ask you is: when do we ever stop being students.

If you ask, My first computer was an Obourne 1. That should tell you something. If that does not, my father was a programmer with I.B.M. Las Vegas in the 60's and I learned the basics of assembly from him.

Incidentally, I am close to 50.

This discussion is closed to new replies.