Vulnerability Reporting

Help us keep the MPoC platform secure. Report responsibly, we respond within 7 business days.


What to Report

Report any security vulnerabilities or concerns related to the MPoC Software, including but not limited to:

  • Authentication issues
  • Authorization flaws
  • Data leakage or exposure
  • Cryptographic vulnerabilities
  • Injection attacks
  • Mobile application issues

Responsible Disclosure Policy

We follow a responsible disclosure policy and appreciate your cooperation. Key guidelines:

  • Report vulnerabilities only through the provided channels on this page.
  • Allow reasonable time for us to investigate and address the reported issue before any public disclosure.
  • Do not disclose or exploit any vulnerabilities without explicit consent from Infibeam Avenues Ltd.

Legal Protections

Infibeam Avenues is committed to protecting the rights of security researchers who responsibly disclose vulnerabilities. We will not take legal action against individuals who adhere to our responsible disclosure policy.

Acknowledgment & Communication

We value the efforts of security researchers and will acknowledge receipt of your report within 7 business days. We will keep you informed about the status and resolution of the reported issue.

Report a Vulnerability

Secure submission — encrypted in transit

Your report is sent securely to the Infibeam Avenues security team.

Inclusion & Exclusion Criteria

How we evaluate and prioritise reported vulnerabilities

Inclusion Criteria
Common Vulnerabilities (CVEs)Vulnerabilities listed in the National Vulnerability Database (NVD) and other recognised databases.
Security AdvisoriesVulnerabilities reported in official advisories from software vendors or reliable sources.
Severity LevelIssues with a severity level that poses a credible threat to Infibeam Avenues systems, data, or operations.
Relevance to EnvironmentVulnerabilities applicable to specific software versions and configurations used by Infibeam Avenues.
CIA ImpactIssues with significant impact on confidentiality, integrity, or availability of systems and data.
Known ExploitsVulnerabilities with known exploits or active threats in the wild.
Compliance ViolationsIssues that may lead to violations of regulatory compliance requirements.
Vendor AcknowledgmentVulnerabilities acknowledged by the COTS vendor, especially where a patch or mitigation is available.
Exclusion Criteria
False PositivesVulnerabilities identified as false positives after thorough investigation and verification.
Non-ApplicableVulnerabilities not applicable to Infibeam Avenues specific software and hardware configurations.
Low-Impact IssuesLow severity vulnerabilities that do not pose a significant risk to operations.
Unsupported SoftwareVulnerabilities in officially unsupported or legacy software components where upgrading is not feasible.
Known MitigationsVulnerabilities for which effective mitigations are already in place or can be readily implemented.
Patch PendingVulnerabilities where a vendor has acknowledged the issue and a patch is pending within an acceptable timeframe.
Low Exploit ProbabilityVulnerabilities with a low probability of exploitation in the specific Infibeam Avenues environment.
Insignificant ImpactVulnerabilities with insignificant impact on confidentiality, integrity, and availability of systems.