How to responsibly report a security issue
Acquia takes the security of our products very seriously. We educate our staff on security best practices and our development process includes quality assurance such as peer review to help ensure our products are high quality and secure. However, like all complex software products it is possible that a security vulnerability may be present in one of our products. If you discover a security issue in an Acquia product or hosted service, we ask that you report it to us confidentially in order to protect the security of our services. Please email the details to our security team at firstname.lastname@example.org. Acquia's security team will respond to confirm receipt of your message, review and plan the mitigation of the issue appropriately, as well as set a timeline for a new release or patch. We follow responsible disclosure and will credit researchers when a security issue has been identified and mitigated while adhering to the following specifics.
- You may not use automated tools in your research without our explicit consent. Use of automated tools may result in investigative action or your IP(s) being blocked.
- You make a good faith effort to avoid privacy violations, destruction of data and interruption or degradation of our service during your research.
- You give us reasonable time to respond to your report and carry out remediation.
- We credit the first researcher to report an issue. Additionally, we reserve the right to only acknowledge researchers who discover issues in Acquia products or hosted services, if we determine the issue to be of a high or critical severity, or if there has been continued research or contributions made by the reporter.
- We will credit you with your name and a "no-follow" link to the address of your choosing (e.g. Twitter or personal website).
- We are not interested in reports on the following issues:
- CSRF in forms available for anonymous user use (e.g. the contact form)
- Displayed server software "banners" or version information
- Issues that are being handled in public issue queues of any of our OSS projects in use
- Click-jacking on Acquia.com domains that do not involve authenticated user accounts
- We will not bring any lawsuit or begin law enforcement investigation into you if you follow these parameters.
What details should you include when reporting a security issue
Please provide as many relevant details as you can. In particular:
- What versions of software are involved
- What steps someone can follow to go from an initial installation of that software to a point where they see the vulnerability
- Any patches or steps to mitigate the problem
A special thanks to the following people that have responsibly disclosed vulnerabilities to Acquia in the past:
-Kamil Sevi (@kamilsevi)
-Emanuel Bronshtein (@e3amn2l)
-M.R.Vignesh Kumar (@vigneshkumarmr)
-Prajal Kulkarni (www.prajalkulkarni.com)
-Himanshu Kumar Das (@mehimansu)
-Ajay Singh Negi
-Atulkumar Hariba Shedage
-Chiragh Dewan (@ChiraghDewan)
-Rafay Baloch (rafayhackingarticles.net)
-Adam Ziaja (adamziaja.com)
-Piyush Malik (@ThePiyushMalik)
-Wan Ikram (@rinakikun)
-Narendra Bhati (facebook.com/narendradewsoft)
-Ahmad Ashraff (@yappare)
-Tejash Patel & Parveen Yadav (www.backtracktutorial.com)
-Sebastian Neef & Tim Schäfers - (@internetwache)
-Vinesh Redkar (AVsecurity.in)
-Samandeep Singh (@samanLEET)
-Dhaval Chauhan (@17haval)
-Nitesh Shilpkar (@NiteshShilpkar)
-Umraz Ahmed (@umrazahmed)
-Ehraz Ahmed (@securityexe)
-Jigar Thakkar (Infobit Technologies)
-Tushar. R. Kumbhare (Defencely)
-Frans Rosén (www.detectify.com)
-Yuji Kosuga (@yujikosuga)
-Rafael Pablos (silverneox.blogspot.com)
-Reegun Richard Jayapaul (linkedin.com/in/reegun)
-Nitin Goplani (in.linkedin.com/in/nitingoplani)
-Ali Hassan Ghori
What if the issue is in some other software?
Acquia relies on open source software such as Drupal, Varnish, memcache, nginx, Apache, MySQL and many others. If you identify a vulnerablity in one of our products that is actually in the underlying software then you can report the issue to us but could also report it to the security team for that project. For Drupal see How to report a security issue in Drupal. If you report an issue to Acquia and the problem lies with another product we will also contact and coordinate with their team prior to making any release.
Handling site-specific security questions
In general we cannot provide security support for non-Acquia customers. If your site was attacked or you have a security issue in custom code on your site the best place to get help is via an Acquia Support Subscription. If your site was attacked and is hosted on Drupal Gardens or Acquia Cloud then please use the above reporting process regardless of whether or not you have a support subscription. If you have a problem with spam posted to your site then this does not need to be handled privately. For spam issues please refer to articles about spam from the Acquia Library (requires Acquia Network subscription to read full articles).