dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2024-9825

MEDIUM · 5.4 CVSS v3.1 Published 2024-10-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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
The Chef Habitat builder-api on-prem-builder package  with any version lower than habitat/builder-api/10315/20240913162802 is vulnerable to indirect object reference (IDOR) by un-authorized deletion of personal token.  Habitat builder consumes builder-api habitat package as a dependency and the vulnerability was specifically due to builder-api habitat package. The fix was made available in habitat/builder-api/10315/20240913162802 and all the subsequent versions after that. We would recommend user to always use on-prem stable channel.

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

This is an Insecure Direct Object Reference (IDOR) vulnerability in the Chef Habitat builder-api package. An unauthorized attacker can delete personal access tokens belonging to other users by directly referencing those token objects without proper authorization checks. The vulnerability exists specifically in the builder-api habitat package dependency used by the Habitat builder.

MitigationUpgrade the habitat/builder-api package to version 10315/20240913162802 or later, or ensure the on-prem-builder uses the stable channel to receive automatic updates.

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
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

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

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 Habitat builder-api is deployed
    Identify if the Chef Habitat builder service is running in your environment. Check for processes or containers named 'builder-api' or look for the Habitat builder service endpoint.
    Affected if builder-api package is not running in your environment (not affected)
  2. Determine builder-api package version
    Run 'hab pkg version <builder-api-package-ident>' or check the package metadata if you have CLI access to the Habitat installation hosting the builder. Alternatively, query the builder-api /info endpoint if accessible.
    Affected if version is earlier than 10315 or build timestamp before 20240913162802
  3. Verify personal access tokens feature is enabled
    Check if the Habitat builder has user accounts with personal access tokens configured. Query the builder-api for existing tokens via authenticated API or review builder configuration for token storage.
    Affected if personal access tokens are created and stored in the builder system
  4. Check API authorization controls
    Review builder-api access logs or test token deletion API endpoints (DELETE /api/v1/user/tokens/<token_id>) with a low-privilege or unauthorized user account to verify if authorization is enforced.
    Affected if unauthorized users can delete tokens belonging to other users

Your environment is affected if the Habitat builder-api package is deployed with a version earlier than 10315 (or build before 20240913162802) and the personal access tokens feature is enabled, allowing unauthorized token deletion.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the habitat/builder-api package to version 10315/20240913162802 or later, or ensure the on-prem-builder uses the stable channel to receive automatic updates.

Recommended fix High confidence

habitat/builder-api/10315/20240913162802 or later (use on-prem stable channel)

  1. Identify the current version of the habitat/builder-api package in your on-prem-builder installation
  2. Upgrade the habitat/builder-api package to version habitat/builder-api/10315/20240913162802 or any subsequent version
  3. If using habitat package manager, run: hab pkg update && hab pkg upgrade origin/builder-api
  4. Alternatively, upgrade to the latest version available in the on-prem stable channel as recommended by the vendor
  5. Verify the upgrade was successful by checking the builder-api package version
  6. Test that the builder-api service is running correctly after the upgrade

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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