|
Category ID: 859
Vulnerability Mapping:
PROHIBITED
This CWE ID must not be used to map to real-world vulnerabilities
|
Summary Membership| Nature | Type | ID | Name |
|---|---|---|---|
| MemberOf |  View - a subset of CWE entries that provides a way of examining CWE content. The two main view structures are Slices (flat lists) and Graphs (containing relationships between entries). |
844 | Weaknesses Addressed by The CERT Oracle Secure Coding Standard for Java (2011) |
| HasMember |  Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource. |
111 | Direct Use of Unsafe JNI |
| HasMember |  Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource. |
266 | Incorrect Privilege Assignment |
| HasMember | Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource. |
272 | Least Privilege Violation |
| HasMember |  Class - a weakness that is described in a very abstract fashion, typically independent of any specific language or technology. More specific than a Pillar Weakness, but more general than a Base Weakness. Class level weaknesses typically describe issues in terms of 1 or 2 of the following dimensions: behavior, property, and resource. |
300 | Channel Accessible by Non-Endpoint |
| HasMember | Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource. |
302 | Authentication Bypass by Assumed-Immutable Data |
| HasMember | Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource. |
319 | Cleartext Transmission of Sensitive Information |
| HasMember | Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource. |
347 | Improper Verification of Cryptographic Signature |
| HasMember | Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource. |
470 | Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') |
| HasMember | Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource. |
494 | Download of Code Without Integrity Check |
| HasMember | Class - a weakness that is described in a very abstract fashion, typically independent of any specific language or technology. More specific than a Pillar Weakness, but more general than a Base Weakness. Class level weaknesses typically describe issues in terms of 1 or 2 of the following dimensions: behavior, property, and resource. |
732 | Incorrect Permission Assignment for Critical Resource |
| HasMember | Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource. |
807 | Reliance on Untrusted Inputs in a Security Decision |
Vulnerability Mapping Notes References Content
History| Submissions |
|||
|---|---|---|---|
| Submission Date | Submitter | Organization | |
|
2011-05-24
(CWE 1.13, 2011-06-01) |
CWE Content Team | MITRE | |
 Modifications |
|||
| Modification Date | Modifier | Organization | |
|
2023-06-29
(CWE 4.12, 2023-06-29) |
CWE Content Team | MITRE | |
| updated Mapping_Notes | |||
|
2023-04-27
(CWE 4.11, 2023-04-27) |
CWE Content Team | MITRE | |
| updated Mapping_Notes | |||
|
2019-01-03
(CWE 3.2, 2019-01-03) |
CWE Content Team | MITRE | |
| updated Description, Name, References | |||
|
2011-09-13
(CWE 2.1, 2011-09-13) |
CWE Content Team | MITRE | |
| updated Relationships | |||
| Previous Entry Names |
|||
| Change Date | Previous Entry Name | ||
| 2019-01-03 | CERT Java Secure Coding Section 14 - Platform Security (SEC) | ||
