GHSA-7rg4-266c-jqw6 CVE-2021-28055
Predictable CSRF tokens in centreon/centreon
Medium
Packagist
- Severity
- 6.5 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.82%
- Chance of exploitation in the next 30 days. Higher than 57.35% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Fix
20.10.7- Upgrade centreon/centreon to this version or later
Description
An issue was discovered in Centreon-Web in Centreon Platform 20.10.0. The anti-CSRF token generation is predictable, which might allow CSRF attacks that add an admin user.
Affected versions
Packagist
| Package | Vulnerable | Fixed in |
|---|---|---|
| centreon/centreon | >= 20.10.0, < 20.10.7 |
20.10.7 |
| centreon/centreon | >= 20.04.0, < 20.04.13 |
20.04.13 |
| centreon/centreon | >= 19.10.0, < 19.10.23 |
19.10.23 |
| centreon/centreon | < 2.8.37 |
2.8.37 |
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 → 20.10.7
- composer
composer require centreon/centreon:^20.10.7
Severity breakdown
CVSS 3.1 6.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
Weakness
CWE-330: Use of Insufficiently Random Values
The product uses insufficiently random numbers or values in a security context that depends on unpredictable numbers.
How to prevent it
- Architecture and Design: Use a well-vetted algorithm that is currently considered to be strong by experts in the field, and select well-tested implementations with adequate length seeds. In general, if a pseudo-random number generator is not advertised as being cryptographically secure, then it is probably a statistical PRNG and should not be used in security-sensitive contexts. Pseudo-random number generators can produce predictable numbers if the generator is known and the seed can be guessed. A 256-bit seed is a good starting point for producing a "random enough" number.
- Implementation: Consider a PRNG that re-seeds itself as needed from high quality pseudo-random output sources, such as hardware devices.
- Architecture and Design, Requirements: Use products or modules that conform to FIPS 140-2 [REF-267] to avoid obvious entropy problems. Consult FIPS 140-2 Annex C ("Approved Random Number Generators").
CWE-352: Cross-Site Request Forgery (CSRF)
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
How to prevent it
- Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. For example, use anti-CSRF packages such as the OWASP CSRFGuard. [REF-330] Another example is the ESAPI Session Management control, which includes a component for CSRF. [REF-45]
- Implementation: Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
- Architecture and Design: Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330). [REF-332]
- Architecture and Design: Identify especially dangerous operations. When the user performs a dangerous operation, send a separate confirmation request to ensure that the user intended to perform that operation.
- Architecture and Design: Use the "double-submitted cookie" method as described by Felten and Zeller: When a user visits a site, the site should generate a pseudorandom value and set it as a cookie on the user's machine. The site should require every form submission to include this value as a form value and also as a cookie value. When a POST request is sent to the site, the request should only be considered valid if the form value and the cookie value are the same. Because of the same-origin policy, an attacker cannot read or modify the value stored in the cookie. To successfully submit a form on behalf of the user, the attacker would have to correctly guess the pseudorandom value. If the pseudorandom value is cryptographically strong, this will be prohibitively difficult. This technique requires Javascript, so it may not work for browsers that have Javascript disabled. [REF-331]
- Architecture and Design: Do not use the GET method for any request that triggers a state change.
- Implementation: Check the HTTP Referer header to see if the request originated from an expected page. This could break legitimate functionality, because users or proxies may have disabled sending the Referer for privacy reasons.
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