Semmle looks forward to working with the security community to find security
vulnerabilities in order to keep our businesses and customers safe.
Please be aware that we have recently updated our scope; please check our
in-scope asset list before attempting any testing. Any testing against out of
scope domains will be marked as N/A
Semmle will make a best effort to meet the following SLAs for hackers
participating in our program:
- Time to first response (from report submit) - 5 business days
- Time to triage (from report submit) - 10 business days
- Time to bounty (from triage) - 10 business days
We’ll try to keep you informed about our progress throughout the process.
- Semmle is committed to working with the open source community and we believe in a transparent policy. As such, we strive to disclose reports once they are resolved. Please provide us a reasonable amount of time to resolve the report before any type of disclosure is made public.
- Follow HackerOne's disclosure guidelines __.
- Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.
- Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
- When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
- Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
- Social engineering (e.g. phishing, vishing, smishing) is prohibited.
- Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
Vulnerabilities affecting the following domains are in scope and may qualify
for a bounty:
Note: there is no need to request any sign-ups. Only lgtm-
com.pentesting.semmle.net has any user access for the purposes of this
program, and you may self-register accounts there.
Note: all production sites including semmle.com, _.semmle.com and lgtm.com and
.lgtm.com are out of scope_ .
In addition, non-HTTP/HTTPS services on the network 18.104.22.168/28 are also
eligible for bounties. This network range represents one of our public
networks used for front-end hosting.
Other domains, or subdomains not listed above are not in scope and will not
qualify for a bounty.
About Our Products
Semmle’s product is LGTM, an code analysis system which works by retrieving
source code from version control systems, (in some cases) building it with
some custom tooling, and creating analysis results.
The product comes in two variants: a publicly hosted version (lgtm.com) which
anyone is free to use to analyse publicly available projects on common hosting
platforms such as Github and Bitbucket; and an enterprise offering suitable
for use in corporate environments.
The public version uses Docker containers to isolate the build and analysis
environment from the rest of the infrastructure. By nature this environment
permits arbitrary code execution by any registered user, so the quality of
isolation is a critical part of the security model. The public site includes
two user types (user and admin user) as well as anonymous access.
This program includes a dedicated test instance of lgtm.com. In the future it
may also offer an accessible version of our enterprise product.
Examples of qualifying vulnerabilities likely to be eligible for a bounty:
- Cross-Site Scripting (XSS)
- Cross-Site Request Forgery (CSRF)
- Missing/Broken Authentication
- Arbitrary Code Execution (subject to the exclusions below)
- Breaking out of the build sandbox accessed through https://lgtm-com.pentesting.semmle.net __
- Privilege Escalation
Out of scope vulnerabilities
When reporting vulnerabilities, please consider (1) attack scenario /
exploitability, and (2) security impact of the bug. The following issues are
considered out of scope:
- Unauthenticated/logout/login CSRF.
- Attacks requiring MITM or physical access to a user's device.
- Previously known vulnerable libraries without a working Proof of Concept.
- Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
- Arbitrary code execution on the LGTM workers (although escaping the build sandbox is in scope on https://lgtm-com.pentesting.semmle.net/ __).
- DoS attacks involving exhaustion of resources, including adding a large number of projects, adding a project with a large number of commits or running a large number of queries.
- Attacks involving causing LGTM to send large numbers of emails.
- Attacks to gain access to Semmle’s first-party code.
- Email address enumeration.
- Any use of LGTM to attack systems other than ones under your ownership.
- Social engineering.
- Vulnerabilities that rely on the use of an unsupported browser or an outdated version of a supported browser. For reference, supported browsers are Chrome, Firefox, Internet Explorer, Edge and Safari.
- Lack of emails being sent out when a security-relevant event such a password reset occurs.
- Email security weaknesses such as lack of DMARC policies
- Submitting forms on https://semmle.com/ __
You can contact Semmle with queries about the bug bounty program by emailing
Thank you for helping keep Semmle and our users safe!