Security detectors
Privilege escalation happens when a malicious user gains elevated access to resources that should be unavailable to them.
Using the spawn
or forkserver
start method without importing the main module might lead to unexpected behavior (for example, it might cause a RuntimeError
).
An integer overflow might might cause security issues when it is used for resource management or execution control.
Unauthenticated LDAP requests can allow untrusted access to LDAP servers.
Constructing path names with unsanitized user input can lead to path traversal attacks (for example, ../../..
) that allow an attacker access to file system resources.
Weak file permissions can lead to privilege escalation.
Writing unsanitized user data to a file is unsafe.
Objects that parse or handle XML can lead to XML External Entity (XXE) attacks when misconfigured.
Improper input validation can enable attacks and lead to unwanted behavior.
Your code doesn't sufficiently authenticate identities provided by its users.
Missing pagination on a paginated call can lead to inaccurate results.
Insecure cookies can lead to unencrypted transmission of sensitive data.
APIs that are not recommended were found - Low Severity.
Not setting the connection timeout parameter can cause a blocking socket connection.
Potentially unsanitized user input in XPath queries can allow an attacker to control the query in unwanted or insecure ways.
Missing authorization checks can lead to unauthorized access to a resource or performance of an action.
Use of untrusted inputs in a SQL database query can enable attackers to read, modify, or delete sensitive data in the database
Lack of validation of a security certificate can lead to host impersonation and sensitive data leaks.
User-controlled input that specifies a link to an external site could lead to phishing attacks and allow user credentials to be stolen.
Calls to mutually exclusive methods were found in the code.
Stack traces can be hard to use for debugging.
Api Logging Disabled may lead to unable to access log and does not record the event.
Constructing operating system or shell commands with unsanitized user input can lead to inadvertently running malicious code.
Logging unencrypted AWS credentials can expose them to an attacker.
Expanding unsanitized archive files taken as input can lead to zip bomb attacks.
Encryption that is dependent on conditional logic, such as an if...then
clause, might cause unencrypted sensitive data to be stored.
Insufficiently restrictive file uploads can lead to inadvertently running malicious code.
Connections that use insecure protocols transmit data in cleartext, which can leak sensitive information.
Failing to set the AuthenticateOnUnsubscribe
flag to True
when confirming an SNS subscription can lead to unauthenticated cancellations.
Binding the socket with an empty IP address can introduce security risks.
Cross-Origin Resource Sharing policies that are too permissive may lead to security vulnerabilities.
Insecure configuration can lead to a cross-site request forgery (CRSF) vulnerability.
Passing a parent process object in a child process can prevent its garbage collection.
Weak algorithm used for Password Hashing. Consider using stronger algorithms, such as Argon2, PBKDF2, or scrypt.
Exposure of sensitive information can lead to an unauthorized actor having access to the information.
Client-side decryption followed by reencryption is inefficient and can lead to sensitive data leaks.
Overriding environment variables that are reserved by AWS Lambda might lead to unexpected behavior.
Passing an unsanitized user argument to a function call makes your code insecure.
Software system fails to properly track or release resources during its operation. This can lead to resource leaks.
Allocated resources are not released properly.
The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
Public method parameters should be validated for nullness, unexpected values, and malicious values.
Improper filtering of Amazon Machine Images (AMIs) can result in loading an untrusted image, a potential security vulnerability.
Sensitive or critical information is not encrypted before storage or transmission in the product.
APIs that are not recommended were found - High Severity.
Weak, broken, or misconfigured cryptography can lead to security vulnerabilities.
An unencrypted bucket could lead to sensitive data exposure.
Relying on potentially untrusted user inputs when constructing web application outputs can lead to cross-site scripting vulnerabilities.
Insecure ways of creating temporary files and directories can lead to race conditions, privilege escalation, and other security vulnerabilities.
Using an AWS KMS key helps follow the standard security advice of granting least privilege to objects generated by the project.
APIs that are not recommended were found.
Deserialization of untrusted objects can lead to security vulnerabilities such as inadvertently running remote code.
Unsanitized wildcards or special matching symbols in user-provided strings can enable attacks and lead to unwanted behavior.
Obsolete, broken, or weak hashing algorithms can lead to security vulnerabilities.
Using AutoAddPolicy
or WarningPolicy
can allow a malicious server to impersonate a trusted server.
Using untrusted inputs in a log statement can enable attackers to break the log's format, forge log entries, and bypass log monitors.
Weak obfuscation while configuring a web request.
Scripts generated from unsanitized inputs can lead to malicious behavior and inadvertently running code remotely.
Binding to all network interfaces can open a service up to traffic on interfaces that are not properly documented or secured.
Hardcoding an IP address can cause security problems.
Credentials, such as passwords and access keys, should not be hardcoded in source code.
Insufficient sanitization of potentially untrusted URLs on the server side can allow server requests to unwanted destinations.
Untrusted user imports in the importlib.import_module()
function allow attacks.
APIs that are not recommended were found - Medium Severity.
Pickling issues on Cloudpickle Load.
LDAP queries that rely on potentially untrusted inputs can allow attackers to read or modify sensitive data, run code, and perform other unwanted actions.
Credentials that are stored in clear text can be intercepted by a malicious actor.
Not setting the S3 bucket owner condition might introduce a risk of accidentally using a wrong bucket.
The AWS resource is missing appropriate encryption.