High
Showing all detectors for the TypeScript language with high severity.
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.
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.
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.
Truncation errors occur when a primitive is cast to a primitive of a smaller size and data is lost in the conversion.
The application incorrectly restricts frame objects or UI layers that belong to another application or domain.
The AWS resource is missing appropriate encryption.
Constructing HTTP response headers from user-controlled data is unsafe.
Weak obfuscation of web requests makes your application vulnerable.
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.
The product relies on default credentials(including passwords and cryptographic keys) for potentially vital functions.
Writing unsanitized user data to a file is unsafe.
Using untrusted inputs in a log statement can enable attackers to break the log's format, forge log entries, and bypass log monitors.
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.
String passed to setInterval
or setTimeout
can cause the JavaScript engine to evaluate, which can lead to a security risk.
Passing an unsanitized user argument to a function call makes your code insecure.
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.
Missing authentication checks can lead to unauthorized access to a resource or performance of an action.
Sensitive or critical information is not encrypted before storage or transmission in the product.
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.
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.
Disabled or incorrectly used protection mechanism can lead to security vulnerabilities.
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.
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.
An unencrypted bucket could lead to sensitive data exposure.
Non-literal input to a regular expression might lead to a denial of service attack.
APIs that are not recommended were found.
Disabling the HTML autoescape mechanism exposes your web applications to attacks.
Relying on potentially untrusted user inputs when constructing web application outputs can lead to cross-site scripting vulnerabilities.
User-controlled input that specifies a link to an external site could lead to phishing attacks and allow user credentials to be stolen.