Amazon CodeGuruDetector Library Sign in to CodeGuru

CodeGuru

Detector Library

JavaScript detectors (78/78)

Improper access control Sensitive data stored unencrypted due to partial encryption Pseudorandom number generators OS command injection URL redirection to untrusted site Integer overflow Protection mechanism failure Non-literal regular expression Tainted input for Docker API Usage of an API that is not recommended XML external entity Server-side request forgery New function detected Stack trace exposure Timing attack SNS don't bind subscribe and publish Invoke super appropriately NoSQL injection Hardcoded credentials Insecure cookie Cross-site scripting Hardcoded IP address AWS credentials logged XPath injection Data loss in a batch request Path traversal Least privilege violation DNS prefetching Resource leak Insufficiently protected credentials File extension validation Insecure connection using unencrypted protocol Cross-site request forgery Typeof expression Set SNS Return Subscription ARN File and directory information exposure Missing Amazon S3 bucket owner condition Insecure hashing Numeric truncation error Client-side KMS reencryption AWS client not reused in a Lambda function LDAP injection Batch request with unchecked failures Cryptographic key generator Unauthenticated Amazon SNS unsubscribe requests might succeed Unverified hostname Origins-verified cross-origin communications Loose file permissions Unsanitized input is run as code Missing pagination Untrusted Amazon Machine Images Improper certificate validation Insecure CORS policy Deserialization of untrusted object Sensitive information leak Check failed records when using kinesis Weak obfuscation of web requests Catch and swallow exception Logging of sensitive information Limit request length String passed to `setInterval` or `setTimeout`Log injection Override of reserved variable names in a Lambda function Improper restriction of rendered UI layers or frames Insecure cryptography Insecure object attribute modification Session fixation Avoid nan in comparison Improper input validation Disabled HTML autoescape Use of a deprecated method Unvalidated expansion of archive files File injection Sendfile injection SQL injection Header injection Insecure temporary file or directory Inefficient polling of AWS resource

Unverified hostname High

Unverified hostnames can allow man-in-the-middle attacks. When establishing an SSL/TLS connection, use the default checkServerIdentity or confirm that the certificate's hostname-specific data matches the server hostname to avoid these attacks.

Detector ID

javascript/unverified-hostname@v1.0

Category

Common Weakness Enumeration (CWE)

Tags

Noncompliant example

1var https = require("https")
2function unverifiedHostnameNoncompliant() {
3    var options = {
4        hostname: 'encrypted.google.com',
5        port: 3000,
6        path: '/pathname/',
7        method: 'POST',
8        // Noncompliant: hostname is not verified.
9        checkServerIdentity: function (host) {
10            console.log('unverified hostname')
11        }
12    }
13    var request = https.request(options, (response) => {
14        let data = 'hello'
15        console.log(data)
16    })
17}

Compliant example

1var https = require("https")
2function unverifiedHostnameCompliant() {
3    var options = {
4        hostname: 'encrypted.google.com',
5        port: 3000,
6        path: '/pathname/',
7        method: 'POST',
8        // Compliant: hostname is verified before using it.
9        checkServerIdentity: function (host) {
10            if (host != "github.com") {
11                console.log('verified hostname')
12            }
13        }
14    }
15    var request = https.request(options, (response) => {
16        let data = 'hello'
17        console.log(data)
18    })
19}