dbcve.org
OpenafsApplication

CVE-2024-10397

HIGH · 7.8 CVSS v3.1 Published 2024-11-14
Fix available
A fix is available. Upgrade to 1.6.25 / 1.8.13 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
A malicious server can crash the OpenAFS cache manager and other client utilities, and possibly execute arbitrary code.

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 · moderate confidence

This is a client-side vulnerability in OpenAFS where a malicious or compromised AFS server can send specially crafted responses that crash the cache manager and client utilities, and potentially achieve arbitrary code execution on the client system. This suggests a memory corruption vulnerability in how the OpenAFS client handles server responses.

MitigationDeploy the vendor patch/updated version of OpenAFS client software once released. Until then, restrict client connections to trusted AFS servers and monitor for suspicious server behavior.

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
OpenafsApplication
Affected:>= 1.0, < 1.6.25>= 1.8.0, < 1.8.13= 1.9.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. Identify installed OpenAFS version
    Run 'fs -version' or 'rxdebug -version' to retrieve the client version, or query the system package manager (dpkg -l openafs-client, rpm -q openafs, etc.)
    Affected if The version falls within the ranges: 1.0 through 1.6.24, 1.8.0 through 1.8.12, or exactly 1.9.0
  2. Confirm AFS client service is active
    Check if the AFS cache manager process (afsd) or the OpenAFS client daemon is running using 'ps aux | grep afsd' or 'systemctl status afsd'
    Affected if The AFS client daemon is actively running and communicating with AFS servers
  3. Verify client-to-server communication is enabled
    Inspect the /etc/openafs/ThisCell file to confirm the client is configured to use a cell, or check for mounted AFS volumes using 'df -t afs' or 'fs mountq'
    Affected if The client is configured to mount or access AFS filesystems from potentially untrusted servers
  4. Review client configuration for trusted server list
    Examine /etc/openafs/CellServDB or run 'fs listcells' to see which AFS cells and servers the client is configured to contact
    Affected if The client connects to servers outside of a fully trusted and controlled environment

A user is affected if OpenAFS client is installed with a version matching the vulnerable ranges AND the AFS client service is actively running and configured to connect to AFS servers.

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.6.25 / 1.8.13 or later
Fixed in 1.6.251.8.13
Interim mitigation

Deploy the vendor patch/updated version of OpenAFS client software once released. Until then, restrict client connections to trusted AFS servers and monitor for suspicious server behavior.

Recommended fix High confidence

1.6.25+, 1.8.13+, or 1.9.1+ (depending on your branch)

  1. Identify the currently installed OpenAFS version using 'rpm -q openafs' or 'dpkg -l openafs'
  2. Determine your current release branch (1.6.x, 1.8.x, or 1.9.x)
  3. Upgrade to the next available fixed release in your branch: for 1.6.x upgrade to 1.6.25 or later; for 1.8.x upgrade to 1.8.13 or later; for 1.9.x upgrade to 1.9.1 or later
  4. Install the updated package using your system's package manager (apt-get, yum, dnf, etc.)
  5. Restart the OpenAFS cache manager service (e.g., 'systemctl restart afs' or 'service afs restart')
  6. Verify the installed version matches the expected fixed release

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

Fix this in Openafs Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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