dbcve.org
YoctoApplication · Linuxfoundation

CVE-2024-25626

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-19
Fix available
A fix is available. Upgrade to 3.1.31 / 4.0.16 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Yocto Project's Bitbake contains a missing input validation vulnerability in its Toaster server component. An unauthenticated attacker can achieve remote code execution on the server by sending a crafted HTTP request to the Toaster server. The Toaster server is not enabled by default in CLI builds and only runs when the Toaster web-based UI is used.

MitigationUpgrade Bitbake to version 2.6.2 or later, or apply the backported patches for Yocto Project versions 5.0, 3.1.31, 4.0.16, or 4.3.2. If Toaster server is not required, ensure it is not running.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
YoctoApplication
Affected:< 3.1.31>= 3.2, < 4.0.16>= 4.1, < 4.3.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify if Toaster web UI server is running
    Check whether the Toaster server process or service is active on your system. This may be visible in running processes, systemd services, or by checking if port 8000 (or configured Toaster port) is listening.
    Affected if The Toaster server is actively running and accessible via network
  2. Identify installed Bitbake version
    Run 'bitbake --version' or check the Bitbake package/version metadata in your Yocto build environment to determine the exact version number.
    Affected if The installed version is < 3.1.31, OR >= 3.2 and < 4.0.16, OR >= 4.1 and < 4.3.2
  3. Confirm Toaster is enabled in build configuration
    Inspect your build configuration (local.conf or bblayers.conf) for variables or settings that enable the Toaster web interface (such as INHERIT += 'toaster' or equivalent Toaster-enabling flags).
    Affected if Toaster is explicitly enabled in your build configuration
  4. Check for exposed Toaster web interface
    Verify network accessibility of the Toaster web server by testing connectivity to its HTTP port from untrusted networks or confirming it binds to non-loopback interfaces.
    Affected if Toaster server is reachable from network locations that should not have access

You are affected if the Toaster web UI server is running AND your Bitbake version falls within any of the affected ranges (< 3.1.31, >= 3.2 to < 4.0.16, or >= 4.1 to < 4.3.2).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.1.31 / 4.0.16 / 4.3.2 or later
Fixed in 3.1.314.0.164.3.2
Interim mitigation

Upgrade Bitbake to version 2.6.2 or later, or apply the backported patches for Yocto Project versions 5.0, 3.1.31, 4.0.16, or 4.3.2. If Toaster server is not required, ensure it is not running.

Recommended fix High confidence

Upgrade to Yocto 3.1.31, 4.0.16, 4.3.2, or 5.0+ (choose based on compatibility with your existing build system)

  1. 1. Determine if the Toaster server is in use (it is not enabled by default for Bitbake command line builds)
  2. 2. Identify the current Yocto/Bitbake version in use from the affected version ranges
  3. 3. Upgrade to one of the fixed versions: 3.1.31, 4.0.16, 4.3.2, or 5.0 (or later) depending on your compatibility requirements
  4. 4. After upgrade, verify the Bitbake version matches the target fixed release
  5. 5. If Toaster was in use, restart the Toaster server with the updated version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Yocto Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-25626 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-25626 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data