pgadmin4@6.5 vulnerabilities
PostgreSQL Tools
-
latest version
8.13
-
latest non vulnerable version
-
first published
4 years ago
-
latest version published
11 days ago
-
licenses detected
- [0,)
Direct Vulnerabilities
Known vulnerabilities in the pgadmin4 package. This does not include vulnerabilities belonging to this package’s dependencies.
Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.Vulnerability | Vulnerable Version |
---|---|
pgadmin4 is a PostgreSQL Tools Affected versions of this package are vulnerable to Information Exposure due to improper handling of OAuth2 authentication credentials. How to fix Information Exposure? Upgrade |
[,8.12)
|
pgadmin4 is a PostgreSQL Tools Affected versions of this package are vulnerable to Cross-site Scripting (XSS) via the How to fix Cross-site Scripting (XSS)? Upgrade |
[,8.6)
|
pgadmin4 is a PostgreSQL Tools Affected versions of this package are vulnerable to Authentication Bypass due to a flaw in the multi-factor authentication process. An attacker with knowledge of a legitimate account's username and password may authenticate to the application and perform sensitive actions within the application, such as managing files and executing SQL queries, regardless of the account's MFA enrollment status. How to fix Authentication Bypass? Upgrade |
[,8.6)
|
pgadmin4 is a PostgreSQL Tools Affected versions of this package are vulnerable to Improper Control of Generation of Code ('Code Injection') via the validate binary path API. An attacker can execute arbitrary code on the server hosting the application, posing a severe risk to the integrity of the database management system and the security of the underlying data. How to fix Improper Control of Generation of Code ('Code Injection')? Upgrade |
[,8.5)
|
pgadmin4 is a PostgreSQL Tools Affected versions of this package are vulnerable to Deserialization of Untrusted Data due to the use of a file-based session management approach where session files are saved on disk as pickle objects. An attacker can execute arbitrary code on the system by manipulating the session ID to escape the intended session folder path and point to a maliciously crafted file. How to fix Deserialization of Untrusted Data? Upgrade |
[,8.4)
|
pgadmin4 is a PostgreSQL Tools Affected versions of this package are vulnerable to Command Injection when the HTTP API validates the path a user selects to external PostgreSQL utilities such as NOTE: This issue does not affect pgAdmin's desktop mode. How to fix Command Injection? Upgrade |
[,7.7)
|
pgadmin4 is a PostgreSQL Tools Affected versions of this package are vulnerable to Directory Traversal due to improper input sanitization, which allows pgAdmin users who are authenticated to access each other's directories and files by providing relative paths. How to fix Directory Traversal? Upgrade |
[,6.19)
|
pgadmin4 is a PostgreSQL Tools Affected versions of this package are vulnerable to Open Redirect. Allows a remote unauthenticated attacker to redirect a user to an arbitrary web site and conduct a phishing attack by having a user access a specially crafted URL. How to fix Open Redirect? Upgrade |
[,6.14)
|
pgadmin4 is a PostgreSQL Tools Affected versions of this package are vulnerable to Arbitrary Code Injection by allowing an unauthenticated user to call an Note: This issue does not affect users running How to fix Arbitrary Code Injection? Upgrade |
[,6.17)
|
pgadmin4 is a PostgreSQL Tools Affected versions of this package are vulnerable to Directory Traversal. A malicious user can construct an How to fix Directory Traversal? Upgrade |
[,6.7)
|