Discussion Locked

Security researcher faces jail time for publishing software vulnerabilities

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

Guillaume Tena, a French security researcher currently with Harvard University, could face jail time for publishing vulnerability research on TEGAM International's Viguard antivirus software. French prosecutors claim that Tena violated French copyright laws by publishing his research, which, according to a French judge included some re-engineered Viguard source code. Prosecutors are seeking a 4-month jail term and a 6,000 euro fine (approximately 7,890 US dollars).

Read the whole story:
http://virusthreatcenter.com/permalink.aspx?BlogId=113

How should we balance the developer's copyright and trade secret privileges with the public's need for secure software?

How do you believe software vulnerabilities should be disclosed?

Should researchers and IT professionals submit vulnerability research first to developers and allow for a fix before going public?

How long should developers be given to release a fix before vulnerability research is made public?

13 replies

by jaqui

how you are publishing the information.

publishing that the exploit exists, right away.
publishing exactly where it exists, not until after it's patched.

publishing code for the exploit, ( the actual malicious code ) never.

by daappley

What does a person gain by publishing an issue that they find, when there is no fix for it? This is especially pertinent when you are dealing with closed source software. If you are not able to help create a fix, then I feel, that it is extremely in-prudent to publish the issue as you are now CREATING the problem by giving malicious users the information they need to exploit those systems. I believe a software vendor needs to be given sufficient time to create a fix before any flaws are published to the general public. It seems to me that they want to get the word out first, simply so they get credit for the find, not for any benevolent reason.

by jaqui

and if the vulnerability is in an open source app, you get a huge number of programmers working on fixing it...FREE

you can't even try to protect against it if you don't know it's there. so let people know so they can try to find workarounds until it is patched.

by aaron a baker

I'm Sorry; I cannot agree witht the "Ford analogy" for disclosure of the virus of which we speak. Having comunicated with Secunia, the Firm who "Supposedly" reported the fault without notifying Microsoft. I was told that it was in fact another "Firm" which works for Secunia" called "Hex Dump" that went public prematurely even before alerting Secunia or Microsoft about the problem. This in my opinion was the wrong thing to do. If I had a Ford and the Brakes were dangerous, the very FIRST people I would call would be FORD. If no action was immediately taken I would then consider the alternatives. This firm,however well intended,"If this is what it was and not Grandstanding" was definitely wrong to act as they did. They worked for Secunia, they should have either informed Secunia as is thier first duty whereupon secunia would have immediately reported the problem to Microsoft or in the event that Secunia didn't act, report to Microsoft directly, not go public. This is the proper way of doing things, not going behind someone's back and blurting it all out without giving the firm in question notice or time to take action. An action that I'm sure would have been immediate. No matter how we look at his, this type of Knee-Jerk reporting, causes nothing but panic and worry and embarassement and should definitely be considered inapropriate and inexcusable. There is also the element of trust. Secunia trusted this firm and this "firm" should have done the right thing, report to Secunia first and Microsoft, both being highly reputable, they would have taken immediate action and rest assured that they too would have published the problem without the cost of embarassement to Microsoft. The bottom line is as that, We being Techs know very well, there is a right way and a wrong way,in my opinion,this was definitely the wrong way.
Thank you.
Aaron A Baker

by aaron a baker

My Apologies to you all, I was refering to another situation of the same thing. However, I feel the same for this as I did for the other.
Regards
Aaron A Baker

by mr l

Sorry Aaron, that dog won't hunt. Yes, vulns should be disclosed to the vendor, who should be given a reasonable, but not open-ended, window to remediate...then the vulnerability should be disclosed. There have been documented (many many) insatnces of Microsoft sitting on vulns for 6 months+ without a fix, so please don't think that they respond "immediately".

Without the "threat" of public disclosure, do you really think that vulnerability remediations would be nearly as quick as they are today?

by aaron a baker

This firm's first duty was to report to "Secunia" and only "IF" Secunia din't take action they should have notified Microsoft and yes I am well aware of the Microsoft clock.That doesn't change the fact that this firm was working for Secunia and thier first duty is to thier employer yes? Therefore by going "Around" thier employer's back tho make themselves look good they have commited a "breach of trust" and should be treated accordingly.For all of our Knowledge, savvy,savoir faire and any else we can think of,the first thing we "Must Be is Up Front and Honest",as Techs, we all know that.Our Honesty 'Is" our reputation. This in my opinion was not the case here and therein lies my objection. They should have done the right thing.
Regards
AaB

by awfernald

I have no idea what French law says on this issue, so, depending on that would be whether what the guy did was right or wrong.

However, courtesy says.... the researcher should have notified the software maker first to give them a chance to start working on the defect, then, if that didn't happen, publish the work.

