Questions of Legality

Questions or suggestions about the platform
Post Reply
User avatar
x1admin
Site Admin
Posts:3102
Joined:Sun Nov 15, 2015 7:04 pm
Questions of Legality

Post by x1admin » Tue Jul 25, 2017 9:14 pm

Hi Folks,

Immense contribution of our community to making Web a safer place is unquestionable. Being a non-profit project with the sole purpose to make Web a safer place, Open Bug Bounty is committed to comply with enacted laws and regulations. To double-check that our community follows this important commitment, we asked an acquaintance from a law firm to clarify certain aspects of security testing.

Only a court is eligible to decide if something is legal or not [within its jurisdiction], however the text below can help understand how law works in general and shape your research activities accordingly.

Disclaimer: this text is provided without any warranty and shall never be taken as an instigation to commit any acts or start any activities.
There are numerous jurisdictions and a great variety of laws, statutes and acts aimed to punish computer crime. Laws of many countries and states may be contradictory, Common (e.g. USA) and Civil (e.g. continental EU) law systems also have substantial differences. Complicated procedural rules, supremacy of federal over state law and conflict of laws make the situation ever more confusing. Therefore, let's try to keep things simple:

1) Civil ("civil", do not confuse with "Civil" law system) lawsuits are primarily designed to compensate tangible (e.g. financial) damages, or to prevent them (e.g. via injunction). Therefore, any civil suit requires a proof of measurable damage caused by someone's [negligent or intentional] acts. Otherwise, it will likely be dismissed by the court.

1.1 People cannot be placed in jail, searched or arrested within the scope of a civil lawsuit (exceptions are out-of-lawsuit violations, such as perjury, obstruction of justice or contempt of court).

1.2 Very few companies will ever start civil litigation if provable damage is insignificant OR the tortfeasor (offender) does not have enough money to compensate the damage inflicted. Otherwise, even their own legal costs will never be covered.


2) Criminal charges are brought exclusively by the government with the main purpose to punish a socially-dangerous behavior. Anyone, who is a victim of a crime, can file a complaint (usually to police), but only the government (usually represented by a prosecutor) can bring criminal charges at the end.

2.1 Virtually any criminal law (statute or act) requires both (a) a malicious intent AND (b) a malicious act. For example, if you buy salt in a local shop and resell it to your friend, and then discover cocaine inside - intent is missing, and you will almost surely be acquitted (but if you sell it for the price of cocaine, no jury or judge will ever believe that you didn't have the intent and were unaware of the cocaine). Exception are so-called "strict liability" offenses where you don't need to act intentionally, knowingly, recklessly or with criminal negligence to be found guilty (currently we are not aware of any strict liability laws in cybercrime sphere).

2.2 To be found guilty, the government must prove "beyond a reasonable doubt" (this is the official standard) EVERY element of the offense specified in text of the statute (law). Presumption of innocence clearly says that one is considered innocent unless proven guilty. For example, if there is a law that criminalizes playing red ball in the city of NY, you can play blue or orange ball in the center of NY without fear, because a vital element of the offense (color) is missing here (except if there is another law prohibiting blue balls as well).

2.3 In some states laws are so blurred and can be construed so broadly that even penetration testing can be a serious crime. However, to avoid absurd results, government [almost] never prosecutes this. Criminal law is also influenced by public policy and politics. In some countries, criminal charges are not brought for the ultimate benefit of the society or economy of state funds. Some minor offenses may be factually decriminalized as law enforcement refuse to investigate them.

2.4 Always keep in mind, that only a court can decide that something violates an enacted [criminal] law and thus is illegal. Lawyers have no legal authority to make any adjudications, but can merely suggest that a specific act or activity may be in violation of a particular law(s). Moreover, almost in every country, you may appeal to at least two superior courts and possibly vacate the judgement of the inferior court.


3) In most countries, the wast majority of laws that criminalize hacking, require a malicious intent to cause damage to (a) integrity (e.g. deface or web shell upload), OR (b) availability (e.g. DoS) OR (c) confidentiality (e.g. extracting data via SQL injection) of any [computer] system [that does not belong to you OR that you are not duly authorized to use in such a manner].

3.1 Re frivolous claims "testing without consent is illegal". Always ask your opponent: (a) in jurisdiction of which particular state it is illegal, (b) which particular law, statute or act recognizes such activities illegal, (c) which particular section/paragraph of the law states that these activities are illegal. Finally ask for the previous cases when a court have already adjudicated this specific, or a less offensive, behavior to be a crime. Ask about definition of "testing" and "consent" specified by the law or accepted by the courts. Does a copy-paste of numerous phrases with double-quotes into a website search represent a "testing without consent" under this specific law?

