Skip to content

← Actionable
Medium, CVSS 4.3

Centreon Sensitive Data Exposure vulnerability

CVE-2020-10945GHSA-h5qv-p378-3hhr

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (centreon/centreon 19.10.7, 19.04.10, 18.10.11, 2.8.32), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • Packagist centreon/centreon

    Affected
    >= 19.10.0, < 19.10.7>= 19.0.0, < 19.04.10>= 18.0.0, < 18.10.11< 2.8.32
    Fixed in
    2.8.32, 18.10.11, 19.04.10, 19.10.7

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
4.3 · CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
  • CVE-2020-10945: 0.56% estimated exploitation activity in the next 30 days; percentile 46.53 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Centreon before 19.10.7 exposes Session IDs in server responses.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-h5qv-p378-3hhr

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-10945

Advisory: Centreon Sensitive Data Exposure vulnerability
IDs: CVE-2020-10945, GHSA-h5qv-p378-3hhr
Record: https://patchnext.com/advisories/cve-2020-10945 (revision 1, source checked 26 Oct 2026, 14:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: centreon/centreon 19.10.7, 19.04.10, 18.10.11, 2.8.32. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist centreon/centreon: affected >= 19.10.0, < 19.10.7; >= 19.0.0, < 19.04.10; >= 18.0.0, < 18.10.11; < 2.8.32; fixed in 2.8.32, 18.10.11, 19.04.10, 19.10.7

## Suggested inspection (read-only)
- Packagist centreon/centreon: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on centreon/centreon.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-h5qv-p378-3hhr (GitHub-reviewed advisory GHSA-h5qv-p378-3hhr lists affected ranges: Packagist centreon/centreon >=19.10.0 =19.0.0 =18.0.0 =0 <2.8.32)

Commands are suggestions: review each one before running it.

Loading voting…