dbcve.org
Cifs UtilsApplication · Debian

CVE-2014-2830

HIGH · 10.0 CVSS v2.0 Published 2015-03-31
Fix available
A fix is available. Upgrade to after 6.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Stack-based buffer overflow in cifskey.c or cifscreds.c in cifs-utils before 6.4, as used in pam_cifscreds, allows remote attackers to have unspecified impact via unknown 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 confidence

Stack-based buffer overflow vulnerability in cifskey.c or cifscreds.c in cifs-utils before version 6.4, affecting the pam_cifscreds PAM module used for CIFS/SMB credential management. The buffer overflow occurs on the stack, potentially allowing attackers to overwrite return addresses and execute arbitrary code with the privileges of the PAM module.

MitigationUpgrade cifs-utils to version 6.4 or later. If immediate upgrading is not feasible, restrict access to pam_cifscreds functionality and CIFS mount points, and audit systems for indicators of compromise.

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
Cifs UtilsApplication
Affected:<= 6.3

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

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

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. Verify cifs-utils package installation
    Run 'rpm -q cifs-utils' (RHEL/CentOS) or 'dpkg -l cifs-utils' (Debian/Ubuntu) to check if the package is installed
    Affected if Package is not installed means not affected; if installed, proceed to version check
  2. Check cifs-utils version
    Run 'rpm -qi cifs-utils' (RHEL/CentOS) or 'dpkg -s cifs-utils' (Debian/Ubuntu) to retrieve the installed version number
    Affected if Version is 6.3 or lower, or the package has no version info but predates the 6.4 release
  3. Locate pam_cifscreds module
    Run 'find /lib*/security/ -name pam_cifscreds*' or 'ls -la /lib*/security/pam_cifscreds*' to find the PAM module binary
    Affected if The pam_cifscreds binary exists in the PAM modules directory
  4. Check if pam_cifscreds is configured in PAM
    Search PAM configuration files: 'grep -r pam_cifscreds /etc/pam.d/' or 'grep pam_cifscreds /etc/pam.conf' to see if the module is referenced
    Affected if The module is referenced in any PAM configuration file, indicating it is actively used

User is affected if cifs-utils version is 6.3 or lower AND pam_cifscreds module is installed and configured in the PAM stack.

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 a release after 6.3
Interim mitigation

Upgrade cifs-utils to version 6.4 or later. If immediate upgrading is not feasible, restrict access to pam_cifscreds functionality and CIFS mount points, and audit systems for indicators of compromise.

Recommended fix High confidence

cifs-utils 6.4 or later

  1. 1. Identify the current version of cifs-utils installed on the system using your package manager (e.g., 'rpm -q cifs-utils', 'dpkg -l cifs-utils', or 'yum list cifs-utils')
  2. 2. Upgrade cifs-utils to version 6.4 or later using your distribution's package manager (e.g., 'yum update cifs-utils', 'apt-get install cifs-utils', or 'dnf update cifs-utils')
  3. 3. If pam_cifscreds is used, ensure the updated package is properly installed and restart any services that may cache the old library
  4. 4. Verify the new version is installed: 'rpm -q cifs-utils' or equivalent command for your package manager

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

Fix this in Cifs Utils Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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