Amazon QDetector Library Sign in to Amazon Q

Q

Detector Library

TypeScript detectors (104/104)

Integer overflow AWS insecure transmission CDK Insecure cookie AWS credentials logged SQL injection Insecure connection using unencrypted protocol New function detected Batch request with unchecked failures Unvalidated expansion of archive files Missing pagination XPath injection Logging of sensitive information Override of reserved variable names in a Lambda function Insecure CORS policy Improper input validation Hardcoded credentials Invoke super appropriately Numeric truncation error Avoid nan in comparison Missing check on method output Insufficiently protected credentials Improper restriction of rendered UI layers or frames Pseudorandom number generators AWS missing encryption CDK Catch and swallow exception Header injection Use {} instead of new Object()Hardcoded IP address Untrusted Amazon Machine Images Weak obfuscation of web requests File Race Bad Improper certificate validation Sendfile injection Cryptographic key generator improper input validation cdk XML external entity Timing attack Missing Amazon S3 bucket owner condition Insecure hashing Session fixation Use of Default Credentials CDK File injection Improper Restriction of Operations within the Bounds of a Memory Buffer Limit request length Log injection Type confusion Server side request forgery aws kmskey encryption cdk Inefficient polling of AWS resource Avoid Undefined As Variable Name Index of method comparison String passed to `setInterval` or `setTimeout`Data loss in a batch request Tainted input for Docker API Insecure temporary file or directory Check failed records when using kinesis AWS api logging disabled cdk Improper Access Control CDK Least privilege violation File extension validation Resource leak Set SNS Return Subscription ARN Insecure object attribute modification Missing Authentication for Critical Function CDK Typeof expression AWS missing encryption of sensitive data cdk Unauthenticated Amazon SNS unsubscribe requests might succeed Cross-site request forgery Client-side KMS reencryption Insecure cryptography Deserialization of untrusted object Clear text credentials Improper handling of case sensitivity Unsanitized input is run as code Protection mechanism failure Use of a deprecated method Sensitive information leak DNS prefetching Exposure of Sensitive Information CDK Insecure JWT parsing Loose file permissions Missing Authorization CDK Sensitive query string Insufficient Logging CDK OS command injection NoSQL injection Unverified hostname Path traversal Origins-verified cross-origin communications LDAP injection SNS don't bind subscribe and publish S3 partial encrypt CDK Non-literal regular expression Stack trace exposure File and directory information exposure Usage of an API that is not recommended Lazy Load Module Disabled HTML autoescape Improper access control Cross-site scripting Sensitive data stored unencrypted due to partial encryption AWS client not reused in a Lambda function URL redirection to untrusted site Untrusted data in security decision

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

typescript/unverified-hostname@v1.0

Category

Common Weakness Enumeration (CWE)

Tags

Noncompliant example

1import https from '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: any) {
10      console.log("unverified hostname");
11    },
12  };
13  var request = https.request(options, (response: any) => {
14    let data = "hello";
15    console.log(data);
16  });
17}

Compliant example

1import https from '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: string) {
10      if (host != "github.com") {
11        console.log("verified hostname");
12      }
13    },
14  };
15  var request = https.request(options, (response: any) => {
16    let data = "hello";
17    console.log(data);
18  });
19}