Vulnerability Disclosure Procedure


1.    PURPOSE:

This Vulnerability Disclosure Procedure (VDP) provides guidelines for the cybersecurity research to improve the security of our networked products, apps, and cloud services.  This VDP also instructs researchers on how to submit discovered vulnerabilities to the the relevant team.


We take security issues extremely seriously as Arçelik and welcome feedback from security researches in order to improve the security of our networked products, apps, and cloud services. We operate a procedure of coordinated disclosure for dealing with reports of security vulnerabilities and issues. Vulnerabilities submitted to us under this procedure will be used for defensive purposes to mitigate or remediate vulnerabilities in our networks and services.

Researchers must review and comply with following terms and contidions of this VDP before conducting any research or testing on our networked products, apps and cloud services.



3.1.    Reporting a Suspected Security Issue

Please send an email to or to report discovered a vulnerability in a Arçelik asset / system.

If your discovered vulnerability about one of our IoT products, its related mobile applications or their related cloud services please send your report to

Please share the security issue with us before making it public on message boards, mailing lists, or other forums.

To receive credit, you must be the first to report vulnerability, and you must notify us in accordance with following;


  • You should provide basic details of discovered issue, typically;

  • Name/type of affected product/app/service, plus specific model number, serial number, etc.

  • Any Proof of Concept(POC) setup details

  • Description of the steps to reproduce the issue

  • Public references if there is any

  • The details of system where the tests were conducted


By following the Vulnerability Disclosure Procedure, we will respond to you within a maximum of 48 business hours upon receiving the initial report. If the reported security issue will be confirmed by looking at the impact, severity, and exploit the complexity of the vulnerability report; we may ask for your further contribution to resolve the potential vulnerability within 90 days.


3.2.    Scope of Vulnerabilities

3.2.1.       Accepted Vulnerabilities

We are willing to be informed about demonstrated vulnerabilities of medium/high impact, such as authentication/authorization, cryptography, data leakage, and URL redirector abuse.


3.2.2.       Out of Scope Vulnerabilities

  • SSL vulnerabilities related to configuration or version

  • Denial of Service (DoS)

  • User enumeration/Brute forcing (for example Login and Forgot Password page)

  • HTTP Trace method is enabled.

    These qualify if you are able to execute an attack.

  • Clickjacking on pages without any authentication and/or sensitive state changes

  • Social Engineering/Phishing

  • Content spoofing

  • Self-XSS. Cross-site scripting issues should be exploitable in reflected, stored or DOM-based types.

  • Logout and other instances of low-severity CSRF

  • Missing HTTP headers

  • Missing cookie flags on cookies

  • Password complexity and reset password flow complexity

  • Invalid or missing SPF (Sender Policy Framework) records

  • Software banner / version disclosure.

    These qualify if you are able to provide an exploitable POC.

  • Results of automated tools or scanners

  • Autocomplete attribute on web forms

  • Vulnerabilities which require a jailbroken device


Although we find every vulnerability that comes from you valuable, we ask you to stay away from any kind of security research that may harm our users, systems and services and has the possibility of data corruption. Also, a researcher determines a vulnerability which includes any sensitive data (including personally identifiable information, financial information, or the proprietary information or trade secrets of any party), they must stop testing, notify relevant e-mail address immediately through our vulnerability submission process, and not disclose this data to anyone else. If a researcher engages in any activities that are inconsistent with this procedure or other applicable law, the researcher may be subject to criminal and/or civil liabilities.


3.3.    Disclosure of Vulnerability

Public disclosure of vulnerabilities approved/processed by us is not permitted under any circumstances.



As Arçelik, we will take appropriate steps to mitigate the risk and remediate the reported vulnerabilities by taking into account any vulnerabilities we receive and comply with the guideline.

Arçelik makes a commitment to cooperate with security researcher(s) as transparently and quickly as possible.

If researcher conduct vulnerability disclosure activities in accordance with our guideline and applicable law, Arçelik will not initiate any law enforcement related to such activities.



If you have any questions about the guideline or the process, do not hesitate to contact us: