Security readout for executives and security teams
Plain-English summary
A logged-in low-privilege local user could chain privileges in cockpit-hq/cockpit before 2.3.8, with limited confidentiality, integrity, and availability impact. This is moderate urgency for organizations running Cockpit, especially where many users can authenticate.
Executive priority
Treat as a targeted privilege-risk cleanup, not an internet-wide emergency. Prioritize upgrade where Cockpit is used by multiple administrators, contractors, or shared operational accounts.
Technical view
CVE-2023-0759 is a CWE-268 privilege chaining issue in cockpit-hq/cockpit before version 2.3.8. The CVSS 3.0 vector is local, low complexity, low privileges required, no user interaction, unchanged scope, with low C/I/A impact.
Likely exposure
Exposure is limited to deployments of cockpit-hq/cockpit running versions before 2.3.8. The provided CVSS vector indicates the attacker needs local access and low privileges, so shared administration environments carry higher practical risk.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Public evidence names the weakness and fix reference, but does not provide complete operational exploitation context.
Researcher notes
Evidence is sparse: the CVE identifies privilege chaining and the pre-2.3.8 affected range, but not detailed prerequisites beyond the CVSS vector. Do not assume remote exploitation, exploit availability, or broader affected products from this bundle.
Mitigation direction
- Upgrade cockpit-hq/cockpit to version 2.3.8 or later.
- Review the linked vendor commit and huntr advisory for implementation context.
- Restrict low-privileged user access to Cockpit deployments until upgraded.
- Check vendor guidance if packaged through a downstream distribution.
Validation and detection
- Inventory cockpit-hq/cockpit deployments and record exact versions.
- Confirm no production instance runs a version before 2.3.8.
- Review local user and role assignments on affected systems.
- Verify change management records include the 2.3.8 remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-268: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2023-0759 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L1.83.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
5.3MediumVector: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Privilege Chaining
Privilege Chaining represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.