Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

CVE-2020-10945 centreon/centreon

MEDIUMFix: centreon/centreon-archived#8291

CVE-2020-10945 is a medium-severity (CVSS 4.3) Information Exposure vulnerability in centreon/centreon. A fix is available for centreon/centreon — see the affected versions and patch details below.

Centreon Sensitive Data Exposure vulnerability

Published
May 24, 2022
Updated
Sep 10, 2026
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Sep 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs47th percentile — riskier than 47% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2020-10945 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

4 pkgs affected
🐘centreon/centreon🐘centreon/centreon🐘centreon/centreon🐘centreon/centreon

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Centreon before 19.10.7 exposes Session IDs in server responses.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistcentreon/centreon19.10.0&&< 19.10.719.10.7composer require centreon/centreon:^19.10.7
🐘Packagistcentreon/centreon19.0.0&&< 19.04.1019.04.10composer require centreon/centreon:^19.04.10
🐘Packagistcentreon/centreon18.0.0&&< 18.10.1118.10.11composer require centreon/centreon:^18.10.11
🐘Packagistcentreon/centreonall versions2.8.32composer require centreon/centreon:^2.8.32

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for centreon/centreon, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update centreon/centreon to 19.10.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-10945 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2020-10945 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2020-10945. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Centreon before 19.10.7 exposes Session IDs in server responses.
O3 Security · Impact-Aware SCA

Is CVE-2020-10945 in your dependencies?

O3 Security finds CVE-2020-10945 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2020-10945: centreon/centreon | O3 Security