Skip to main content
CVE-2024-2947VulnerabilityPublished Updated

CVE-2024-2947: cockpit · Command Injection

Affects cockpitSource CVE Database V5

0

Not known to be exploited · CVSS 7.3 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
7.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.1% chance of exploitation in 30 days – higher than 67% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Mar 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
Fedorafedora/cockpitpkg:rpm/fedora/cockpitOther threatsAffected
  • =270
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-2947, organizations should: 1) Apply patches or updates from Cockpit maintainers as soon as they become available to address the input sanitization flaw. 2) Restrict access to the Cockpit web interface to trusted administrators only, using network segmentation and firewall rules. 3) Enforce the principle of least privilege by limiting user permissions within Cockpit, preventing unprivileged users from deleting sosreports or performing sensitive actions. 4) Implement input validation and sanitization controls on any custom integrations or scripts interacting with Cockpit to prevent injection of malicious commands. 5) Monitor system logs and Cockpit audit trails for unusual sosreport deletion attempts or command execution patterns. 6) Educate users about the risks of interacting with suspicious filenames or links within the management interface. 7) Consider disabling sosreport deletion via the web interface if not required or restricting it to command-line operations with stricter controls. These measures, combined with timely patching, will reduce the risk of exploitation and limit potential damage.

Description

A flaw was found in Cockpit. Deleting a sosreport with a crafted name via the Cockpit web interface can lead to a command injection vulnerability, resulting in privilege escalation. This issue affects Cockpit versions 270 and newer.

References

Community reviews

Loading reviews…