dbcve.org
AlloyApplication · Grafana

CVE-2024-8975

HIGH · 7.8 CVSS v3.1 Published 2024-09-25
Fix available
A fix is available. Upgrade to 1.3.3 or later.
See remediation →
80/100
Remediation priority · High
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
Unquoted Search Path or Element vulnerability in Grafana Alloy on Windows allows Privilege Escalation from Local User to SYSTEM This issue affects Alloy: before 1.3.3, from 1.4.0-rc.0 through 1.4.0-rc.1.

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

Grafana Alloy on Windows contains an unquoted service path vulnerability where the executable path includes spaces and is not properly quoted. This allows a local attacker to place a malicious executable in an intermediate directory along the path, which Windows will attempt to execute with SYSTEM privileges when the service starts, enabling privilege escalation.

MitigationUpgrade Grafana Alloy to version 1.3.3 or later (or a stable release beyond 1.4.0-rc.1). For existing installations, ensure the service executable path in Windows is properly quoted if an immediate upgrade is not feasible.

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
AlloyApplication
Affected:< 1.3.3= 1.4.0

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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. Check if Grafana Alloy service exists on Windows
    Open Services (services.msc) and look for a service named 'Alloy', or run: sc queryex type= service state= all | findstr /i "Alloy"
    Affected if No Alloy service is found - the vulnerability does not apply
  2. Verify the service executable path is unquoted with spaces
    Run: sc qc Alloy (or check the ImagePath value in Registry at HKLM\SYSTEM\CurrentControlSet\Services\Alloy)
    Affected if The ImagePath value does NOT start and end with quotation marks (") AND the path contains one or more spaces (for example: C:\Program Files\Grafana Alloy\alloy.exe service run) - this indicates an unquoted path vulnerability
  3. Check the installed Grafana Alloy version
    Run: alloy --version (from the Alloy bin directory, typically C:\Program Files\Grafana Alloy\alloy.exe --version)
    Affected if The installed version is lower than 1.3.3 (such as 1.3.0, 1.2.0, etc.) OR the version is exactly 1.4.0 - these versions are affected by the unquoted path issue
  4. Identify vulnerable intermediate directories in the service path
    If the service path is unquoted (e.g., C:\Program Files\Grafana Alloy\alloy.exe), examine each directory in the path: C:\, C:\Program, C:\Program Files, C:\Program Files\Grafana, C:\Program Files\Grafana Alloy
    Affected if A non-admin user can write to any intermediate directory (C:\Program Files\ is typically restricted, but verify with: icacls "C:\Program Files\Grafana") - combined with an unquoted path, this allows privilege escalation

A user is affected if Grafana Alloy is installed as a Windows service with an unquoted executable path containing spaces AND the installed version is < 1.3.3 or = 1.4.0 AND an attacker can place a malicious executable in an intermediate directory along the path.

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 1.3.3 or later
Fixed in 1.3.3
Interim mitigation

Upgrade Grafana Alloy to version 1.3.3 or later (or a stable release beyond 1.4.0-rc.1). For existing installations, ensure the service executable path in Windows is properly quoted if an immediate upgrade is not feasible.

Recommended fix High confidence

Alloy 1.3.3 or later (avoid 1.4.0 which is also vulnerable)

  1. 1. Identify the current Alloy version by running 'alloy --version' or checking the installed binary
  2. 2. On Windows, stop the Alloy service if running (e.g., via Services.msc or 'sc stop alloy')
  3. 3. Download Alloy version 1.3.3 or later from the official Grafana GitHub releases (grafana.com/docs/alloy/release/upgrade/)
  4. 4. Install the new Alloy binary, replacing the existing installation
  5. 5. Start the Alloy service on Windows
  6. 6. Verify the upgrade by running 'alloy --version' and confirming the version is 1.3.3 or later (but not 1.4.0)

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

Fix this in Alloy Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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