GHSA-h5qv-p378-3hhr CVE-2020-10945
Centreon Sensitive Data Exposure vulnerability
Medium
Packagist
- Severity
- 4.3 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.56%
- Chance of exploitation in the next 30 days. Higher than 46.50% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Fix
19.10.7- Upgrade centreon/centreon to this version or later
Description
Centreon before 19.10.7 exposes Session IDs in server responses.
Affected versions
Packagist
| Package | Vulnerable | Fixed in |
|---|---|---|
| centreon/centreon | >= 19.10.0, < 19.10.7 |
19.10.7 |
| centreon/centreon | >= 19.0.0, < 19.04.10 |
19.04.10 |
| centreon/centreon | >= 18.0.0, < 18.10.11 |
18.10.11 |
| centreon/centreon | < 2.8.32 |
2.8.32 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
centreon/centreon Packagist → 19.10.7
- composer
composer require centreon/centreon:^19.10.7
Severity breakdown
CVSS 3.1 4.3
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Weakness
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
How to prevent it
- Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
References
Advisories
Packages
Other links
- github.com/centreon/centreon-archived/pull/8291
- github.com/centreon/centreon-archived/commit/02a3248602ce194fbb098af34be4652565…
- github.com/centreon/centreon-archived/commit/1c14a8ee07225836bdd2ca480e47a63070…
- github.com/centreon/centreon-archived/commit/afa0ee6d43d22860ae4351635599126965…
- github.com/centreon/centreon-archived/commit/fbee38536960eecaf52eda2bf31b90859c…
- web.archive.org/web/20200625084841/https://sysdream.com/news/lab/2020-05-13-cve-2020…
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-626r-cj47-p49g Centreon insertGraphTemplate SQL Injection Remote Code Execution Vulnerability | High | Also affects centreon/centreon |
| GHSA-2j4g-v4fv-rhwg Centreon updateContactHostCommands SQL Injection Remote Code Execution Vulnerability | High | Also affects centreon/centreon |
| GHSA-j8hg-v5qv-9m28 Centreon updateContactServiceCommands SQL Injection Remote Code Execution Vulnerability | High | Also affects centreon/centreon |
| GHSA-j4pc-vqvc-4p9x Centreon updateLCARelation SQL Injection Remote Code Execution Vulnerability | High | Also affects centreon/centreon |
| GHSA-qjvm-p5vg-437c Centreon updateGroups SQL Injection Remote Code Execution Vulnerability | High | Also affects centreon/centreon |
| GHSA-22v7-v3mj-pm8r Centreon updateDirectory SQL Injection Remote Code Execution Vulnerability | High | Also affects centreon/centreon |
| GHSA-j5wx-jvw3-j363 Centreon vulnerable to SQL Injection | Critical | Also affects centreon/centreon |
| GHSA-rv5q-72p2-2q24 Centreon contains cross-site scripting vulnerability via esc_name parameter | Medium | Also affects centreon/centreon |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor