dbcve.org
OpenafsApplication

CVE-2024-10396

MEDIUM · 6.5 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 →
71/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
An authenticated user can provide a malformed ACL to the fileserver's StoreACL RPC, causing the fileserver to crash, possibly expose uninitialized memory, and possibly store garbage data in the audit log. Malformed ACLs provided in responses to client FetchACL RPCs can cause client processes to crash and possibly expose uninitialized memory into other ACLs stored on the server.

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 an ACL (Access Control List) parsing vulnerability in a fileserver component. An authenticated user can send malformed ACL data to the StoreACL RPC, causing server crashes, potential uninitialized memory exposure, and audit log corruption. Conversely, malformed ACLs in FetchACL responses can crash client processes and contaminate server-stored ACLs with uninitialized memory.

MitigationImplement strict validation and bounds checking on all ACL data structures during parsing. Ensure all memory allocations for ACL storage are properly initialized before use, and validate ACL structure integrity before processing or storing.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 OpenAFS version
    Run 'rxstat -version' or check the installed package version via package manager (dpkg -l openafs-fileserver, rpm -q openafs-fileserver, or similar)
    Affected if Installed version falls within >=1.0 to <1.6.25, OR >=1.8.0 to <1.8.13, OR equals 1.9.0
  2. Confirm fileserver component is active
    Check for running bosserver or fileserver processes: 'ps aux | grep -E "(fileserver|bosserver)"'. Also check if port 7000-7007 (typical AFS ports) are listening via 'netstat -tlnp | grep -E "700[0-7]"'
    Affected if Fileserver processes are running and exposed on network ports
  3. Verify RPC service availability
    Check if the StoreACL RPC endpoint is reachable. Use 'bos status <server> -localauth' or examine RPC port listings. For clients, check if FetchACL responses can be received from servers
    Affected if StoreACL RPC is exposed to authenticated users or FetchACL responses are processed by clients
  4. Inspect ACL storage for corruption
    Examine ACL binary data stored on the fileserver. On the server, review any audit logs or debug logs for ACL parsing errors, crashes, or warnings related to 'ACL' or 'StoreACL'. Check for entries indicating memory initialization failures
    Affected if ACL parsing errors appear in logs, or ACL data shows signs of corruption or uninitialized memory patterns

A defender is affected if OpenAFS fileserver or client version matches the vulnerable ranges AND the fileserver component is running with RPC access enabled.

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

Implement strict validation and bounds checking on all ACL data structures during parsing. Ensure all memory allocations for ACL storage are properly initialized before use, and validate ACL structure integrity before processing or storing.

Recommended fix High confidence

OpenAFS 1.8.13 (or 1.6.25 if staying on 1.6 branch)

  1. Identify currently installed OpenAFS version using 'afs_version' command or package manager
  2. For OpenAFS 1.6.x versions (< 1.6.25): Upgrade to version 1.6.25 or later from www.openafs.org or your distribution's package repository
  3. For OpenAFS 1.8.x versions (< 1.8.13): Upgrade to version 1.8.13 or later from www.openafs.org or your distribution's package repository
  4. For OpenAFS 1.9.0: Upgrade to 1.8.13 or later (1.9.x branch has no fix)
  5. After upgrade, restart the OpenAFS client and fileserver services to apply the fix
  6. Verify the fix by checking that the fileserver no longer crashes on malformed ACL inputs
Caveat Minor: Ensure client and server are on compatible versions after upgrade; some older clients may need updating to work with patched servers

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

Fix this in Openafs Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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