CVE-2024-34455VulnerabilityPublished 3 May 2024Updated 2 Aug 2024

CVE-2024-34455: buildroot · n/a

Affects buildrootSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 2024.02.2 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2024.02.2

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 May 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade buildroot/buildroot to 2024.02.2.

Affected software

Product	Affected	Fixed in
GitHubbuildroot/buildroot`pkg:github/buildroot/buildroot`Other threats	Affected <2024.02.2	Fixed in 2024.02.2

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-34455, organizations should immediately upgrade to Buildroot version 2024.02.2 or later, which includes the fix that properly sets the sticky bit on the /dev/shm directory. For existing deployments where upgrading firmware is not immediately feasible, administrators should manually verify and correct the permissions of /dev/shm by setting the sticky bit (chmod 1777 /dev/shm) during system initialization. Implement network segmentation and access controls to limit exposure of embedded devices and reduce the attack surface. Monitor systems for unusual file deletions or renaming activities within /dev/shm. Employ runtime integrity monitoring tools to detect unauthorized permission changes. Additionally, review and harden other default permissions in the embedded environment to prevent similar misconfigurations. Regularly audit embedded device firmware and configurations for compliance with security best practices. Finally, maintain an inventory of devices using Buildroot to prioritize patching and mitigation efforts.

Description

Buildroot before 0b2967e lacks the sticky bit for the /dev/shm directory. A fix was released in 2024.02.2.

Impact

The primary impact of CVE-2024-34455 is the potential unauthorized deletion or renaming of files in the /dev/shm directory, which can lead to confidentiality breaches. Since /dev/shm is used for shared memory, sensitive information or inter-process communication data could be exposed or disrupted. Although integrity and availability are not directly impacted, the loss or manipulation of shared memory files can cause application errors or data leakage. The vulnerability is exploitable remotely without authentication or user interaction, increasing the risk of widespread exploitation if attackers gain network access to affected devices. Embedded systems, IoT devices, and network appliances built with vulnerable Buildroot versions are at risk, potentially affecting critical infrastructure, industrial control systems, and consumer electronics. The lack of the sticky bit can facilitate privilege escalation or lateral movement within compromised environments. Organizations using Buildroot-based firmware should consider this vulnerability a high risk due to the ease of exploitation and the sensitive nature of shared memory data.

CWE-276Incorrect Default Permissions (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
During installation, installed file permissions are set to allow anyone to modify those files.
Architecture and Design · Operation
The architecture needs to access and modification attributes for files to only those users who actually require those actions.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Access Control (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
Directory Indexing (opens in a new tab)
Web Server Logs Tampering (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 04:44 UTC

WeaknessesCWE-276

Technical details

References

Community reviews

Related threats