dbcve.org
OpenafsApplication

CVE-2013-1794

MEDIUM · 6.5 CVSS v2.0 Published 2013-03-14
Fix available
A fix is available. Upgrade to after 1.6.1 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
Buffer overflow in certain client utilities in OpenAFS before 1.6.2 allows remote authenticated users to cause a denial of service (crash) and possibly execute arbitrary code via a long fileserver ACL entry.

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

Buffer overflow in client utilities in OpenAFS before version 1.6.2 allows authenticated remote users to cause denial of service (crash) or potentially execute arbitrary code by sending a long fileserver ACL entry to the affected system.

MitigationUpgrade OpenAFS to version 1.6.2 or later to patch the buffer overflow vulnerability in client utilities.

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.6.1= 1.5.10= 1.5.11= 1.5.12= 1.5.13= 1.5.14= 1.5.15= 1.5.16= 1.5.17= 1.5.18= 1.5.19= 1.5.20

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
Authentication
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:S/C:P/I:P/A:P

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 installed OpenAFS version
    Run 'afsversion' command or check package manager (rpm -q openafs, dpkg -l openafs)
    Affected if Version is 1.5.10 through 1.5.20, or 1.6.1 or earlier (anything below 1.6.2)
  2. Verify fileserver component is running
    Check for fileserver process: 'ps aux | grep fileserver' or check /proc/$(pidof fileserver)/cmdline
    Affected if Fileserver process is running on the system
  3. Confirm client utilities are in use
    Check for OpenAFS client daemon: 'ps aux | grep afsd' or check if /usr/vice/etc/AFSDev file exists
    Affected if AFS client utilities are installed and running
  4. Inspect fileserver ACL handling
    Check fileserver configuration in /usr/afs/etc/FileServer or via 'vos listvldb' to identify fileserver instances
    Affected if Fileserver accepts ACL operations from authenticated users

The system is affected if OpenAFS version is 1.6.1 or earlier (including 1.5.10-1.5.20) and the fileserver component is running and accessible to authenticated users.

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
Upgrade available Upgrade to a release after 1.6.1
Interim mitigation

Upgrade OpenAFS to version 1.6.2 or later to patch the buffer overflow vulnerability in client utilities.

Fix this in Openafs Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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