CVE-2024-25626: Yocto Project Security Advisory - BitBake/Toaster
Yocto Project is an open source collaboration project that helps developers create custom Linux-based systems regardless of the hardware architecture. In Yocto Projects Bitbake before 2.6.2 (before and included Yocto Project 4.3.1), with the Toaster server (included in bitbake) running, missing input validation allows an attacker to perform a remote code execution in the server's shell via a crafted HTTP request. Authentication is not necessary. Toaster server execution has to be specifically run and is not the default for Bitbake command line builds, it is only used for the Toaster web based user interface to Bitbake. The fix has been backported to the bitbake included with Yocto Project 5.0, 3.1.31, 4.0.16, and 4.3.2.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Yocto Project BitBake/Toasterto a version that resolves this vulnerability.Fixed in 2.6.2 - Upgrade
Upgrade
Yocto Project BitBake/Toasterto a version that resolves this vulnerability.Fixed in 4.3.2 - Upgrade
Upgrade
Yocto Project BitBake/Toasterto a version that resolves this vulnerability.Fixed in 5.0 - Upgrade
Upgrade
Yocto Project BitBake/Toasterto a version that resolves this vulnerability.Fixed in 3.1.31 - Upgrade
Upgrade
Yocto Project BitBake/Toasterto a version that resolves this vulnerability.Fixed in 4.0.16
Event History
Frequently Asked Questions
What is the severity of CVE-2024-25626?
CVE-2024-25626 is classified as a high-severity vulnerability affecting the Yocto Project.
How do I fix CVE-2024-25626?
To fix CVE-2024-25626, you should update Yocto Project Bitbake to version 2.6.2 or later.
What components are affected by CVE-2024-25626?
CVE-2024-25626 affects Yocto Project versions before 4.3.1, including Bitbake 2.6.2 and Toaster server.
Who is impacted by CVE-2024-25626?
Developers using Yocto Project versions prior to 4.3.1 are impacted by CVE-2024-25626.
Is there a workaround for CVE-2024-25626?
There are no known workarounds for CVE-2024-25626; updating to the latest versions is recommended.