CVE-2010-0791 json
The (1) ncpmount, (2) ncpumount, and (3) ncplogin programs in ncpfs 2.2.6 do not properly create lock files, which allows local users to ca…
published 2010-03-09 16 y ago modified 2026-06-16 4 mo ago also EUVD-2010-0817
- cvss
- 2.1
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 29%
- public exploits
- 0
- none known
Summary
The (1) ncpmount, (2) ncpumount, and (3) ncplogin programs in ncpfs 2.2.6 do not properly create lock files, which allows local users to cause a denial of service (application failure) via unspecified vectors that trigger the creation of a /etc/mtab~ file that persists after the program exits.
Patch / fix
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-2010-0791 updated cvss 3.3
ncpfs: Information disclosure and denial of service
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
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
0.36% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
References
-
seclists.org
/fulldisclosure/2010/Mar/122
mailing-list, patch
-
lists.opensuse.org
/opensuse-security-announce/2010-06/msg00001.html
vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2010-05/msg00002.html
vendor-advisory
-
securityfocus.com
/archive/1/509893/100/0/threaded
mailing-list
-
securityfocus.com
/bid/38563
vdb-entry
-
securityfocus.com
/archive/1/509894/100/0/threaded
mailing-list
Sources
- CVE List CVE-2010-0791
- NVD CVE-2010-0791
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.