RESPONSIBLE VULNERABILITY DISCLOSURE POLICY
Index
Introduction
This policy aims to define a process by which security researchers can work with ORF to help improve the security of our products and services.
ORF takes security and the trust of our users very seriously. The responsible disclosure of security vulnerabilities helps us to ensure the security and privacy of our users. We are committed to thoroughly investigating and resolving security issues on our platforms and services.
In Scope
This disclosure policy applies only to vulnerabilities in ORF products and services under the following conditions:
- Only domains/subdomains which have a security.txt file in their root (i.e. https://shop.orf.at/security.txt) are in scope. Currently, the scope is limited https://orf.at
Out of scope
Any services hosted by 3rd party providers and services are excluded from scope.
In the interest of the safety of our users, staff, the Internet at large and you as a security researcher, the following test types are excluded from scope:
- Findings from physical testing such as office access (e.g. open doors, tailgating)
- Findings derived primarily from social engineering (e.g. phishing, vishing)
- Findings from applications or systems not listed in the ‘Scope’ section
- UI and UX bugs and spelling mistakes
- Reports of non-exploitable vulnerabilities and/or reports indicating that our services do not fully align with „best practice“ (e.g. missing security headers) are not in scope.
- Network level Denial of Service (DoS/DDoS) vulnerabilities
- TLS configuration weaknesses (e.g. „weak“ ciphersuite support, TLS1.0 support etc.) are not in scope.
- Volumetric vulnerabilities are not in scope (i.e. simply overwhelming our service with a high volume of requests is not in scope).
- Personally, identifiable information (PII)
- Credit card holder data
Rewards
Unfortunately, due to ORF’s funding structure, it is not currently possible for us to offer a paid bug bounty program. We would, however, like to offer a token of our appreciation to security researchers who take the time and effort to investigate and report security vulnerabilities to us according to this policy. Reporters of qualifying vulnerabilities will be offered a unique Company reward and special acknowledgement of achievements on the company’s website.
Mandatory Rules
Responsible security researchers understand that the integrity and security of our customers is our priority and will work with ORF to ensure that all necessary vulnerabilities are resolved, and that customers have ample opportunity to deploy the fixes required before releasing information regarding their finding on a public forum, blog, or social media.
The ciso@orf.at address is only to be used for submitting potential product vulnerabilities. Regular product or service support should be directed to our contact E-mail kundendienst@orf.at.
Security researchers must not:
- Access unnecessary amounts of data. For example, 2 or 3 records is enough to demonstrate most vulnerabilities (such as an enumeration or direct object reference vulnerability);
- Violate the privacy of ORF users, staff, contractors, systems etc. For example, by sharing, redistributing and/or not properly securing data retrieved from our systems or services;
- Communicate any vulnerabilities or associated details via methods not described in this policy or with anyone other than your dedicated ORF security contact;
- Modify data in our systems/services which is not your own;
- Place or insert any kind of malicious code on the system;
- Disrupt our service(s) and/or systems; or
- Disclose any vulnerabilities in ORF systems/services to 3rd parties/the public prior to ORF confirming that those vulnerabilities have been mitigated or rectified. This does not prevent notification of a vulnerability to 3rd parties to whom the vulnerability is directly relevant, for example where the vulnerability being reported is in a software library or framework – but details of the specific vulnerability of ORF must not be referenced in such reports. If you are unsure about the status of a 3rd party to whom you wish to send notification, please e-mail ciso@orf.at for clarification.
- ORF requests that all data retrieved during research is securely deleted as soon as it is no longer required and at most, 1 month after the vulnerability is resolved, whichever occurs sooner.
If you are unsure at any stage whether the actions you are thinking of taking are acceptable, please contact our security team for guidance (please do not include any sensitive information in the initial communications): ciso@orf.at.
Reporting a vulnerability
If you have discovered an issue which you believe is an in-scope security vulnerability (please see section above for more detail on scope), please e-mail ciso@orf.at including:
- The website or page in which the vulnerability exists.
- A brief description of the class (e.g. „XSS vulnerability“) of the vulnerability. Please avoid including any details which would allow reproduction of the issue at this stage. Detail will be requested subsequently, over encrypted communications.
In accordance with industry convention, we ask that reporters provide a benign (i.e. non-destructive) proof of exploitation wherever possible. This helps to ensure that the report can be triaged quickly and accurately whilst also reducing the likelihood of duplicate reports and/or malicious exploitation for some vulnerability classes (e.g. sub-domain takeovers).
Please ensure that you do not send your proof of exploit in the initial, plaintext email if the vulnerability is still exploitable. Please also ensure that all proof of exploits is in accordance with our guidance (below), if you are in any doubt, please e-mail ciso@orf.at for advice.
Please read this document fully prior to reporting any vulnerabilities to ensure that you understand the policy and can act in compliance with it.
What to expect
In response to your initial e-mail to ciso@orf.at you will receive an acknowledgement e-mail from ORF Security Team, usually within 72 hours of your report being received. The acknowledgment e-mail will include a ticket reference number that you can quote in any further communications with our Security Team.
A secure communication channel (e.g. S/MIME, PGP,...) is defined in the confirmation e-mail by ORF, which you can use for future messages containing sensitive information. Following the initial contact, our Security Team will work to triage the reported vulnerability and will respond to you as soon as possible to confirm whether further information is required and/or whether the vulnerability qualifies as per the above scope or is a duplicate report.
From this point, necessary remediation work will be assigned to the appropriate ORF teams and/or supplier(s). Priority for bug fixes and/or mitigations will be assigned based on the severity of impact and complexity of exploitation. Vulnerability reports may take some time to triage and/or remediate; you are welcome to enquire on the status of the process but please limit this to no more than once every 14 days, this helps our Security team focus on the reports as much as possible. Our Security Team will notify you when the reported vulnerability is resolved (or remediation work is scheduled) and will ask you to confirm that the solution covers the vulnerability adequately.
We will offer you the opportunity to feed back to us on the process and relationship as well as the vulnerability resolution. This information will be used in strict confidence to help us improve the way in which we handle reports and/or develop services and resolve vulnerabilities. We will also offer to include reporters of qualifying vulnerabilities on our acknowledgments page and we'll ask for the details you wish to be included.
Legal Framework
This policy is designed to be compatible with common good practice among well-intentioned security researchers. It does not give you permission to act in any manner that is inconsistent with the law or cause the ORF to be in breach of any of its legal obligations, including but not limited to:
- The General Data Protection Regulation 2016/679 (GDPR) and the Data Protection Act 2018
- Austrian Data Protection Act
- Austrian Telecommunications Act 2021
ORF will not seek prosecution of any security researcher who reports in good faith and in accordance with this policy, any security vulnerability on an in-scope ORF service.
Hall of Fame
Researcher: | Date: | Vulnerability: |
---|---|---|
Jack Liam | 01/2024 | Security Misconfiguration |
Saran SENGOTTUVEL | 07/2024 | Security Misconfiguration |
Harald Schmal | 11/2024 | Security Misconfiguration |
Mirza Sanaullah | 12/2024 | Security Misconfiguration |