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
Interpretation conflict in ASP.NET in Microsoft .NET Framework 1.0, 1.1, and 2.0 for Windows 2000, XP, Server 2003, and Vista allows remote attackers to access configuration files and obtain sensitive information, and possibly bypass security mechanisms that try to constrain the final substring of a string, via %00 characters, related to use of %00 as a string terminator within POSIX functions but a data character within .NET strings, aka "Null Byte Termination Vulnerability."
Exposure of Sensitive Information to an Unauthorized Actor The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
Metrics
Metrics
Score
Severity
CVSS Vector
Source
V2
7.8
AV:N/AC:L/Au:N/C:C/I:N/A:N
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
–
–
51.09%
–
–
2022-04-03
–
–
51.09%
–
–
2023-03-12
–
–
–
97.05%
–
2023-04-02
–
–
–
96.7%
–
2023-05-07
–
–
–
96.66%
–
2023-06-11
–
–
–
96.37%
–
2023-07-16
–
–
–
96.07%
–
2023-08-27
–
–
–
95.75%
–
2023-10-01
–
–
–
95.9%
–
2023-11-05
–
–
–
96.11%
–
2023-12-17
–
–
–
96.12%
–
2024-01-21
–
–
–
95.82%
–
2024-03-03
–
–
–
95.61%
–
2024-04-07
–
–
–
94.07%
–
2024-06-02
–
–
–
91.97%
–
2024-06-23
–
–
–
90.53%
–
2024-07-28
–
–
–
92.82%
–
2024-09-08
–
–
–
92%
–
2024-10-13
–
–
–
92.09%
–
2024-12-08
–
–
–
91.49%
–
2024-12-22
–
–
–
65.96%
–
2025-01-19
–
–
–
54.84%
–
2025-03-16
–
–
–
35.96%
–
2025-01-19
–
–
–
54.84%
–
2025-03-18
–
–
–
–
80.63%
2025-03-18
–
–
–
–
80.63,%
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.
Publication date : 2007-07-05 22h00 +00:00 Author : Paul Craig EDB Verified : Yes
source: https://www.securityfocus.com/bid/24791/info
Microsoft .NET Framework is prone to multiple NULL-byte injection vulnerabilities because it fails to adequately sanitize user-supplied data.
An attacker can exploit these issues to access sensitive information that may aid in further attacks; other attacks are also possible.
http://www.example.com/[path]/somescript.asp%00