Skip to content

Vulnerability Management Process

Version: 2.1


Choreo Labs treats security vulnerability disclosures with the highest priority and follows a Coordinated Vulnerability Disclosure (CVD) program to ensure they are handled responsibly and consistently. This page outlines the process for receiving, assessing, remediating, and coordinating the disclosure of reported vulnerabilities, including communication with affected customers, security researchers, and the broader public.

Sources

Choreo Labs receives vulnerability information through the following channels:

  • Internal security testing. Continuous scanning of Choreo Labs infrastructure, services, and product versions (both released and under development) using industry-standard tooling.
  • Security mailing lists. Public reporting channels for vulnerabilities in Choreo Labs products and services. Submission requirements are documented in Vulnerability Reporting Guidelines.
  • Customer Support Portal. Confidential reporting channel for Choreo Labs customers with an active subscription.
  • External sources. Third-party security mailing lists, vendor security notifications, and public vulnerability databases.

Raw automated scan reports submitted through the public security mailing lists are not processed; the false-positive rate of automated scanning is too high to make blanket triage useful. Only verified findings with reproduction steps enter the handling process. Submissions from Choreo Labs customers go through the Customer Scan Report Submissions workflow.

Severity Classification

Severity is assigned per the Common Vulnerability Scoring System v3.1 for products listed in the Choreo Labs Support Matrix. The Choreo Labs classification mapping:

Classification CVSS Score
Critical 9.0 to 10.0
High 7.0 to 8.9
Medium 4.0 to 6.9
Low 3.9 or below

Resolution Timeframes

Target resolution windows run from the date a report is confirmed as a true positive.

Classification CVSS Score Target Resolution Time
Critical 9.0 to 10.0 7 days
High 7.0 to 8.9 14 days
Medium 4.0 to 6.9 30 days
Low 3.9 or below Next product release, or at the product team's discretion

For confirmed security breaches or zero-day vulnerabilities, Choreo Labs takes immediate action.

Vulnerability Handling Process

The lifecycle of a reported vulnerability:

  1. Acknowledgement. Choreo Labs acknowledges receipt and creates an internal ticket to track progress.
  2. Routing. The report is treated as high priority and directed to the responsible product or services team.
  3. Evaluation. The product or services team, the product's security champion, and the Platform Security team jointly evaluate the report.
  4. Non-threat. If the report does not constitute a threat to the product or service, Choreo Labs responds with the reasoning.
  5. Confirmed threat. If the report is a real vulnerability, Choreo Labs accepts the issue and proceeds.
  6. Mitigation. The product team identifies a configuration mitigation if one exists, then begins work on a code fix.
  7. ETA for customer reporters. If the reporter is a Choreo Labs customer, an ETA is communicated for the patch on the affected product version.
  8. Coordinated disclosure for non-customer reporters. If the reporter is not a Choreo Labs customer:
    • Identify every product version that needs a fix (see Backport Policy).
    • Estimate the effort to patch each.
    • Set a target date for issuing the fixes to customers.
    • Add a one-month buffer beyond that date for the public announcement.
    • Per Choreo Labs' responsible-disclosure ethics, confirm the public announcement date with the reporter before disclosure.
  9. Patch development. The fix is created.
  10. Internal identifier. Assigned in the format WSO2-<year>-<ticket> (e.g., WSO2-2016-0010).
  11. Security advisory. A security advisory is drafted covering impact and mitigation.
  12. Delivery to customer reporter. If the reporter is a Choreo Labs customer, the patch is delivered directly to that customer.
  13. Delivery to non-customer reporter. If the reporter is not a Choreo Labs customer, the source-code diff is provided on request. The public advisory is published after all customer patches are delivered and the buffer period elapses.

Backport Policy

Security fixes are proactively backported to product versions marked as Available or Deprecated in the Choreo Labs Support Matrix and distributed to customers through Choreo Labs Updates.

Customer Announcements

Once a fix and its security advisory are ready for every affected product version within the backport policy, they are shared with all Choreo Labs customers in the monthly Customer Announcement issued on the last working day of each month.

Adjustments to the monthly cycle:

  • Customer-reported vulnerabilities. The reporting customer receives the fix as soon as it is ready, without waiting for the monthly announcement.
  • Catastrophic vulnerabilities. Fixes are announced to all customers immediately; the monthly cycle is bypassed.

Public Disclosure

After the monthly customer announcement, a four-week buffer allows customers to apply the patches. The vulnerability is then published on the Security Advisories page. The content of the public advisory depends on the CVSS score and whether the latest product version is affected:

  • CVSS ≥ 9.0, latest version affected. A patch release of the product follows the buffer period; the public advisory describes the issue and announces the patch release.
  • CVSS < 9.0, latest version affected. The public advisory describes the issue, available risk mitigations, and the pull-request reference for the fix.
  • Latest version not affected. The public advisory advises community users to update to the latest product version.

Acknowledgements

Security researchers who report vulnerabilities to Choreo Labs are credited on the relevant security advisory and listed on the Security Hall of Fame. Inclusion on either page is subject to the researcher's consent. The full program is documented in the Choreo Labs Security Reward and Acknowledgement Program.

Customer Scan Report Submissions

Choreo Labs customers may submit security scanning reports for analysis. Submission requirements:

  • Reports must be submitted through the Choreo Labs Support Portal.
  • Reports must contain only vulnerabilities in Choreo Labs products or product dependencies, not operating-system, application-runtime, or infrastructure-configuration findings.
  • Each report must cover a single product version.

Supported scanner output formats:

Scanner Name Supported Format
Aqua json
JFrog (jfrogxray) json
Trivy json
Veracode (SAST) xml
Harbor json
Burp Suite xml

Reports from scanners not in the supported list are accepted when converted to the Choreo Labs Common Vulnerability Format and submitted alongside the original output.