CVE-2015-3283
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 · uneditedOpenAFS before 1.6.13 allows remote attackers to spoof bos commands via unspecified vectors.
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 confidenceOpenAFS before version 1.6.13 contains a vulnerability allowing remote attackers to spoof bos (Basic Overfiling System) commands through unspecified vectors. The bos commands are administrative commands used to control OpenAFS server processes, and the spoofing implies an authentication or integrity bypass in the command pathway.
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<= 1.6.12CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/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 checksWork through these to decide whether this CVE applies to you.
-
Determine OpenAFS server versionRun 'afs_version' command, check package version with 'rpm -q openafs' or 'dpkg -l openafs', or examine the contents of '/usr/vice/etc/ThisCell' and cross-reference with installed binariesAffected if Installed version is 1.6.12 or earlier, or version cannot be determined but OpenAFS server binaries are present
-
Identify if host runs OpenAFS server processesCheck for running bos server process: 'ps aux | grep bos' or check for bos server binary at '/usr/afs/bin/bos' or '/usr/lib/openafs/bos'Affected if The bos server executable exists or the bos process is running on the system
-
Verify bos command availabilityCheck if bos administrative commands are accessible: run 'bos status' or 'bos' without arguments to see available subcommands, typically located in /usr/afs/bin/ or /usr/lib/openafs/Affected if Bos commands are executable and accessible on the system (indicates OpenAFS server functionality is enabled)
-
Check authentication configuration for bosExamine /usr/afs/etc/UserList or authentication configuration files to determine if bos commands rely on the vulnerable authentication pathwayAffected if Bos commands are configured to accept remote administrative connections without additional integrity verification beyond basic authentication
The system is affected if OpenAFS server version is 1.6.12 or earlier AND bos administrative commands are enabled on the host.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade OpenAFS to version 1.6.13 or later to obtain the security patch for this vulnerability.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3283 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-3283 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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