A flaw was found in cockpit-machines. Saving VNC console settings passes the configured password through virtXmlEdit() and runVirtXml() into a virt-xml --graphics command-line argument. A local unprivileged attacker on a host permitting cross-user process inspection can read the password while another user saves the settings. Because the dialog also submits an existing password when other settings are changed, changing only the console port can expose the credential again. A disclosed password may allow unauthorized access to a guest's VNC console when the console is active, reachable, and accepts that password. Loopback-only listening does not by itself prevent access by a local attacker.

A flaw was found in cockpit-machines. Saving VNC console settings passes the configured password through virtXmlEdit() and runVirtXml() into a virt-xml --graphics command-line argument. A local unprivileged attacker on a host permitting cross-user process inspection can read the password while another user saves the settings. Because the dialog also submits an existing password when other settings are changed, changing only the console port can expose the credential again. A disclosed password may allow unauthorized access to a guest's VNC console when the console is active, reachable, and accepts that password. Loopback-only listening does not by itself prevent access by a local attacker.

Cockpit CMS 2.14.1 contains an observable timing discrepancy vulnerability that allows unauthenticated attackers to enumerate accounts due to an incomplete timing fix in /auth/check. Attackers can post login attempts and measure response times, since existing accounts incur two bcrypt operations versus one, revealing valid usernames and email addresses.

Cockpit CMS 2.12.0 before 2.14.1 disables TLS certificate verification in the cron.php web worker restart request, allowing network attackers to capture the worker token. Man-in-the-middle attackers on the outbound path to siteurl can present any certificate to steal the worker/web/token value and start the web worker.

A flaw was found in Cockpit. An unauthenticated remote attacker can exploit this vulnerability by initiating and sustaining numerous simultaneous connections to the cockpit-tls service. This forces the service to create an unbounded number of detached threads, consuming system resources such as memory and file descriptors. The primary consequence is a denial of service (DoS), leading to degradation or complete unavailability of the Cockpit service for legitimate users.

Cockpit 2.13.5 and earlier is vulnerable to directory traversal via the Buckets component. This vulnerability allows authenticated attackers to write files to arbitrary locations within the uploads directory or overwrite assets with malicious versions.

Cockpit 2.13.5 and earlier is affected by a misconfiguration within the Bucket component isFileTypeAllowed function where a specially crafted filename bypasses an extension filter. This allows an authenticated attacker to rename arbitrary files with the .php file extension enabling arbitrary code to be executed on the underlying server.

A vulnerability was found in Cockpit up to 2.11.3. It has been rated as problematic. This issue affects some unknown processing of the file /system/users/save. The manipulation of the argument name/email leads to cross site scripting. The attack may be initiated remotely. Upgrading to version 2.11.4 is able to address this issue. The patch is named bdcd5e3bc651c0839c7eea807f3eb6af856dbc76. It is recommended to upgrade the affected component. The vendor was contacted early about this disclosure and acted very professional. A patch and new release was made available very quickly.

A flaw was found in the cockpit package. This flaw allows an authenticated user to kill any process when enabling the pamenv's userreadenv option, which leads to a denial of service (DoS) attack.

Cockpit (and its plugins) do not seem to protect itself against clickjacking : it is possible to render a page from a cockpit server via another website, inside an <iFrame> HTML entry.

This may be used by a malicious website in clickjacking, or similar, attacks.

To prevent this behavior, a X-Frame-Options header could be added to the responses.