Weaknesses in this category are related to rules in the Platform Security (SEC) chapter of The CERT Oracle Secure Coding Standard for Java (2011).
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | V | 844 | Weaknesses Addressed by The CERT Oracle Secure Coding Standard for Java (2011) |
| HasMember | Allowed | V | 111 | Direct Use of Unsafe JNI |
| HasMember | Allowed | B | 266 | Incorrect Privilege Assignment |
| HasMember | Allowed | B | 272 | Least Privilege Violation |
| HasMember | Discouraged | C | 300 | Channel Accessible by Non-Endpoint |
| HasMember | Allowed | B | 302 | Authentication Bypass by Assumed-Immutable Data |
| HasMember | Allowed | B | 319 | Cleartext Transmission of Sensitive Information |
| HasMember | Allowed | B | 347 | Improper Verification of Cryptographic Signature |
| HasMember | Allowed | B | 470 | Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') |
| HasMember | Allowed | B | 494 | Download of Code Without Integrity Check |
| HasMember | Allowed-with-Review | C | 732 | Incorrect Permission Assignment for Critical Resource |
| HasMember | Allowed | B | 807 | Reliance on Untrusted Inputs in a Security Decision |
This entry is a Category. Using categories for mapping has been discouraged since 2019. Categories are informal organizational groupings of weaknesses that can help CWE users with data aggregation, navigation, and browsing. However, they are not weaknesses in themselves.
See member weaknesses of this category.
| Taxonomy Name | Entry ID | Fit | Entry Name |
|---|