DIGI Responsible Disclosure Program
Description
DIGI Communications is a European telecommunications group operating in Romania, Spain, Italy, Portugal, and Belgium, providing mobile and fixed telephony, high-speed internet, and television services under its local brands. The platform enables users to securely access and interact with information associated with their DIGI profile.
Bounties
This is a responsible disclosure program without bounties.
Rules of Engagement
- Automated tooling: max. 10 requests/sec
- 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)
- Safe harbour for researchers is applied
Assets in Scope
*.digi.pt (Wildcard) - No bounty*.digi.it (Wildcard) - No bounty*.digimobil.it (Wildcard) - No bounty*.digi-belgium.be (Wildcard) - No bounty*.digimobil.es (Wildcard) - No bounty*.rcs-rds.ro (Wildcard) - No bounty*.digi.ro (Wildcard) - No bounty
Out of Scope
Introduction
We are happy to announce our program! We've done our best to clean up our known issues and now would like to request your help to spot the ones we missed!
Feedback
Would you like to help us improve our program or have some feedback to share, please send your anonymous feedback here: https://go.intigriti.com/program-feedback
Please note this form will be checked periodically and should not be used for submission or support queries.
Pathway to our private Bug Bounty Program
We value meaningful collaboration with the community. By submitting high-quality reports to our Vulnerability Disclosure Program, you may be invited to join our private Bug Bounty Program that offers: paid bounties for verified vulnerabilities, closer collaboration with our security team.
Out of Scope Issues
Application
- Wordpress usernames disclosure
- Pre-Auth Account takeover/OAuth squatting
- Self-XSS that can't 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 aren't sufficient)
- Disclosed/misconfigured Google Maps API keys
- Host header injection without proven business impact
General
- 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
Mobile
- Shared links leaked through the system clipboard
- Any URIs leaked because a malicious app has permission to view URIs opened
- The absence of certificate pinning
- Sensitive data in URLs/request bodies when protected by TLS
- Lack of obfuscation
- Path disclosure in the binary
- Lack of jailbreak & root detection
- Crashes due to malformed URL Schemes
- Lack of binary protection (anti-debugging) controls, mobile SSL pinning
- Snapshot/Pasteboard leakage
- Runtime hacking exploits (exploits only possible in a jailbroken environment)
- API key leakage used for insensitive activities/actions
Severity Assessment
This program follows Intigriti's triage standards based on the proof of concept.
FAQ
We currently don't offer any credentials to test user roles.
Pathway to our private Bug Bounty Program
We value meaningful collaboration with the community. By submitting high-quality reports to our Vulnerability Disclosure Program, you may be invited to join our private Bug Bounty Program that offers: paid bounties for verified vulnerabilities, closer collaboration with our security team.