Open Bug Bounty selected among the
Top 5 Bug Bounty programs to watch
in 2021 by The Hacker News

For security researchers
Report a Vulnerability
Submit, help fixing, get kudos.
For website owners
Start a Bug Bounty
Run your bounty program for free.
1,202,930 coordinated disclosures
811,950 fixed vulnerabilities
1,570 bug bounty programs, 3,120 websites
27,909 researchers, 1,427 honor badges

JaPhoneAB Bug Bounty Program

JaPhoneAB runs a bug bounty program to ensure the highest security and privacy of its websites. Everyone is eligible to participate in the program subject to the below-mentioned conditions and requirements of JaPhoneAB

Open Bug Bounty performs triage and verification of the submissions. However, we never intervene to the further process of vulnerability remediation and disclosure between JaPhoneAB and researchers.

Bug bounty program allow private and public submissions.

Bug Bounty Scope

The following websites are within the scope of the program:

rey.se
lagaiphone.se

Non-Intrusive Submissions Handling

The following section encompasses submission of the vulnerabilities that do not require intrusive testing as per Open Bug Bounty rules:

- Cross Site Scripting (XSS)
- Open Redirect

- Cross Site Request Forgery (CSRF)
- Improper Access Control

General Requirements:

Data protection and security have always had a special meaning and, therefore, a particular concern for united-domains. We have a deep desire to see the Internet remain as safe as possible for us all. That is why we take security issues very seriously.

We are interested in hearing about any potential security issues on united-domains websites, web services, and products. To be eligible for a reward, note that we typically require the issue report to have some actual security impact in a realistic scenario. That does not mean you need to exploit issues fully. Just provide the information you have, and we will analyze your report and draw conclusions on the impact.

In our opinion, the practice of responsible disclosure is the best way to safeguard the Internet. It allows individuals to notify companies like united-domains of any security threats before going public with the information. That gives us a fighting chance to resolve the problem before the criminally-minded become aware of it.

Responsible disclosure is the industry's best practice, and we recommend it as a procedure for anyone researching security vulnerabilities.

We are happy to thank everyone who submits accurate reports which help us improve the security of united-domains. However, only those that meet the following eligibility requirements may receive a monetary reward:
* You must be the first reporter of a vulnerability.
* The vulnerability must be a qualifying vulnerability
* Any weakness found must be reported no later than 24 hours after discovery and exclusively through openbugbounty.org
* You must send a clear textual description of the report along with steps to reproduce the issue, include attachments such as screenshots or proof of concept code as necessary.
* You must avoid tests that could cause degradation or interruption of our service (refrain from using automated tools, and limit yourself about requests per second).
* You must not leak, manipulate, or destroy any user data.
* You must not be a former or current employee of united-domains or one of its contractors.
* Reports about vulnerabilities are examined by our security analysts. Our analysis is always based on the worst-case exploitation of the vulnerability, as is the reward we pay.
* No vulnerability disclosure, including partial, is allowed for the moment.

Qualifying Vulnerabilities:
* Cross-Site Scripting (XSS)
* Local files access and manipulation (LFI, RFI, XXE, SSRF, XSPA)
* Authentication and Authorization Flaws
* Cross-Site Request Forgery (CSRF)
* Remote Code Execution (RCE)
* Code injections (HTML, JS, SQL, PHP, etc.)
* Insecure direct object references
* CORS
* Directory Traversal
* Privilege Escalation

Non-Qualifying Vulnerabilities:
* Self XSS
* Missing cookie flags
* SSL/TLS best practices
* Mixed content warnings
* DoS or DDoS attacks
* HTTP Host Header XSS
* Clickjacking/UI redressing
* Software version disclosure
* Stack traces or path disclosure
* Physical or social engineering attempts
* Recently disclosed 0-day vulnerabilities
* Presence of autocomplete attribute on web forms
* Vulnerabilities affecting outdated browsers or platforms
* Issues that require physical access to a victim's computer/device
* Logout and other instances of low-severity Cross-Site Request Forgery
* Missing security-related HTTP headers which do not lead directly to a vulnerability
* Reports from automated web vulnerability scanners (Acunetix, Vega, etc.) that have not been validated
* Invalid or missing SPF (Sender Policy Framework) records (Incomplete or missing SPF/DKIM/DMARC)

