CVE-2014-2830 json
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…
published 2015-03-31 11 y ago modified 2026-06-17 4 mo ago also EUVD-2014-2855
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.6%
- EPSS 5.6% chance of exploitation in 30 days, percentile 92%
- public exploits
- 0
- none known
Summary
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.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2014-2830 updated cvss 5.2
cifs-utils: stack-based buffer overflow flaw in pam_cifscreds
-
Red Hat Enterprise Linux 5 samba, samba3x Red Hat Enterprise Linux 6 cifs-utils Red Hat Enterprise Linux 7 cifs-utilsaffected: no fix planned “Will not fix”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
5.61% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
mandriva.com
/security/advisories?name=MDVSA-2015:114
vendor-advisory
-
security.gentoo.org
/glsa/201612-08
vendor-advisory
-
lists.samba.org
/archive/samba-technical/2014-July/101132.html
mailing-list
- bugs.mageia.org /show_bug.cgi?id=13386
- bugzilla.redhat.com /show_bug.cgi?id=1086224
- bugzilla.novell.com /show_bug.cgi?id=870168
- advisories.mageia.org /MGASA-2014-0242.html
-
seclists.org
/oss-sec/2014/q2/96
mailing-list
Sources
- CVE List CVE-2014-2830
- NVD CVE-2014-2830
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.