No technology is perfect, and curl believes that working with skilled security researchers across the globe is crucial in identifying weaknesses in any technology. If you believe you've found a security issue in our products, we encourage you to notify us. We welcome working with you to resolve the issue promptly.
While researching, we'd like to ask you to refrain from:
Any activities conducted in a manner consistent with this policy 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.
Any security problem in a released curl/libcurl version that hasn't already been reported and hasn't otherwise been made public, in full or in part, may be subject for a bounty. Responsible disclosure must be followed for a vulnerability to be subject for a bounty.
Vulnerabilities in features which are off by default and documented as experimental, are not eligible for a reward.
Any infrastructure issue that you may find is out of the policy unless it affects the source packaging/distribution. This includes but is not limited to DNS config for our domains and email setup details. Not in scope!
It is on purpose. It is a wiki. If you change or add non-curl related contents to prove a point, we consider that abuse.
Thank you for helping keep curl and our users safe!
|Scope Type||Scope Name|
This program have been found on Hackerone on 2019-04-25.