GHSA-j224-7qr4-8646 CVE-2019-17104
Centreon Does Not Set HTTPOnly Flag
- Severity
- 7.5 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 1.94%
- Chance of exploitation in the next 30 days. Higher than 80.16% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-565 Reliance on Cookies without Validation and Integrity Checking
- Fix
- None yet
- No fixed version published
Description
In Centreon VM through 19.04.3, the cookie configuration within the Apache HTTP Server does not protect against theft because the HTTPOnly flag is not set.
Affected versions
Packagist
| Package | Vulnerable | Fixed in |
|---|---|---|
| centreon/centreon | <= 19.04.3 |
No fix yet |
How to fix
No fixed version has been published yet. Until one is, remove or replace the package, or turn off or isolate the affected feature. This page updates when a fix ships.
Severity breakdown
CVSS 3.1 7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Weakness
CWE-565: Reliance on Cookies without Validation and Integrity Checking
The product relies on the existence or values of cookies when performing security-critical operations, but it does not properly ensure that the setting is valid for the associated user.
How to prevent it
- Architecture and Design: Avoid using cookie data for a security-related decision.
- Implementation: Perform thorough input validation (i.e.: server side validation) on the cookie data if you're going to use it for a security related decision.
- Architecture and Design: Add integrity checks to detect tampering.
- Architecture and Design: Protect critical cookies from replay attacks, since cross-site scripting or other attacks may allow attackers to steal a strongly-encrypted cookie that also passes integrity checks. This mitigation applies to cookies that should only be valid during a single transaction or session. By enforcing timeouts, you may limit the scope of an attack. As part of your integrity check, use an unpredictable, server-side value that is not exposed to the client.
References
Advisories
Packages
Other links
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