We ask you to abide by the following guidelines:
* Unless united-domains permits you, do not disclose any issues to the public, or any third party.
* Unless united-domains permits you, do not publish any report submitted concerning this program.
* If you have questions on timelines (to remediation, bounty, etc.), please ask directly in the relevant report.

Testing Requirements:

There are some things we explicitly ask you not to do:
* When experimenting, please only attack test accounts you control. A Proof of Concept unnecessarily involving accounts of other end users or united-domains employee may be disqualified.
* Do not run automated scans without checking with us first.
* Do not test the physical security of united-domains offices, employees, equipment, etc.
* Do not test using social engineering techniques (phishing, vishing, et.c.)
* Do not perform DoS or DDoS attacks.
* In any way, attack our end users, or engage in trade of stolen user credentials.

In scope:
www.lagaiphone.se
www.rey.se

Out of scope:
All other companies and services acquired by united-domains are not in scope. That includes other hostnames or other subdomains not listed as in scope.

Possible Awards:

We reserve the right to adjust the bounty amount and change the report's vulnerability level accordingly, as well as not make a payout if, in our opinion, the above criteria have not been met. These bounties are only a guideline.

* Low 10 €
* Medium 30 €
* High 50 €
* Critical 100 €

Special Notes:

If you have any further questions, please do not hesitate to contact us.

Community Rating

Provided by security researchers who reported security vulnerabilities via this bug bounty program:

 
Response Time  Information How quickly researchers get responses to their submissions.
Remediation Time  Information How quickly reported submissions are fixed.
Cooperation and Respect  Information How fairly and respectfully researchers are being treated.

Researcher's comments

Esss_ayy     9 May, 2022
    Esss_ayy:
Hey,

Plz share email address to share bugs non report able here

  Latest Patched

 16.05.2022 baclieu.gov.vn
 16.05.2022 essuir.sumdu.edu.ua
 16.05.2022 westerncape.gov.za
 16.05.2022 mobilecentre.am
 16.05.2022 e-store.bluebrand.me
 16.05.2022 jic.edu.sa
 16.05.2022 faculdadefacit.edu.br
 16.05.2022 dochkisinochki.ru
 16.05.2022 uner.edu.ar
 16.05.2022 trangnguyen.edu.vn

  Latest Blog Posts

15.02.2022 by sepkatpro
Ultimate XSS Polyglot
11.11.2021 by mistry4592
The Most used Chrome Extensions are Used For Penetration Testing.
08.10.2021 by NNeuchi
How I Found My First Bug Reflected Xss On PIA.GOV.PH(Philippine Information Agency)
26.08.2021 by PyaePhyoThu98
eG Manager v7.1.2: Improper Access Control lead to Remote Code Execution (CVE-2020-8591)
14.07.2021 by Open Bug Bounty
Interview With Open Bug Bounty

  Recent Recommendations

@notedekd     28 April, 2022
    Twitter notedekd:
@singhnitesh21 provides precise and comprehensive vulnerable information. I highly appreciate the support and quick response.
@CERT_rlp     27 April, 2022
    Twitter CERT_rlp:
The team of CERT-rlp would like to thank Antonio for a responsible and coordinated disclosure of vulnerabilities
@DeanHalter     25 April, 2022
    Twitter DeanHalter:
Appreciate the skill and effort Nitesh and others in the open bounty, ethical hacker community bring to the table. He pointed out an XSS vulnerability on our website.
@TiagoGuedesEGo1     22 April, 2022
    Twitter TiagoGuedesEGo1:
Pranjal made us aware of several security vulnerabilities that represented security flaws of several degrees and needed to be rectified.

It was a pleasure working with him and I hope we can work again in the future, Thank you!
@DeanHalter     20 April, 2022
    Twitter DeanHalter:
Thank you for reporting the pair of XSS issues you found on our site. Your expertise and ethical reporting/handling helped us secure our website. Keep up the great and necessary work.