The information on this page is intended for security researchers interested
in responsibly reporting security vulnerabilities to the CompanyHub security
Security requires transformation and there is no better way to transform a
security program than to engage directly with our customers and users. It is
that engagement, along with a strong belief in the collaboration with the
security community, that is the key to maintaining a secure environment for
all of our users. If you believe you've discovered a security vulnerability on
or within CompanyHub, we strongly encourage you to inform us as quickly as
possible. We ask that such vulnerability reports be kept private and
researchers not make those public until we have resolved the issue.
In return, we will work to review reports and respond in a timely manner. We
will invite you to our disclosure program at Hackerone, to triage your
submission. CompanyHub will not seek judicial or law enforcement remedies
against you for identifying security issues, so long as you (1) comply with
the policies set forth herein; (2) comply with Hackerone’s Standard Disclosure
Terms; (3) do not compromise the safety or privacy of our users; and (4) do
not destroy any sensitive data you might have gathered from CompanyHub as part
of your research once issues are resolved.
Thanks for your help!
CompanyHub believes that working with skilled security researchers across the
globe is crucial in identifying weaknesses in any technology. If you have
information related to security vulnerabilities of CompanyHub, we want to hear
from you. Please submit a report in accordance with the guidelines below.We
value the positive impact of your work and thank you in advance for your
CompanyHub agrees to not pursue civil claims against researchers related to
the disclosures submitted through this website who:
do not cause harm to CompanyHub, our customers, or others;
provide a detailed summary of the vulnerability, including the target, steps, tools, and artifacts used during discovery (the detailed summary will allow us to reproduce the vulnerability);
do not compromise the privacy or safety of our customers and the operation of our services. Specifically;contact us immediately if you inadvertently encounter user data;
do not view, alter, save, store, transfer, or otherwise access the data, and immediately purge any local information upon reporting the vulnerability to CompanyHub;
act in good faith to avoid privacy violations, destruction of data, and interruption or degradation of our services (including denial of service);
comply with all applicable laws;
do not violate any other law (other than those that would result only in claims by CompanyHub), or disrupt or compromise any data that is not their own;
publicly disclose vulnerability details only after CompanyHub confirms completed remediation of the vulnerability and not publicly disclose vulnerability details if there is no completion date or completion cannot be ascertained;
While researching, we'd like to ask you to refrain from:
Reports from automated tools or scans
Issues without clearly identified security impact (such as clickjacking on a static website), missing security headers, or descriptive error messages
Missing best practices, information disclosures, use of a known-vulnerable libraries or descriptive / verbose / unique error pages (without substantive information indicating exploitability)
Speculative reports about theoretical damage without concrete evidence or some substantive information indicating exploitability
Forms missing CSRF tokens without evidence of the actual CSRF vulnerability
Self-exploitation (e.g., cookie reuse)
Reports of insecure SSL / TLS ciphers (unless you have a working proof of concept, and not just a report from a scanner such as SSL Labs)
Our policies on presence/absence of SPF / DMARC records
Password complexity requirements, account/e-mail enumeration, or any report that discusses how you can learn whether a given username or email address has a CompanyHub-related account
Missing security-related HTTP headers which do not lead directly to a vulnerability
Self Cross-site Scripting vulnerabilities without evidence on how the vulnerability can be used to attack another user
Social engineering of CompanyHub-related employees or contractors
Any physical attempt against CompanyHub-related property or data center
Presence of autocomplete attribute on web forms
Missing secure cookie flags on non-sensitive cookies
Denial of Service Attacks
Banner identification issues (e.g., identifying what web server version is used)
Open ports which do not lead directly to a vulnerability
Open redirect vulnerabilities
Publicly accessible login panels
Content spoofing / text injection
Please use your own account for testing or research purposes. Do not attempt to gain access to another user’s account or confidential information.
Please do not test for spam, social engineering or denial of service issues.
Your testing must not violate any law, or disrupt or compromise any data that is not your own.
Please contact firstname.lastname@example.org to report security incidents such as customer data leakage or breach of infrastructure.
Any activities conducted in a manner consistent with this policy and and
HackerOne’s policies regarding this vulnerability disclosure program will be
considered authorized conduct and we will not initiate legal action against
you. If legal action is initiated by a third party against you in connection
with activities conducted under this policy, we will take steps to make it
known that your actions were conducted in compliance with this policy.
By clicking Submit Report, you consent to Your Information being transferred
to and stored in the United States and acknowledge that you have read and
when you created your account.
Thank you for helping keep CompanyHub and our users safe!
|Scope Type||Scope Name|
Firebounty have crawled on 2020-02-13 the programe CompanyHub on the platform Hackerone.