TypeScript detectors
Showing all detectors for the TypeScript language.
Browse by tags
Browse all detectors by tags.
Browse by severity
Browse all detectors by severity.
Browse by category
Browse all detectors by category.
Browse all detectors
An integer overflow might cause security issues when it is used for resource management or execution control.
The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
Insecure cookies can lead to unencrypted transmission of sensitive data.
Logging unencrypted AWS credentials can expose them to an attacker.
The use of untrusted inputs in a SQL database query can enable attackers to read, modify, or delete sensitive data in the database.
Connections that use insecure protocols transmit data in cleartext, which can leak sensitive information.
Use of new Function()
can be dangerous if used to evaluate dynamic content.
Unchecked failures can lead to data loss.
Expanding unverified archive files without controlling the size of the expanded data can lead to zip bomb attacks.
Missing pagination on a paginated call can lead to inaccurate results.
Potentially unsanitized user input in XPath queries can allow an attacker to control the query in unwanted or insecure ways.
The logging of sensitive information can expose the information to potential attackers.
Overriding environment variables that are reserved by AWS Lambda might lead to unexpected behavior.
Cross-origin resource sharing policies that are too permissive could lead to security vulnerabilities.
Improper input validation can enable attacks and lead to unwanted behavior.
Hardcoded credentials can be intercepted by malicious actors.
The incorrect use of super()
causes problems.
Truncation errors occur when a primitive is cast to a primitive of a smaller size and data is lost in the conversion.
Checks if nan is used is comparison.
Missing checks might cause silent failures that are harder to debug.
An object attribute constructed from a user-provided input should not be passed directly to a method.
The application incorrectly restricts frame objects or UI layers that belong to another application or domain.
Using pseudorandom number generators (PRNGs) is security-sensitive.
The AWS resource is missing appropriate encryption.
Swallowing exceptions, without rethrowing or logging them, can make it hard to understand why your application is failing.
Constructing HTTP response headers from user-controlled data is unsafe.
New Object() has been used for object creation instead of {}.
Hardcoding an IP address can cause security problems.
Improper filtering of Amazon Machine Images (AMIs) can result in loading an untrusted image, which is a potential security vulnerability.
Weak obfuscation of web requests makes your application vulnerable.
File name should not be used to do the file operations.
Lack of validation of a security certificate can lead to host impersonation and sensitive data leaks.
The software allows user input to control or influence paths or file names that are used in file system operations.
Insufficient key sizes can lead to brute force attacks.
Improper input validation can enable attacks and lead to unwanted behavior.
Objects that parse or handle XML can lead to XML external entity (XXE) attacks when they are misconfigured.
Insecure string comparison can lead to a timing-attack.
Not setting the Amazon S3 bucket owner condition could lead to accidentally using the wrong bucket.
Obsolete, broken, or weak hashing algorithms can lead to security vulnerabilities.
Session fixation might allow an attacker to steal authenticated session IDs.
The product relies on default credentials(including passwords and cryptographic keys) for potentially vital functions.
Writing unsanitized user data to a file is unsafe.
An improper buffer read operation might lead to a BufferOverflowException
.
Significant content length can lead to denial of service.
Using untrusted inputs in a log statement can enable attackers to break the log's format, forge log entries, and bypass log monitors.
Type confusion occurs when an application accesses a resource using a type that is incompatible with its original type.
Insufficient sanitization of potentially untrusted URLs on the server side can allow server requests to unwanted destinations.
Using an AWS KMS key helps follow the standard security advice of granting least privilege to objects generated by the project.
Custom polling can be inefficient and prone to error. Consider using AWS waiters instead.
Checks if the undefined is used as variable.
indexOf
method should not be compared with values greater than zero.
String passed to setInterval
or setTimeout
can cause the JavaScript engine to evaluate, which can lead to a security risk.
A batch request that doesn't check for failed items can lead to loss of data.
Passing an unsanitized user argument to a function call makes your code insecure.
Insecure ways of creating temporary files and directories can lead to race conditions, privilege escalation, and other security vulnerabilities.
A batch request that doesn't check for failed records can lead to loss of data.
Api Logging Disabled may lead to unable to access log and does not record the event.
The software does not restrict or incorrectly restrict access to a resource from an unauthorized actor.
The elevated privilege level should be dropped immediately after the operation is performed.
Checks if the extension of a file uploaded by a user is validated before the file is saved.
Allocated resources are not released properly.
To always return the subscription ARN, set the ReturnSubscriptionArn
argument to True
.
Updating object attributes obtained from external sources is security sensitive.
Missing authentication checks can lead to unauthorized access to a resource or performance of an action.
The typeof operator should only be compared to valid values.
Sensitive or critical information is not encrypted before storage or transmission in the product.
Failing to set the AuthenticateOnUnsubscribe
flag to True
when confirming an SNS subscription can lead to unauthenticated cancellations.
Insecure configuration can lead to a cross-site request forgery (CRSF) vulnerability.
Client-side decryption followed by encryption is inefficient and can lead to sensitive data leaks.
Weak, broken, or misconfigured cryptography can lead to security vulnerabilities.
Deserialization of untrusted objects can lead to security vulnerabilities such as, inadvertently running remote code.
Credentials that are stored in clear text can be intercepted by a malicious actor.
Improper handling of case sensitivity when accessing a resource can lead to inconsistent results.
Scripts generated from unsanitized inputs can lead to malicious behavior and inadvertently running code remotely.
Disabled or incorrectly used protection mechanism can lead to security vulnerabilities.
This code uses deprecated methods, which suggests that it has not been recently reviewed or maintained.
Exposure of sensitive information can lead to an unauthorized actor having access to the information.
DNS prefetching can cause latency and privacy issues.
The product unintentionally grants unauthorized actors access to a resource by placing it in the wrong control sphere.
Checks if the none
algorithm is used in a JWT token
parsing.
Weak file permissions can lead to privilege escalation.
Do not fetch sensitive information from a GET request.
In the case of a security-critical event, the product fails to either log the event or misses crucial details in the logged information.
Constructing operating system or shell commands with unsanitized user input can lead to inadvertently running malicious code.
User input can be vulnerable to injection attacks.
Unverified hostnames lead to security vulnerabilities.
Creating file paths from untrusted input might give a malicious actor access to sensitive files.
Unverified origins of messages and identities in cross-origin communications can lead to security vulnerabilities.
LDAP queries that rely on potentially untrusted inputs can allow attackers to read or modify sensitive data, run code, and perform other unwanted actions.
Do not bind the SNS Publish operation with the SNS Subscribe or Create Topic operation.
An unencrypted bucket could lead to sensitive data exposure.
Non-literal input to a regular expression might lead to a denial of service attack.
Stack traces can be hard to use for debugging.
Allowing hidden files while serving files from a given root directory can cause information leakage.
APIs that are not recommended were found.
Checks for lazy module loading.
Disabling the HTML autoescape mechanism exposes your web applications to attacks.
The software does not restrict or incorrectly restrict access to a resource from an unauthorized actor.
Relying on potentially untrusted user inputs when constructing web application outputs can lead to cross-site scripting vulnerabilities.
Encryption that is dependent on conditional logic, such as an if...then
clause, might cause unencrypted sensitive data to be stored.
Recreating AWS clients in each Lambda function invocation is expensive.
User-controlled input that specifies a link to an external site could lead to phishing attacks and allow user credentials to be stolen.
Security decisions should not depend on branching that can be influenced by untrusted or client-provided data.