3.2 Exploitation of SQL injection can be a criminal offense in almost every jurisdiction. /*This is why Open Bug Bounty never accept them*/. However, when hacking of hundreds of celebrities is punished by six months of prison in US, a single quote in your browser address line will quite unlikely trigger a prosecutor spending his/her limited resources to prosecute this.

3.3 Customized crawling of a public website for accidentally leaked confidential information (e.g. passwords) may be considered a crime in many jurisdictions as well. This is because you, and any reasonable person in your shoes, know or should have known that this information is strictly confidential, and therefore you knowingly violate the confidentiality by abusing the weakness (even if you don't make any money with it afterwards). On the other hand, if you open a suddenly defaced website and it contains 10 000 passwords on the main page in plaintext - you have not committed an offense (but be careful, if you will store them locally - you may be found guilty).

3.4 Careful and non-intrusive testing (i.e. that is not aimed to and cannot affect integrity, availability or confidentiality of the website or related computer systems such as databases) of a public website with the sole pro bono intent to help fix the vulnerability is very unlikely to be found illegal in the majority of jurisdictions. However, running general-purpose security tools (e.g. scanners that test for all types of vulnerabilities, including intrusive testing) against the systems, or extorting monetary remuneration for the discovered flaws, can likely be in violation of enacted laws in many jurisdictions.


4) Misleading claims about illegality of certain acts or activities can be indictable in many jurisdictions, especially if a third party that makes such claims has an interest to intimidate and unfairly preclude you from certain, otherwise lawful, activities. When someone, except law enforcement or judicial authorities, tries to intimidate you with allegations of illegality, you can politely remind them that their behavior can be against the law.


5) Instead of a conclusion, remember that law is a very complicated subject and even supreme courts change their verdicts from time to time. A minor factual difference in two very similar cases can dramatically change the outcome of judgement. Therefore, it's almost impossible to give one-size-fits-all advice for any activities, from driving or cooking to information security. However, almost always, you can rely on a common sense: if what you do is done with a good faith and does not harm or put at risk individuals or society - you have a very low chances to be found guilty.
If you have any reliable information or cases to be added - please do so!

Spam404Online
Posts:296
Joined:Mon Nov 23, 2015 6:43 pm
Contact:

Re: Questions of Legality

Post by Spam404Online » Tue Jul 25, 2017 9:55 pm

Very interesting! Thanks for providing this.

Out of my 22k submissions not once have I had any legal issues. I think only a total of 3 times have I had some negative (not at all legal) response but after explaining that I am only trying to help, they seem fine about it.

Aside from those 3 experiences, every other interaction has been great. Some even overly positive like inviting me to their company headquarters or paying expenses for security conferences. Meeting the people on the other end of my report in real life was surprising as I wasn't sure how they would react or feel about me (probably could of guessed given they've flown me all across the globe :lol:) but, they were super appreciative and glad it was me letting them know about the vulnerability rather than discovering it being exploited while looking at their server logs.

The whole legal ordeal regarding OBB probably has some substance in certain countries but it still makes me laugh every time when I think about someone getting into trouble for pointing out a reflected cross-site scripting or open redirect vulnerability. I'll eat my white hat should I have a legal issue while using OBB to help website owners rectify vulnerabilities on their websites :)

micomat
Posts:169
Joined:Tue Mar 07, 2017 7:16 pm

Re: Questions of Legality

Post by micomat » Wed Jul 26, 2017 5:00 am

Well, I can speak only for the country i live in: Germany.

Here the law ("Hacker Article") is talking about:

§202a "Spying out data"
"Anyone who is unauthorized or has access to data which is not intended for him and which is particularly secured against unauthorized access, by overcoming the access security"
--> so that does not fit to XSS or CSRF testings. May fit to SQLi but also not sure. For IAC test it could be a problem

§202b "Interception of data" -> does not fit to XSS or so

§202c "Prepare for spying out and intercepting data"
Whoever prepares a crime according to § 202a or § 202b, by
1. Creating passwords or other security codes that allow access to data (§ 202a), or
2. Creating computer programs whose purpose is the commission of such an act,
or sells them to another person, distributes or otherwise makes them available to others, ..

--> so that is also irrelevant for XSS. For IAC when testing with default passwords it might be a problem.

I was talking to a lawyer regarding Bounty Hunting and he was quite sure it's not a big deal as especially for XSS you're just entering data in a field made for entering data. Data handling and neutralization is up to the website owner.

