# How to Report a Vulnerability

> Responsible process for reporting security vulnerabilities in iDempiere

This page is part of the list of contribution paths described in [Contributing to iDempiere](./contributing-to-idempiere).

Security is a serious issue, and iDempiere follows a responsible approach to report, fix, and disclose vulnerabilities in a way that protects the community worldwide.

## Responsible disclosure

If you discover a vulnerability in iDempiere, please follow a phased disclosure approach before making details public.

The goal of phased disclosure is to give users and maintainers a reasonable maintenance window to apply updates and reduce rushed operational risk.

## How to report

If you find a vulnerability, send an email to:

`security at idempiere dot com`

Include the following information in your report:

- full version details
- clear reproduction steps
- impact of the vulnerability on the affected system
- any additional details that help verification
- whether you want coordination with the iDempiere security team for disclosure timing

## What happens next

All vulnerability reports sent to this email address are treated as public knowledge and trigger the vulnerability management process described below.

:::note
This is the process the community expects responsible contributors to follow. Anyone can still choose to disclose a vulnerability publicly, for example on a blog, but following this process is appreciated.
:::

## Vulnerability management process

The process has three phases.

### Phase 1: reporting, validation and replication

1. The finder (internal or external) reports the issue as described above.
2. The security team acknowledges the report.
3. The team validates the report.
4. The team assesses the status of the issue.
5. The team replicates the issue.
6. The team calculates the CVSS score.

To calculate the CVSS score, use the public [CVSS v2 calculator](http://nvd.nist.gov/cvss.cfm?calculator&adv&version=2). The [CVSS v2 guide](https://www.first.org/cvss/v2/guide) explains how to fill in the calculator values.

### Phase 2: resolution

Developers work on a solution for the vulnerability. This can be a workaround, a patch or a fix.

At this stage, developers on the security mailing list can decide to work closely with the finder and other key developers of the community.

### Phase 3: responsible disclosure

Disclosure happens in phases. Increasingly larger groups are notified until the final phase of general public disclosure.

The goal is to give users time to upgrade within a reasonable maintenance window. This avoids rushed action and operational anxiety.

iDempiere is an open source project, so the vulnerability management process is published for all vendors and users.

#### Level one

Key contributors, including the responsible finder, receive a formal notice and a pre-release code snapshot. This happens as far in advance as possible, and at least five business days before the public disclosure.

#### Level two

Software forum subscribers and global security organizations receive written notice about 24 hours before the planned public disclosure and code release.

#### Level three

The vulnerability is disclosed to the general public and patched versions are released.
