Vulnerability Database
Every documented weakness class (CWE), sorted by CWE number.
- CWE-296: Improper Following of a Certificate's Chain of TrustImproper Following of a Certificate's Chain of Trust is a vulnerability that occurs when a product does not follow, or incorrectly follows, the chain
- CWE-297: Improper Validation of Certificate with Host MismatchImproper Validation of Certificate with Host Mismatch is a vulnerability that occurs when a product accepts certificates without verifying they
- CWE-298: Improper Validation of Certificate ExpirationImproper Validation of Certificate Expiration is a vulnerability that occurs when certificate expiration dates are not validated or are incorrectly
- CWE-299: Improper Check for Certificate RevocationImproper Check for Certificate Revocation is a vulnerability that occurs when a product does not check or incorrectly checks the revocation status of
- CWE-300: Channel Accessible by Non-EndpointChannel Accessible by Non-Endpoint is a vulnerability that occurs when a product does not adequately verify the identities of the entities at both
- CWE-301: Reflection Attack in an Authentication ProtocolReflection Attack in an Authentication Protocol is a vulnerability that occurs when simple authentication protocols using shared secret keys are
- CWE-302: Authentication Bypass by Assumed-Immutable DataAuthentication Bypass by Assumed-Immutable Data is a vulnerability that occurs when an authentication scheme uses key data elements that developers
- CWE-303: Incorrect Implementation of Authentication AlgorithmIncorrect Implementation of Authentication Algorithm is a vulnerability that occurs when a product's requirements dictate the use of an established
- CWE-304: Missing Critical Step in AuthenticationMissing Critical Step in Authentication is a vulnerability that occurs when a product implements an authentication technique but omits a critical
- CWE-305: Authentication Bypass by Primary WeaknessAuthentication Bypass by Primary Weakness is a vulnerability that occurs when the authentication algorithm itself is sound, but an underlying
- CWE-306: Missing Authentication for Critical FunctionMissing Authentication for Critical Function occurs when software does not perform any authentication for functionality that requires a provable user
- CWE-307: Improper Restriction of Excessive Authentication AttemptsImproper Restriction of Excessive Authentication Attempts occurs when a web application does not limit or improperly limits the number of failed
- CWE-308: Use of Single-factor AuthenticationUse of Single-factor Authentication is a vulnerability that occurs when a product relies on only one authentication factor (typically a password) in
- CWE-309: Use of Password System for Primary AuthenticationUse of Password System for Primary Authentication is a vulnerability that occurs when password-based authentication serves as the sole or primary
- CWE-311: Missing Encryption of Sensitive DataMissing Encryption of Sensitive Data occurs when software does not encrypt sensitive or critical information before storage or transmission.
- CWE-312: Cleartext Storage of Sensitive InformationCleartext Storage of Sensitive Information occurs when a product stores sensitive information in cleartext within a resource that might be accessible
- CWE-313: Cleartext Storage in a File or on DiskCleartext Storage in a File or on Disk is a vulnerability that occurs when a product stores sensitive information in cleartext in files or directly
- CWE-314: Cleartext Storage in the RegistryCleartext Storage in the Registry is a vulnerability specific to Windows systems where a product stores sensitive information in cleartext in the
- CWE-315: Cleartext Storage of Sensitive Information in a CookieCleartext Storage of Sensitive Information in a Cookie is a vulnerability that occurs when a product stores sensitive information in cleartext within
- CWE-316: Cleartext Storage of Sensitive Information in MemoryCleartext Storage of Sensitive Information in Memory is a vulnerability that occurs when a product stores sensitive information in cleartext in memory.
- CWE-317: Cleartext Storage of Sensitive Information in GUICleartext Storage of Sensitive Information in GUI is a vulnerability that occurs when a product stores sensitive information in cleartext within
- CWE-318: Cleartext Storage of Sensitive Information in ExecutableCleartext Storage of Sensitive Information in Executable is a vulnerability that occurs when a product stores sensitive information in cleartext
- CWE-319: Cleartext Transmission of Sensitive InformationCleartext Transmission of Sensitive Information occurs when software transmits sensitive or security-critical data in cleartext over a communication
- CWE-321: Use of Hard-coded Cryptographic KeyUse of Hard-coded Cryptographic Key occurs when software contains a fixed cryptographic key embedded in source code, configuration, or firmware.
- CWE-322: Key Exchange without Entity AuthenticationKey Exchange without Entity Authentication is a vulnerability that occurs when a system performs a cryptographic key exchange with an actor without
- CWE-323: Reusing a Nonce, Key Pair in EncryptionReusing a Nonce, Key Pair in Encryption is a vulnerability that occurs when the same nonce (number used once) is used with the same key for multiple
- CWE-324: Use of a Key Past its Expiration DateUse of a Key Past its Expiration Date is a vulnerability that occurs when a product uses cryptographic keys or passwords beyond their intended
- CWE-325: Missing Cryptographic StepMissing Cryptographic Step is a vulnerability that occurs when a product does not implement a required step in a cryptographic algorithm, resulting
- CWE-326: Inadequate Encryption StrengthInadequate Encryption Strength occurs when software uses a cryptographic algorithm or key length that is insufficient to protect data according to
- CWE-327: Use of a Broken or Risky Cryptographic AlgorithmUse of a Broken or Risky Cryptographic Algorithm occurs when software uses cryptographic algorithms or protocols that have known weaknesses, are
- CWE-328: Use of Weak HashUse of Weak Hash is a vulnerability that occurs when a product uses a hashing algorithm that does not meet security requirements, allowing attackers
- CWE-329: Not Using an Unpredictable IV with CBC ModeNot Using an Unpredictable IV with CBC Mode occurs when software uses Cipher Block Chaining (CBC) mode encryption but fails to use a random,
- CWE-330: Use of Insufficiently Random ValuesUse of Insufficiently Random Values occurs when a product uses insufficiently random numbers or values in a security context that depends on
- CWE-331: Insufficient EntropyInsufficient Entropy is a vulnerability that occurs when a product uses an algorithm or scheme that produces values with insufficient randomness,
- CWE-332: Insufficient Entropy in PRNGInsufficient Entropy in PRNG is a vulnerability that occurs when a Pseudo-Random Number Generator (PRNG) lacks sufficient entropy in its seeding or
- CWE-333: Improper Handling of Insufficient Entropy in TRNGImproper Handling of Insufficient Entropy in TRNG is a vulnerability that occurs when a system using a True Random Number Generator (TRNG) fails to
- CWE-334: Small Space of Random ValuesSmall Space of Random Values is a vulnerability that occurs when the number of possible random values that a product can generate is smaller than
- CWE-335: Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG)Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG) is a vulnerability that occurs when a product uses a PRNG but fails to properly
- CWE-336: Same Seed in Pseudo-Random Number Generator (PRNG)Same Seed in Pseudo-Random Number Generator (PRNG) is a vulnerability that occurs when a PRNG is initialized with the same seed value across multiple
- CWE-337: Predictable Seed in Pseudo-Random Number Generator (PRNG)Predictable Seed in Pseudo-Random Number Generator (PRNG) is a vulnerability that occurs when a PRNG is initialized with a seed value that an
- CWE-338: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)Use of Cryptographically Weak PRNG occurs when software uses a pseudo-random number generator (PRNG) that is not suitable for security-sensitive
- CWE-339: Small Seed Space in PRNGSmall Seed Space in PRNG is a vulnerability that occurs when a Pseudo-Random Number Generator (PRNG) is seeded with a value from a space that is too
- CWE-340: Generation of Predictable Numbers or IdentifiersGeneration of Predictable Numbers or Identifiers occurs when software generates identifiers, sequence numbers, or other values that should be
- CWE-341: Predictable from Observable StatePredictable from Observable State is a vulnerability that occurs when numbers or identifiers can be predicted by an attacker who observes system or
- CWE-342: Predictable Exact Value from Previous ValuesPredictable Exact Value from Previous Values is a vulnerability that occurs when an exact value or random number can be precisely predicted by
- CWE-343: Predictable Value Range from Previous ValuesPredictable Value Range from Previous Values is a vulnerability that occurs when a random number generator produces sequences that allow attackers to
- CWE-344: Use of Invariant Value in Dynamically Changing ContextUse of Invariant Value in Dynamically Changing Context is a vulnerability that occurs when a product uses a constant value, name, or reference in
- CWE-345: Insufficient Verification of Data AuthenticityInsufficient Verification of Data Authenticity occurs when software does not sufficiently verify the origin or authenticity of data before using it
- CWE-346: Origin Validation ErrorOrigin Validation Error occurs when software does not properly verify the origin of a request, message, or data.
- CWE-347: Improper Verification of Cryptographic SignatureImproper Verification of Cryptographic Signature occurs when software does not verify, or incorrectly verifies, the cryptographic signature for data.
- CWE-348: Use of Less Trusted SourceUse of Less Trusted Source is a vulnerability that occurs when a product selects between multiple data sources but chooses the one that offers
- CWE-349: Acceptance of Extraneous Untrusted Data With Trusted DataAcceptance of Extraneous Untrusted Data With Trusted Data is a vulnerability that occurs when a product, while processing trusted data, accepts any
- CWE-350: Reliance on Reverse DNS Resolution for a Security-Critical ActionReliance on Reverse DNS Resolution for a Security-Critical Action occurs when software performs a security decision based on the result of a reverse
- CWE-351: Insufficient Type DistinctionInsufficient Type Distinction is a vulnerability that occurs when a product does not properly distinguish between different types of elements in a
- CWE-352: Cross-Site Request Forgery (CSRF)Cross-Site Request Forgery (CSRF) is a vulnerability that occurs when a web application does not sufficiently verify whether a request came from an
- CWE-353: Missing Support for Integrity CheckMissing Support for Integrity Check is a vulnerability that occurs when a product employs a transmission protocol or data storage mechanism that
- CWE-354: Improper Validation of Integrity Check ValueImproper Validation of Integrity Check Value is a vulnerability that occurs when a product fails to validate or incorrectly validates integrity check
- CWE-356: Product UI does not Warn User of Unsafe ActionsProduct UI does not Warn User of Unsafe Actions is a vulnerability that occurs when a software application's user interface fails to alert users
- CWE-357: Insufficient UI Warning of Dangerous OperationsInsufficient UI Warning of Dangerous Operations is a vulnerability that occurs when an application's user interface provides a warning about
- CWE-358: Improperly Implemented Security Check for StandardImproperly Implemented Security Check for Standard is a vulnerability that occurs when a product fails to properly implement or entirely omits one or
- CWE-359: Exposure of Private Personal Information to an Unauthorized ActorExposure of Private Personal Information to an Unauthorized Actor occurs when a product does not properly prevent a person's private, personal
- CWE-360: Trust of System Event DataTrust of System Event Data is a vulnerability that occurs when software relies on system event information—such as window messages, keyboard/mouse
- CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')Race Condition vulnerabilities occur when multiple threads, processes, or systems access and modify shared resources concurrently without proper
- CWE-363: Race Condition Enabling Link FollowingRace Condition Enabling Link Following is a Time-of-Check Time-of-Use (TOCTOU) vulnerability that occurs when a program checks a file's properties
- CWE-364: Signal Handler Race ConditionSignal Handler Race Condition is a vulnerability that occurs when signal handlers introduce race conditions through asynchronous actions.
- CWE-366: Race Condition within a ThreadRace Condition within a Thread is a vulnerability that occurs when two or more threads of execution use a resource simultaneously without proper
- CWE-367: Time-of-check Time-of-use (TOCTOU) Race ConditionTime-of-check Time-of-use (TOCTOU) Race Condition occurs when a program checks the state of a resource and then uses that resource based on the
- CWE-368: Context Switching Race ConditionContext Switching Race Condition is a vulnerability that occurs when a product performs non-atomic actions while switching between security contexts,
- CWE-369: Divide By ZeroDivide By Zero is a vulnerability that occurs when a product divides a value by zero, causing undefined behavior, crashes, or exceptions.
- CWE-370: Missing Check for Certificate Revocation after Initial CheckMissing Check for Certificate Revocation after Initial Check is a vulnerability that occurs when a product fails to verify certificate revocation
- CWE-372: Incomplete Internal State DistinctionIncomplete Internal State Distinction is a vulnerability that occurs when a product fails to accurately determine its current operational state,
- CWE-374: Passing Mutable Objects to an Untrusted MethodPassing Mutable Objects to an Untrusted Method is a vulnerability that occurs when a program transmits non-cloned mutable data as an argument to a
- CWE-375: Returning a Mutable Object to an Untrusted CallerReturning a Mutable Object to an Untrusted Caller is a vulnerability that occurs when functions return references to mutable internal data without
- CWE-377: Insecure Temporary FileInsecure Temporary File vulnerability occurs when software creates temporary files in an insecure manner.
- CWE-378: Creation of Temporary File With Insecure PermissionsCreation of Temporary File With Insecure Permissions is a vulnerability that occurs when an application creates temporary files with permissions that
- CWE-379: Creation of Temporary File in Directory with Insecure PermissionsCreation of Temporary File in Directory with Insecure Permissions is a vulnerability that occurs when an application creates temporary files in a
- CWE-382: J2EE Bad Practices: Use of System.exit()J2EE Bad Practices: Use of System.exit() is a vulnerability that occurs when a J2EE or web application calls System.exit() or similar VM termination
- CWE-383: J2EE Bad Practices: Direct Use of ThreadsJ2EE Bad Practices: Direct Use of Threads is a vulnerability that occurs when a web application directly creates and manages threads instead of using
- CWE-384: Session FixationSession Fixation occurs when authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier.
- CWE-385: Covert Timing ChannelCovert Timing Channel is a vulnerability that occurs when sensitive information can be inferred by observing the timing of system operations.
- CWE-386: Symbolic Name not Mapping to Correct ObjectSymbolic Name not Mapping to Correct Object is a vulnerability that occurs when a constant symbolic reference to an object is used, even though the
- CWE-390: Detection of Error Condition Without ActionDetection of Error Condition Without Action is a vulnerability that occurs when software detects a specific error but takes no actions to handle it.
- CWE-391: Unchecked Error ConditionUnchecked Error Condition is a vulnerability that occurs when programmers fail to properly check or handle exceptions and error conditions.
- CWE-392: Missing Report of Error ConditionMissing Report of Error Condition is a vulnerability that occurs when software encounters an error but does not provide a status code or return value
- CWE-393: Return of Wrong Status CodeReturn of Wrong Status Code is a vulnerability that occurs when a function or operation returns an incorrect return value or status code that does
- CWE-394: Unexpected Status Code or Return ValueUnexpected Status Code or Return Value is a vulnerability that occurs when software fails to adequately verify when a function or operation returns a
- CWE-395: Use of NullPointerException Catch to Detect NULL Pointer DereferenceUse of NullPointerException Catch to Detect NULL Pointer Dereference is a vulnerability that occurs when code uses exception handling to detect null
- CWE-396: Declaration of Catch for Generic ExceptionDeclaration of Catch for Generic Exception occurs when software uses a catch block that handles all exceptions (like catching Exception or
- CWE-397: Declaration of Throws for Generic ExceptionDeclaration of Throws for Generic Exception is a vulnerability that occurs when methods declare they throw overly broad exceptions like Exception or
- CWE-400: Uncontrolled Resource ConsumptionUncontrolled Resource Consumption occurs when a product does not properly control the allocation and maintenance of limited resources, allowing an
- CWE-401: Missing Release of Memory after Effective Lifetime (Memory Leak)Missing Release of Memory after Effective Lifetime occurs when a program allocates memory but fails to release it after it is no longer needed.
- CWE-402: Transmission of Private Resources into a New Sphere ('Resource Leak')Transmission of Private Resources into a New Sphere occurs when a product makes resources available to untrusted parties when those resources are
- CWE-403: Exposure of File Descriptor to Unintended Control Sphere ('File Descriptor Leak')Exposure of File Descriptor to Unintended Control Sphere occurs when a process fails to close sensitive file descriptors before spawning a child
- CWE-404: Improper Resource Shutdown or ReleaseImproper Resource Shutdown or Release occurs when software fails to properly close, release, or cleanup resources after they are no longer needed.
- CWE-405: Asymmetric Resource Consumption (Amplification)Asymmetric Resource Consumption (Amplification) is a vulnerability that occurs when a product does not properly control situations in which an
- CWE-406: Insufficient Control of Network Message Volume (Network Amplification)Insufficient Control of Network Message Volume is a vulnerability where a product does not sufficiently monitor or control transmitted network
- CWE-407: Inefficient Algorithmic ComplexityInefficient Algorithmic Complexity is a vulnerability that occurs when an algorithm in a product has an inefficient worst-case computational
- CWE-408: Incorrect Behavior Order: Early AmplificationIncorrect Behavior Order: Early Amplification is a vulnerability where a product allows an entity to perform a legitimate but expensive operation
- CWE-409: Improper Handling of Highly Compressed Data (Data Amplification)Improper Handling of Highly Compressed Data is a vulnerability that occurs when a product fails to properly manage compressed inputs with
- CWE-410: Insufficient Resource PoolInsufficient Resource Pool is a vulnerability that occurs when a system's resource pool cannot meet peak demand, allowing attackers to exhaust
