Amazon CodeGuruDetector Library Sign in to CodeGuru

CodeGuru

Detector Library

JSX detectors (78/78)

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

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

jsx/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}