# CVE-2020-10945: Centreon Sensitive Data Exposure vulnerability

> Centreon exposes session IDs in server responses, allowing attackers to potentially hijack user sessions and access sensitive data.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-h5qv-p378-3hhr, UBUNTU-CVE-2020-10945

## What is CVE-2020-10945?

CVE-2020-10945 is a medium-severity vulnerability in Centreon Centreon, published on 27 May 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Centreon before 19.10.7 exposes Session IDs in server responses.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2020-10945?

8 open source packages ship an affected version, including centreon/centreon. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `centreon/centreon` | Packagist | All versions | 2.8.32 |
| `centreon/centreon` | Packagist | All versions | 2.8.32 |
| `centreon/centreon` | Packagist | From 18.0.0 | 18.10.11 |
| `centreon/centreon` | Packagist | From 18.0.0 | 18.10.11 |
| `centreon/centreon` | Packagist | From 19.0.0 | 19.04.10 |
| `centreon/centreon` | Packagist | From 19.0.0 | 19.04.10 |
| `centreon/centreon` | Packagist | From 19.10.0 | 19.10.7 |
| `centreon/centreon` | Packagist | From 19.10.0 | 19.10.7 |

Products: Centreon Centreon, Centreon Widget-Host-Monitoring.

## How do I fix CVE-2020-10945?

Upgrade centreon/centreon to a fixed version for your release line: 2.8.32, 18.10.11, 19.04.10 or 19.10.7.

## Is CVE-2020-10945 being exploited?

There is no known exploitation of CVE-2020-10945 in the wild and no public exploit code.

## Other vulnerabilities in Centreon Centreon

- [CVE-2021-37558](https://insights.sbomify.com/CVE-2021-37558/): SQL injection in n/a (critical 9.8)
- [CVE-2019-17647](https://insights.sbomify.com/CVE-2019-17647/): SQL injection in n/a (critical 9.8)
- [CVE-2018-21024](https://insights.sbomify.com/CVE-2018-21024/): File upload in n/a (critical 9.8)
- [CVE-2019-16194](https://insights.sbomify.com/CVE-2019-16194/): SQL injection in Centreon (critical 9.8)
- [CVE-2018-19281](https://insights.sbomify.com/CVE-2018-19281/): Centreon allows SNMP trap SQL Injection (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-10945 and fix it if it is affected.

What it is: CVE-2020-10945 is a medium-severity vulnerability in Centreon Centreon, published on 27 May 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-10945 in the wild and no public exploit code.

Affected packages and fixed versions:
- centreon/centreon (Packagist): affected all versions; fixed in 2.8.32
- centreon/centreon (Packagist): affected all versions; fixed in 2.8.32
- centreon/centreon (Packagist): affected from 18.0.0; fixed in 18.10.11
- centreon/centreon (Packagist): affected from 18.0.0; fixed in 18.10.11
- centreon/centreon (Packagist): affected from 19.0.0; fixed in 19.04.10
- centreon/centreon (Packagist): affected from 19.0.0; fixed in 19.04.10
- centreon/centreon (Packagist): affected from 19.10.0; fixed in 19.10.7
- centreon/centreon (Packagist): affected from 19.10.0; fixed in 19.10.7

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-10945/ (Markdown: https://insights.sbomify.com/CVE-2020-10945/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-10945
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-10945
- OSV: https://osv.dev/vulnerability/CVE-2020-10945

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-10945/
Summaries are generated and may contain mistakes; the official description above is the record.