GHSA-86rf-38v8-9c4x CVE-2023-0759
privilege chaining in cockpit-hq/cockpit
- Severity
- 8.8 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 0.34%
- Chance of exploitation in the next 30 days. Higher than 27.97% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-268 Privilege Chaining
- Fix
2.3.8- Upgrade cockpit-hq/cockpit to this version or later
Description
Privilege Chaining in GitHub repository cockpit-hq/cockpit prior to 2.3.8.
Affected versions
Packagist
| Package | Vulnerable | Fixed in |
|---|---|---|
| cockpit-hq/cockpit | < 2.3.8 |
2.3.8 |
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.
cockpit-hq/cockpit Packagist → 2.3.8
- composer
composer require cockpit-hq/cockpit:^2.3.8
Severity breakdown
CVSS 3.1 8.8
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Weakness
CWE-268: Privilege Chaining
Two distinct privileges, roles, capabilities, or rights can be combined in a way that allows an entity to perform unsafe actions that would not be allowed without that combination.
How to prevent it
- Architecture and Design: Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
- Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Architecture and Design, Operation: Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-ch4j-vcf5-58x5 Cockpit CMS: Stored cross-site scripting vulnerability in the Set field type's Display template option | Medium | Also affects cockpit-hq/cockpit |
| GHSA-p46p-7pmj-m34f Cockpit is vulnerable to directory traversal | Medium | Also affects cockpit-hq/cockpit |
| GHSA-j2rx-4jg9-79mw Cockpit Vulnerable to Unrestricted Upload of File with Dangerous Type | High | Also affects cockpit-hq/cockpit |
| GHSA-fm6c-rhcf-7439 Cockpit is vulnerable to arbitrary code execution | Critical | Also affects cockpit-hq/cockpit |
| GHSA-5pv2-86qj-5jf9 Cockpit has NoSQL Injection Through Content Aggregation Pipelines | Medium | Also affects cockpit-hq/cockpit |
| GHSA-7x5c-vfhj-9628 Cockpit CMS has SQL Injection in MongoLite Aggregation Optimizer via toJsonExtractRaw() | Medium | Also affects cockpit-hq/cockpit |
| GHSA-j4rj-fgcq-wmqp Cockpit - Content Platform vulnerable to XSS through name or email argument names | Medium | Also affects cockpit-hq/cockpit |
| GHSA-wp68-xrfg-xvq4 Cockpit Arbitrary File Upload | High | Also affects cockpit-hq/cockpit |
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