dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2024-45798

CRITICAL · 9.9 CVSS v3.1 Published 2024-09-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
arduino-esp32 is an Arduino core for the ESP32, ESP32-S2, ESP32-S3, ESP32-C3, ESP32-C6 and ESP32-H2 microcontrollers. The `arduino-esp32` CI is vulnerable to multiple Poisoned Pipeline Execution (PPE) vulnerabilities. Code injection in `tests_results.yml` workflow (`GHSL-2024-169`) and environment Variable injection (`GHSL-2024-170`). These issue have been addressed but users are advised to verify the contents of the downloaded artifacts.

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

The arduino-esp32 CI/CD pipeline contains multiple Poisoned Pipeline Execution (PPE) vulnerabilities allowing code injection via the tests_results.yml workflow (GHSL-2024-169) and environment variable injection (GHSL-2024-170). These CI vulnerabilities enable attackers to inject malicious code or manipulate environment variables in the pipeline, potentially compromising build artifacts and supply chain integrity.

MitigationUsers should verify the integrity of downloaded artifacts and ensure their CI workflows are updated to the patched version that addresses the code and environment variable injection issues.

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

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Confirm arduino-esp32 usage
    Inspect your project dependencies, submodules, or CI configuration files (such as .gitmodules, platformio.ini, or arduino.json) for references to the arduino-esp32 repository or core
    Affected if Your project depends on or uses the arduino-esp32 core for ESP32 microcontrollers in any capacity
  2. Identify the arduino-esp32 version in use
    Check the version by examining your Git submodule reference, platform manager URL, or board manager installation path. If you have the repository locally, run 'git describe --tags' or 'git tag' to list available tags
    Affected if The installed version predates the patched version that addresses GHSL-2024-169 and GHSL-2024-170 (the vendor advisory contains the specific fixed version)
  3. Locate the tests_results.yml workflow file
    Search for the file at .github/workflows/tests_results.yml within your arduino-esp32 checkout or check if your CI pulls this workflow from the arduino-esp32 repository
    Affected if This workflow file exists in your environment and originates from a vulnerable version of arduino-esp32
  4. Inspect workflow for unsafe variable handling
    Examine the workflow YAML files in .github/workflows/ for use of 'run:' blocks or 'env:' directives that process untrusted input, environment variables from pull requests, or user-contributed parameters without validation
    Affected if Your CI workflows contain 'run:' commands or environment variable usage that processes external input without sanitization

You are affected if your environment incorporates the arduino-esp32 CI/CD pipeline from a version prior to the vendor-patched release, particularly if you execute or reference the tests_results.yml workflow or expose environment variables to unvalidated CI inputs.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Users should verify the integrity of downloaded artifacts and ensure their CI workflows are updated to the patched version that addresses the code and environment variable injection issues.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-45798 — 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-45798 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