CRITICAL
Rule Definition
Security misconfiguration is the most commonly seen issue. This is commonly a result of insecure default configurations, incomplete or ad hoc configurations, open cloud storage, misconfigured HTTP headers, and verbose error messages containing sensitive information. Not only must all operating systems, frameworks, libraries, and applications be securely configured, but they must be patched/upgraded in a timely fashion.
Remediation
Do not disable NODE_TLS_REJECT_UNAUTHORIZED attributes
Violation Code Sample
process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0";
//or
export NODE_TLS_REJECT_UNAUTHORIZED = "0";
Fixed Code Sample
process.env.NODE_TLS_REJECT_UNAUTHORIZED = "1";
//or
export NODE_TLS_REJECT_UNAUTHORIZED = "1";
Reference
https://cwe.mitre.org/data/definitions/295.html
https://www.owasp.org/index.php/Top_10_2013-A5-Security_Misconfiguration
https://www.owasp.org/index.php/Top_10-2017_A6-Security_Misconfiguration
Related Technologies
Technical Criterion
Secure Coding - Input Validation
About CAST Appmarq
CAST Appmarq is by far the biggest repository of data about real IT systems. It's built on thousands of analyzed applications, made of 35 different technologies, by over 300 business organizations across major verticals. It provides IT Leaders with factual key analytics to let them know if their applications are on track.