High
Showing all detectors for the Python language with high severity.
Privilege escalation happens when a malicious user gains elevated access to resources that should be unavailable to them.
The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
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.
The product relies on default credentials(including passwords and cryptographic keys) for potentially vital functions.
The product unintentionally grants unauthorized actors access to a resource by placing it in the wrong control sphere.
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.
Do not pass generic exception.
APIs that are not recommended were found - High Severity.
Using outdated multiprocessing API calls and parameters is not recommended.
An unencrypted bucket could lead to sensitive data exposure.
Your code doesn't sufficiently authenticate identities provided by its users.
Relying on potentially untrusted user inputs when constructing web application outputs can lead to cross-site scripting vulnerabilities.
Insecure cookies can lead to unencrypted transmission of sensitive data.
APIs that are not recommended were found.
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.
Deserialization of untrusted objects can lead to security vulnerabilities such as inadvertently running remote code.
Use of untrusted inputs in a SQL database query can enable attackers to read, modify, or delete sensitive data in the database
Unsanitized wildcards or special matching symbols in user-provided strings can enable attacks and lead to unwanted behavior.
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.
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.
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.
The os.close()
does not work on some platforms.
Expanding unsanitized archive files taken as input can lead to zip bomb attacks.
Synchronous publication of AWS Lambda metrics is inefficient.
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.
Insecure configuration can lead to a cross-site request forgery (CRSF) vulnerability.
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.
Weak algorithm used for Password Hashing. Consider using stronger algorithms, such as Argon2, PBKDF2, or scrypt.
Missing authentication checks can lead to unauthorized access to a resource or performance of an action.
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.
The constructors for the hashlib
module are faster than new()
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.
Overriding environment variables that are reserved by AWS Lambda might lead to unexpected behavior.
The AWS resource is missing appropriate encryption.