[馃惛 Frogbot] Update version of org.postgresql:postgresql to 42.3.3 - #25
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
馃摝 Vulnerable Dependencies
Critical
馃敄 Details
Vulnerability Details
An unsafe deserialization in pgjdbc leads to arbitrary file overwrite when an attacker can control the pgjdbc configuration.
馃敩 JFrog Research Details
Description:
pgjdbc is an Open source JDBC driver written in Pure Java, which allows Java programs to connect to a PostgreSQL database using standard, database independent Java code.
The Java client that connects to the PostgreSQL DB needs to be configured with parameters such as the database host, database credentials and more.
It was discovered to two of these configuration parameters, specifically
loggerFileandloggerLevelcan cause arbitrary file overwrite on the Java client, if they are externally controlled.The vulnerability was disputed, since it is a security vulnerability in itself to expose JDBC connection parameters to untrusted input
The vulnerability can only be exploited when the
loggerFileandloggerLevelconnection properties can be controlled by an attacker. These properties are specified in the host, either explicitly in code -Or via a connection URL in code -
A public exploit exists that demonstrates writing a JSP webshell, which allows the attacker to run arbitrary shell commands on the victim (in cases where the servlet supports JSP)
馃惛 JFrog Frogbot