Common Sense says.... alert the software maker and publish the work without having a "how to exploit this defect" attached, simply telling that there is a flaw of x type, and that the company is coming out with a fix at this time.

by daappley

I don't think this fella deserves jail time. I mean when did bad judgment become a crime? If he can be put in jail for making a bad decision then I think we could all be deserving of jail time. I'd like to see him say "sorry, I will NEVER do that again" and that would be that in my eyes.

by jessie

Robbing a liquor store... drinking and driving... child abuse... these are all examples of bad judgement for which I will personally not accept an "I'm sorry, I'll never do it again."

Now, not knowing what exactly was published, what French law dictates and what have you, it would depend entirely on the depth of the moronity. If you loan a buddy a gun knowing that he might use it to murder someone, you are an accessory to murder. If you publish info about a software vulerability knowing there are PLENTY of hackers out there who will exploit that info, makes you an accessory to virus creation/distribution.

by jessie

that you approach the vendor first with your findings. It's the same thing I apply in my personal life, if I have a problem with something that's going on, I go to the "perpetrator" and explain the issue and my problem with it. If that doesn't help, THEN I go to a higher-up.

by daappley

I suppose I didn't consider that he is an accomplice to hacker activity. Your viewpoint is very valid there. I suppose we will have to wait and see what the French courts have to say on it. Like you, I know nothing about French, or international, laws in this regard. Whatever the decision this is a HUGE precedent and I am interested to see the results.

by elisko

First, the link in the article above doesn't seem to work anymore.

Googling the researcher's name brought me to this blog entry http://www.darknet.org.uk/2006/03/donations-flood-in-for-guilty-security-researcher-guillaume-tena/ where some helpful commenter provided a link to "Guillermito's" own site (in French) where the "crime" occurred http://web.archive.org/web/20030404161138/www.pipo.com/guillermito/viguard/index.html . If, like me, you can only vaguely decipher written French, you might also be helped by Google Translate http://translate.google.com/translate?prev=hp&hl=en&js=y&u=http%3A%2F%2Fweb.archive.org%2Fweb%2F20030404161138%2Fwww.pipo.com%2Fguillermito%2Fviguard%2Findex.html&sl=fr&tl=en&history_state0= (Of course, it only translates the first third of a veeery long web page.)

Basically, he rips through a seemingly very shoddy anti-virus program by showing how to test it. In the process, he gives a good introduction to HOW to test such programs which, unfortunately gives a good deal of theory as to how to write viruses, too. He writes a very basic "test" virus, and then installs one after another existing viruses, showing how the program does or does not detect them, and a little bit of why, and also gives a few software analysis tools that may be of help to people, white or black hat.

The actual code violation, according to one poster, is "65 bytes" but I didn't figure out exactly where - it seems to be some of the "reverse engineered" software that he deduces by black-box testing, which according to the French court matches the vendor's copyrighted software.

From the bottom of the web page, he shows where he corresponded with the company, but I can't figure out if the page was public before that point or not. In any case, the company stonewalls him and lies, claiming, according to his quote, that any viruses that their software doesn't detect are "harmless", anyway, so why bother checking for them? This, while their web site claims to stop ALL viruses.

If the "criminal" page wasn't live before that point, I can understand his righteous indignation in posting it afterwards.

In balance, a ZD|Net UK article http://news.zdnet.co.uk/itmanagement/0,1000000308,39183786,00.htm says that Tegam International, the vendor, posted a "refutation" of his claims, saying that Guillermito's methods were shoddy, and that he had also "harrassed" the company about their vulnerabilities. Those links, though, no longer function.

Besides the criminal suit, the vendor was filing a civil suit against him for 900,000 Euros in damages! It seems that they were clutching at straws, though, because three months later they went bankrupt. http://translate.google.com/translate?hl=en&sl=fr&u=http://www.journaldunet.com/solutions/0505/050520_tegam.shtml&ei=JydvSoqUKsTOjAevwrWdBQ&sa=X&oi=translate&resnum=7&ct=result&prev=/search%3Fq%3Dtegam%2Binternational%26hl%3Den .

Personally, I wish they had stayed around, because if I were him I would have countersued for false advertising, in return. As it was, though, it seems that Guillermito got his fine paid with the help of others over the Internet, so he wasn't left in the wind.

The French are still left with the foul taste of this case as a legal precedent, though.

Anyway, it's all a page out of history now, four years later. I started writing up this comment before I twigged to the dates, and figured that I might as well put a post here with the final outcome of the story for any future readers. I just wonder why TR suddenly pulled this thread up as "most popular"?

This discussion is closed to new replies.