I've furthermore had some lawyers on my "hit list" which never had any complaints about my information.

User avatar
mradamdavies
Posts:29
Joined:Wed Nov 25, 2015 3:00 pm
Contact:

Re: Questions of Legality

Post by mradamdavies » Wed Aug 09, 2017 3:39 pm

Spam404Online wrote:
Tue Jul 25, 2017 9:55 pm
Very interesting! Thanks for providing this.

Out of my 22k submissions not once have I had any legal issues. I think only a total of 3 times have I had some negative (not at all legal) response but after explaining that I am only trying to help, they seem fine about it.
I received legal threats from a previous employer after making my Barclays Bank post live. I don't think they understand the law as they couldn't have instantiated legal action on their behalf, if they wanted to.

§202a "Spying out data"? Not exfiltration of data?

As an aside: The Law Society of Ireland were very receptive to having their security issues fixed. They had as much right to try litigation as anyone. I got some free swag for helping them instead of a visit from the police. :)

micomat
Posts:169
Joined:Tue Mar 07, 2017 7:16 pm

Re: Questions of Legality

Post by micomat » Sun Aug 13, 2017 7:13 am

mradamdavies wrote:
Wed Aug 09, 2017 3:39 pm
Spam404Online wrote:
Tue Jul 25, 2017 9:55 pm
Very interesting! Thanks for providing this.

§202a "Spying out data"? Not exfiltration of data?

nope it's not exfiltration, it's spying out.

baptx
Posts:2
Joined:Mon Aug 28, 2017 9:36 am

Re: Questions of Legality

Post by baptx » Tue Apr 17, 2018 2:46 pm

Hello, can you recommend a professional liability insurance for security testing and vulnerability reports on Open Bug Bounty?

kongwenbin
Posts:18
Joined:Sun Sep 24, 2017 4:30 am

Re: Questions of Legality

Post by kongwenbin » Fri Apr 20, 2018 8:04 am

I believe that as long as people remember to not perform any intrusive testing and do not exploit the discovered issues in a bad way, most companies should be fine with it and might even appreciate the kind gesture of notifying them. One thing I observed that might be a potential problem is when researchers don't contact the company properly.

For example, I spoken with a friend few weeks back. He works at a bank and he was notified that there is going to be a public disclosure on Openbugbounty for one of his bank's subdomain in the next few days. That was the first time he know about the platform. He don't have any impression of anyone ever trying to contact them on anything related to this report in the past few months as well. He is interested to fix the problem but he only has a few days and at that time, he don't even know how to reproduce the issue and it is going to be difficult for his team to investigate without knowing the payload.

So guys, please do your best to contact the company if you find something on their website, unless they really does not want to reply back at all -- at least we tried our best.

baptx
Posts:2
Joined:Mon Aug 28, 2017 9:36 am

Re: Questions of Legality

Post by baptx » Sun Apr 29, 2018 1:14 pm

I know the risk of having complaints is low if we do responsible testing but sometimes stored XSS can make a site unavailable with a simple alert test. It happened to me once because JavaScript code was replaced with an empty string and the interface kept loading indefinitely for all users. Hopefully there was a contract with the website, I saw the problem and found a way to revert my action. An insurance could help in some cases.

There is also the case of unfixed vulnerabilities published, a website owner could complain that a CSRF issue was exploited to edit or delete data by someone who found it on Open Bug Bounty. And an unfixed public XSS issue could be used for session hijacking or data exfiltration.
A website owner could say he did not receive our emails or that he was not available for more than 3 months.
When submitting a bug that is listed publicly on Open Bug Bounty and details are hidden from the public for 3 months, the reports could still be used to find vulnerable websites and easily find an exploit if it is a systemic XSS or CSRF.

The safest / more ethical way to respect privacy while reporting a vulnerability on Open Bug Bounty would be to make the report private by checking the "Do not publish the incident" option and only make it public if the vulnerability is fixed and the website owner agrees.

I may need a professional liability insurance for freelance development so it would be good if it includes bug bounties.
Let me know if someone knows insurances for bug bounties at a reasonable price.

Update:

Here is an interesting article "18 year old guy arrested for reporting a shamefully stupid bug in the new Budapest e-Ticket system": https://blog.marai.me/2017/07/24/18-yea ... -e-ticket/
Not sure if it is a coincidence but the article was published 1 day before the creation of this topic by @x1admin :D
I found the link on this article: https://www.cyberscoop.com/eu-vulnerabi ... ask-force/

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests