CARD.com's website is based on several layers of software including the operating system, webserver, database, and programming language of the site itself. CARD.com builds our site on top of those layers of software and has a shared responsibility with the developers of those products to keep the software safe.
CARD.com responsible disclosure policy
If you give us a reasonable time to respond to your report before making any information public and make a good faith effort to avoid privacy violations, destruction of data and interruption or degradation of our service during your research, we will not bring any lawsuit against you or ask law enforcement to investigate you.
However, there are some limitations and requirements you must follow.
Reporting an issue directly to CARD.com
We welcome your submission, but will only respond to valid issues that initiate a configuration or code change. All issue submissions are subject to the scope laid out below.
- Each issue will be credited to the first individual who reports it
- We will include your name and if you tell us a link we may include it
- You must not use automated tools that generate a large number of requests (i.e. more than a normal user browsing the site would experience)
- We have some known issues which we are not interested in receiving reports about:
- CSRF on forms that are available to anonymous users (e.g. the contact form)
- Username enumeration: our feeling is that usernames are only part of a secure login process and we do not consider allowing a brute-force dictionary-style enumeration to be a problem. If usernames are exposed without requiring dictionary-style guessing then we do consider that to be a vulnerability and welcome any reports of such issues.
- Server software "banner" being displayed - our server may indicate a banner (e.g. Apache version X.Y.Z) that seems out of date, but which is not in fact out of date due to the way we manage patches to that software.
Thanks to security researchers!
If you follow our responsible disclosure policy in reporting a security bug that materially affects CARD.com's websites or infrastructure (see below for a list of those), we will give you thanks by naming you on this page. In the future we hope to be able to give even more thanks. To report an issue to us send a mail to security AT card.com. If the issue is in upstream software you are also encouraged to use their contact process if they have one.
- Peter Jaric - @peterjaric
- Frans Rosén - @detectify
- Shashank - @cyberboyIndia
- Harsha Vardhan Boppana - @hvboppana
- Kamil Sevi - @kamilsevi
- Anand Sundar Tiwari - fb:anandtiwarics
- Devesh Bhatt
- Mohankumar Vengatachalam - @vimokumar
- Ali Hasan Ghauri
- Adam Ziaja - @adamziaja
- Ali Hasan Ghauri - @alihasanghauri
- Jay - @Silent_Screamr
- Nitesh Shilpkar - @NiteshShilpkar
- Arpit Gupta - fb:erarpitgupta
- Gökmen GÜREŞÇİ - @GokmenGuresci
- Pankaj Singh - @singhpankaj7777
- Rafay Baloch - @rafaybaloch
- Ravikumar Paghdal - @_RaviRamesh
- Javid Hussain - @javidhussain21
- Jigar Thakkar - @jigarthakkar39
- Moham Krushna Kallepalli - @MohanKallepalli
- Prem Kumar - @iAmPr3m
- Nitin Goplani
- Jatinder Pal Singh
- Hardik Tailor - @iamhardiktailor
- Simone Memoli - @Simon90_Italy
- Jay Turla - @shipcod3
- Peter Wolanin
- Rakesh Singh - @zerodayguys