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
Unspecified vulnerability in Microsoft Word 2000, 2002, and Word Viewer 2003 allows user-assisted remote attackers to execute arbitrary code via a crafted DOC file that triggers memory corruption, as demonstrated via the 12122006-djtest.doc file, a different issue than CVE-2006-5994 and CVE-2006-6456.
CVE Informations
Related Weaknesses
CWE-ID
Weakness Name
Source
CWE Other
No informations.
Metrics
Metrics
Score
Severity
CVSS Vector
Source
V2
9.3
AV:N/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
–
–
46.72%
–
–
2022-12-18
–
–
46.72%
–
–
2023-03-12
–
–
–
96.61%
–
2023-07-02
–
–
–
96.69%
–
2023-09-10
–
–
–
96.65%
–
2023-10-01
–
–
–
96.65%
–
2023-10-22
–
–
–
96.75%
–
2024-02-11
–
–
–
96.28%
–
2024-03-31
–
–
–
96.28%
–
2024-06-02
–
–
–
96.28%
–
2024-06-02
–
–
–
96.28%
–
2024-11-03
–
–
–
95.89%
–
2024-12-22
–
–
–
95.09%
–
2024-12-29
–
–
–
95.09%
–
2025-01-05
–
–
–
95.09%
–
2025-01-26
–
–
–
95.09%
–
2025-01-19
–
–
–
95.09%
–
2025-01-25
–
–
–
95.09%
–
2025-03-18
–
–
–
–
75.7%
2025-03-30
–
–
–
–
74.41%
2025-04-22
–
–
–
–
76.28%
2025-04-22
–
–
–
–
76.28,%
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.
=====
The file I have attached is a very basic two stage bug. stage 1 (the
first mod) forces the code down a wrong path. the second mod by
itsself is harmless, however when used with the first it will be the
first and part of the second overwrite.
I have use 41414141 as a marker to make it easier for you to see.
I have made it crash the wordviewer again to make it more obvious
Weight,
location: 00000274
value : 00000022 - just so it crashes, values 00000001 -> 00000006
are probably the most useful for trying to overwrite a pointer. notice
that neighbouring areas can be weighted the same.
marker,
location: 000027e4
value : 41414141
the weight destination address == ((weight * 4[this is EDI]) + 4 [ECX*4]) + source memory offest[ESI].
[also the meta data is microsofts, not mine]
======
bug hugs,
disco.
poc: https://gitlab.com/exploit-database/exploitdb-bin-sploits/-/raw/main/bin-sploits/2922.doc (12122006-djtest.doc)
# milw0rm.com [2006-12-12]