TemporaryFolder on unix-like systems does not limit access to created files in pgjdbc
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 42.2.27, 42.3.8, 42.4.3, 42.5.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
pgjdbc is an open source postgresql JDBC Driver. In affected versions a prepared statement using either `PreparedStatement.setText(int, InputStream)` or `PreparedStatemet.setBytea(int, InputStream)` will create a temporary file if the InputStream is larger than 2k. This will create a temporary file which is readable by other users on Unix like systems, but not MacOS. On Unix like systems, the system's temporary directory is shared between all users on that system. Because of this, when files and directories are written into this directory they are, by default, readable by other users on that same system. This vulnerability does not allow other users to overwrite the contents of these directories or files. This is purely an information disclosure vulnerability. Because certain JDK file system APIs were only added in JDK 1.7, this this fix is dependent upon the version of the JDK you are using. Java 1.7 and higher users: this vulnerability is fixed in 4.5.0. Java 1.6 and lower users: no patch is available. If you are unable to patch, or are stuck running on Java 1.6, specifying the java.io.tmpdir system environment variable to a directory that is exclusively owned by the executing user will mitigate this vulnerability.
Timeline
- CVE published
- Record last updated
Affected versions
- pgjdbc pgjdbc
From 42.2.0 · fixed in 42.2.27; From 42.3.0 · fixed in 42.3.8; From 42.4.0 · fixed in 42.4.3; From 42.5.0 · fixed in 42.5.1
- org.postgresql:postgresqlMaven
From 42.2.0 · fixed in 42.2.27
- org.postgresql:postgresqlMaven
From 42.3.0 · fixed in 42.3.8
- org.postgresql:postgresqlMaven
From 42.4.0 · fixed in 42.4.3
- org.postgresql:postgresqlMaven
From 42.5.0 · fixed in 42.5.1