By participating in this program, you agree to:

• Respect the Community Code of Conduct
• Respect the Intigriti Terms and Conditions
• Respect the scope of the program
• Not discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)

We kindly ask you to not:

• Use automated scanning tools
• Change any accounts passwords
• Access or download confidential information
• Perform any test that will impact our costumers
• Share or publicize an unresolved vulnerability with/to third parties.

Azena Commitment

Azena agrees not to pursue claims against reporting parties related to disclosures submitted to us providing the following:

• The reporting party does not cause harm to Azena, our customers, or others.
• The reporting party does not compromise the privacy or safety of our customers or the operation of our services.
• The reporting party does not violate any criminal law.
• The reporting party publicly discloses vulnerability details only after Azena confirms completed remediation of the vulnerability

We want to give everyone the chance to get in contact with us regarding the security of our platform and are happy to announce our responsible disclosure program!
We've done our best to clean most of our known issues and now would like to request your help to spot the ones we missed!

Domains

• Any domain that is not listed in the Domains section, is out of scope for this program
• Specifically, connect.azena.com and it's subdomains point to third party devices and do not fall under this program.

General

• Signing up to the Azena platform (registration is limited to companies and requires a valid VAT ID - you'd need to provide fake information which is out of scope).
• In case that a reported vulnerability was already known to the company from their own tests, it will be flagged as a duplicate
• Theoretical security issues with no realistic exploit scenario(s) or attack surfaces, or issues that would require complex end user interactions to be exploited
• Spam, social engineering and physical intrusion
• DoS/DDoS attacks or brute force attacks
• Vulnerabilities that only work on software that no longer receive security updates
• Attacks requiring physical access to a victim's computer/device, man in the middle or compromised user accounts
• Recently discovered zero-day vulnerabilities found in in-scope assets within 14 days after the public release of a patch or mitigation may be reported, but are usually not eligible for a bounty
• Reports that state that software is out of date/vulnerable without a proof-of-concept

Application

• API key disclosure without proven business impact
• Wordpress usernames disclosure
• Pre-Auth Account takeover/OAuth squatting
• Self-XSS that cannot be used to exploit other users
• Verbose messages/files/directory listings without disclosing any sensitive information
• CORS misconfiguration on non-sensitive endpoints
• Missing cookie flags
• Missing security headers
• Cross-site Request Forgery with no or low impact
• Presence of autocomplete attribute on web forms
• Reverse tabnabbing
• Bypassing rate-limits or the non-existence of rate-limits.
• Best practices violations (password complexity, expiration, re-use, etc.)
• Clickjacking without proven impact/unrealistic user interaction
• CSV Injection
• Sessions not being invalidated (logout, enabling 2FA, etc.)
• Tokens leaked to third parties
• Anything related to email spoofing, SPF, DMARC or DKIM
• Content injection without being able to modify the HTML
• Username/email enumeration
• Email bombing
• HTTP Request smuggling without any proven impact
• Homograph attacks
• XMLRPC enabled
• Banner grabbing/Version disclosure
• Not stripping metadata of files
• Same-site scripting
• Subdomain takeover without taking over the subdomain
• Arbitrary file upload without proof of the existence of the uploaded file
• Blind SSRF without proven business impact (pingbacks are not sufficient)
• Disclosed/misconfigured Google Maps API keys
• Host header injection without proven business impact

This program follows Intigriti's contextual CVSS standard

Where can we get credentials for the app?

We currently don’t offer any credentials to test user roles.