CWE-748
Grouping ProhibitedCERT C Secure Coding Standard (2008) Appendix - POSIX (POS)
Status: Obsolete
Weaknesses in this category are related to the rules and recommendations in the POSIX (POS) appendix of the CERT C Secure Coding Standard (2008).
Grouping entries organize the catalogue and should not be used to map the root cause of a vulnerability.
Mapping guidance
This entry is a Grouping. Using groupings for mapping has been discouraged since 2019. They 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.
Relationships and members
Notes
Relationship
In the 2008 version of the CERT C Secure Coding standard, the following rules were mapped to the following CWE IDs:
CWE-59 POS01-C Check for the existence of links when dealing with files
CWE-170 POS30-C Use the readlink() function properly
CWE-242 POS33-C Do not use vfork()
CWE-272 POS02-C Follow the principle of least privilege
CWE-273 POS37-C Ensure that privilege relinquishment is successful
CWE-363 POS35-C Avoid race conditions while checking for the existence of a symbolic link
CWE-366 POS00-C Avoid race conditions with multiple threads
CWE-562 POS34-C Do not call putenv() with a pointer to an automatic variable as the argument
CWE-667 POS31-C Do not unlock or destroy another thread's mutex
CWE-686 POS34-C Do not call putenv() with a pointer to an automatic variable as the argument
CWE-696 POS36-C Observe correct revocation order while relinquishing privileges
Content history
updated Description, Name, Relationship_Notes
updated Description, Name, References, Relationship_Notes, Relationships
updated Mapping_Notes
updated Mapping_Notes
updated Mapping_Notes, Type
0 vulnerabilities reference this CWE, most recent first.
No vulnerabilities reference this CWE.
No mitigation information available for this CWE.
No CAPEC attack patterns related to this CWE.