View: Deprecated Entries

Draft
Type: Implicit
Objective

CWE nodes in this view (slice) have been deprecated. There should be a reference pointing to the replacement in each deprecated weakness.

Membership
IDNameDescription
CWE-1187DEPRECATED: Use of Uninitialized ResourceThis entry has been consolidated into CWE-908: Use of Uninitialized Resource. All relevant information has been migrated to that primary weakness entry.
CWE-132DEPRECATED: Miscalculated Null TerminationThis entry has been deprecated and merged into CWE-170 (Improper Null Termination). It was originally created as a duplicate, and all relevant information has been consolidated under CWE-170 for clearer vulnerability tracking.
CWE-1324DEPRECATED: Sensitive Information Accessible by Physical Probing of JTAG InterfaceThis entry has been deprecated. The issue of accessing sensitive data through physical probing of a device's JTAG debugging interface is now comprehensively covered under CWE-319: Cleartext Transmission of Sensitive Information.
CWE-216DEPRECATED: Containment Errors (Container Errors)This entry has been retired because it functioned more as a broad category than a specific, actionable vulnerability. The term 'container' also caused confusion, as developers interpret it differently than originally intended, making the entry unclear for practical use.
CWE-217DEPRECATED: Failure to Protect Stored Data from ModificationThis entry has been deprecated. The security issues it described—specifically around failing to protect stored data from unauthorized changes—are now more precisely covered by CWE-766 (Critical Data Element Declared Public) and CWE-767 (Access to Critical Private Field via Unsafe Reflection).
CWE-218DEPRECATED: Failure to provide confidentiality for stored dataThis entry has been consolidated into CWE-493: Critical Public Variable Without Final Modifier. The original content describing failure to protect stored data confidentiality has been moved to that entry.
CWE-225DEPRECATED: General Information Management ProblemsThis entry has been deprecated and consolidated into CWE-199: Information Management Errors. Please refer to that entry for current information.
CWE-247DEPRECATED: Reliance on DNS Lookups in a Security DecisionThis deprecated entry has been merged into CWE-350: Reliance on Reverse DNS Resolution for a Security-Critical Action. All related content has been moved to that primary weakness entry.
CWE-249DEPRECATED: Often Misused: Path ManipulationThis entry has been deprecated. Its content was unclear and combined multiple security issues. Most relevant information has been moved to CWE-785.
CWE-292DEPRECATED: Trusting Self-reported DNS NameThis entry is a duplicate and has been consolidated into CWE-350: Reliance on Reverse DNS Resolution for a Security-Critical Action. The content from this deprecated entry has been fully migrated to CWE-350.
CWE-365DEPRECATED: Race Condition in SwitchThis deprecated entry originally suggested a race condition could occur if a switch statement's controlling expression was evaluated multiple times. In practice, this doesn't happen—the expression is evaluated just once, making this specific scenario not a valid software weakness.
CWE-373DEPRECATED: State Synchronization ErrorThis entry has been retired because its core concept—errors that occur when different parts of a system fail to coordinate their shared state correctly—is fully covered by two more precise and actively maintained categories: Race Conditions (CWE-362) and Improper Synchronization (CWE-662).
CWE-423DEPRECATED: Proxied Trusted ChannelThis entry is no longer active. It was merged into CWE-441 (The 'Proxied Trusted Channel' weakness) to eliminate duplication. Please refer to CWE-441 for all related information.
CWE-443DEPRECATED: HTTP response splittingThis entry has been deprecated and consolidated into CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting').
CWE-458DEPRECATED: Incorrect InitializationThis CWE entry has been retired. Its original description overlapped with another vulnerability (CWE-454), while its name pointed to a broader category of initialization issues. For guidance on improper initialization problems, please see CWE-665.
CWE-516DEPRECATED: Covert Timing ChannelThis entry has been deprecated and its content has been moved. Please refer to CWE-385: Covert Timing Channel for the current information.
CWE-533DEPRECATED: Information Exposure Through Server Log FilesThis entry has been deprecated. Its scope was too narrow, focusing on a specific symptom rather than the root cause. Please refer to CWE-532: Insertion of Sensitive Information into Log File for the current, more comprehensive guidance.
CWE-534DEPRECATED: Information Exposure Through Debug Log FilesThis deprecated entry describes a vulnerability where sensitive application data is unintentionally written to debug log files, potentially exposing it to unauthorized users. It has been consolidated into the broader CWE-532: Information Exposure Through Log Files.
CWE-542DEPRECATED: Information Exposure Through Cleanup Log FilesThis entry has been deprecated because it was too specific. Please refer to the broader and more comprehensive CWE-532: Information Exposure Through Log Files for current guidance.
CWE-545DEPRECATED: Use of Dynamic Class LoadingThis entry has been retired. Its content is now covered elsewhere, primarily because it described a standard programming technique rather than a specific vulnerability and overlapped with other existing weakness entries.
CWE-592DEPRECATED: Authentication Bypass IssuesThis entry has been retired because its core concept—authentication bypass vulnerabilities—is fully covered by CWE-287: Improper Authentication. It was removed to eliminate redundancy and streamline the CWE list.
CWE-596DEPRECATED: Incorrect Semantic Object ComparisonThis CWE entry has been retired. It was originally created to describe a specific type of bug where code incorrectly compares two objects that should be considered the same, but the description was too vague and overlapped with other weaknesses. It has been consolidated into CWE-1023.
CWE-71DEPRECATED: Apple '.DS_Store'This entry has been deprecated because it describes a specific real-world example of a UNIX hard link vulnerability, not a distinct weakness category. For the core issue, please refer to CWE-62: UNIX Hard Link.
CWE-769DEPRECATED: Uncontrolled File Descriptor ConsumptionThis entry has been deprecated and merged into CWE-774 (Allocation of Resources Without Limits or Throttling). The content describing uncontrolled file descriptor consumption is now fully covered under that more comprehensive weakness.
CWE-92DEPRECATED: Improper Sanitization of Custom Special CharactersThis deprecated entry originally flagged issues where custom or non-standard special characters weren't properly sanitized. It has been consolidated into the more comprehensive CWE-75: Failure to Sanitize Special Elements.
CWE-1DEPRECATED: LocationThis category has been deprecated. It was originally used for organizing the Development View (CWE-699), but it introduced unnecessary complexity and depth to the resulting tree.
CWE-10DEPRECATED: ASP.NET Environment IssuesThis category has been deprecated. It added unnecessary depth and complexity to its associated views.
CWE-100DEPRECATED: Technology-Specific Input Validation ProblemsThis category has been deprecated. It was originally intended as a "catch-all" for input validation problems in technologies that did not have their own CWE, but introduces unnecessary depth to the hierarchy.
CWE-101DEPRECATED: Struts Validation ProblemsThis category has been deprecated. It was originally used for organizing the Development View (CWE-699), but it introduced unnecessary complexity and depth to the resulting tree.
CWE-139DEPRECATED: General Special Element ProblemsThis entry has been deprecated. It is a leftover from PLOVER, but CWE-138 is a more appropriate mapping.
CWE-169DEPRECATED: Technology-Specific Special ElementsThis category has been deprecated. It was originally intended as a "catch-all" for input validation problems in technologies that did not have their own CWE, but introduces unnecessary depth to the hierarchy.
CWE-17DEPRECATED: CodeThis entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.
CWE-171DEPRECATED: Cleansing, Canonicalization, and Comparison ErrorsThis entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree. Weaknesses in this category were related to improper handling of data within protection mechanisms that attempt to perform neutralization for untrusted data. These weaknesses can be found in other similar categories.
CWE-18DEPRECATED: Source CodeThis entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.
CWE-21DEPRECATED: Pathname Traversal and Equivalence ErrorsThis category has been deprecated. It was originally used for organizing weaknesses involving file names, which enabled access to files outside of a restricted directory (path traversal) or to perform operations on files that would otherwise be restricted (path equivalence). Consider using either the File Handling Issues category (CWE-1219) or the class Use of Incorrectly-Resolved Name or Reference (CWE-706).
CWE-3DEPRECATED: Technology-specific Environment IssuesThis category has been deprecated. It was originally intended as a "catch-all" for environment issues for technologies that did not have their own CWE, but it introduced unnecessary depth and complexity to the Development View (CWE-699).
CWE-376DEPRECATED: Temporary File IssuesThis category has been deprecated. It was originally used for organizing the Development View (CWE-699), but it introduced unnecessary complexity and depth to the resulting tree. Consider using the File Handling Issues category (CWE-1219).
CWE-380DEPRECATED: Technology-Specific Time and State IssuesThis entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.
CWE-381DEPRECATED: J2EE Time and State IssuesThis entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.
CWE-4DEPRECATED: J2EE Environment IssuesThis entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.
CWE-418DEPRECATED: Channel ErrorsThis category has been deprecated because it redundant with the grouping provided by CWE-417.
CWE-442DEPRECATED: Web ProblemsThis entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.
CWE-445DEPRECATED: User Interface ErrorsThis weakness has been deprecated because it was a duplicate of CWE-355. All content has been transferred to CWE-355.
CWE-461DEPRECATED: Data Structure IssuesThis entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.
CWE-490DEPRECATED: Mobile Code IssuesThis entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.
CWE-503DEPRECATED: Byte/Object CodeThis category has been deprecated. It was originally used for organizing the Development View (CWE-699), but it introduced unnecessary complexity and depth to the resulting tree.
CWE-504DEPRECATED: Motivation/IntentThis category has been deprecated. It was originally used for organizing the Development View (CWE-699), but it introduced unnecessary complexity and depth to the resulting tree.
CWE-505DEPRECATED: Intentionally Introduced WeaknessThis category has been deprecated as it was originally used for organizing the Development View (CWE-699), but it introduced unnecessary complexity and depth to the resulting tree.
CWE-513DEPRECATED: Intentionally Introduced Nonmalicious WeaknessThis category has been deprecated as it was originally used for organizing the Development View (CWE-699), but it introduced unnecessary complexity and depth to the resulting tree.
CWE-517DEPRECATED: Other Intentional, Nonmalicious WeaknessThis category has been deprecated as it was originally used for organizing the Development View (CWE-699), but it introduced unnecessary complexity and depth to the resulting tree.
CWE-518DEPRECATED: Inadvertently Introduced WeaknessThis category has been deprecated as it was originally used for organizing the Development View (CWE-699), but it introduced unnecessary complexity and depth to the resulting tree.
CWE-519DEPRECATED: .NET Environment IssuesThis entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.
CWE-559DEPRECATED: Often Misused: Arguments and ParametersThis entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.
CWE-60DEPRECATED: UNIX Path Link ProblemsThis category has been deprecated. It covered a very low level of abstraction based on operating system, which was not useful for any existing view.
CWE-63DEPRECATED: Windows Path Link ProblemsThis category has been deprecated. It covered a very low level of abstraction based on operating system, which was not useful for any existing view.
CWE-632DEPRECATED: Weaknesses that Affect Files or DirectoriesThis category has been deprecated. It was not actively maintained, and it was not useful to stakeholders. It was originally created before CWE 1.0 as part of view CWE-631, which was a simple example of how views could be structured within CWE.
CWE-633DEPRECATED: Weaknesses that Affect MemoryThis category has been deprecated. It was not actively maintained, and it was not useful to stakeholders. It was originally created before CWE 1.0 as part of view CWE-631, which was a simple example of how views could be structured within CWE.
CWE-634DEPRECATED: Weaknesses that Affect System ProcessesThis category has been deprecated. It was not actively maintained, and it was not useful to stakeholders. It was originally created before CWE 1.0 as part of view CWE-631, which was a simple example of how views could be structured within CWE.
CWE-68DEPRECATED: Windows Virtual File ProblemsThis category has been deprecated as it was found to be an unnecessary abstraction of platform specific details. Please refer to the category CWE-632 and weakness CWE-66 for relevant relationships.
CWE-70DEPRECATED: Mac Virtual File ProblemsThis category has been deprecated as it was found to be an unnecessary abstraction of platform specific details. Please refer to the category CWE-632 and weakness CWE-66 for relevant relationships.
CWE-630DEPRECATED: Weaknesses Examined by SAMATEThis view has been deprecated. It was only used for an early year of the NIST SAMATE project, and it did not represent any official or commonly-utilized list.
CWE-631DEPRECATED: Resource-specific WeaknessesThis view has been deprecated because it is not actively maintained and does not provide utility to stakeholders. It was originally created before CWE 1.0 as a simple example of how views could be structured within CWE.
CWE-679DEPRECATED: Chain ElementsThis view has been deprecated. It has limited utility for stakeholders, since all weaknesses can be links in a chain.
CWE-999DEPRECATED: Weaknesses without Software Fault PatternsThis view has been deprecated. It was based on gaps in another view (CWE-888) related to research that is no longer updated, but was complete with respect to CWE at the time it was conducted.
Mapping Notes
Usage: Prohibited
Reasons: View
Rationale:
This entry is a View. Views are not weaknesses and therefore inappropriate to describe the root causes of vulnerabilities.
Comment:
Use this View or other Views to search and navigate for the appropriate weakness.