Vulnerability · Published Nov 23, 2022 · Assigned by GitHub_M

CVE-2022-41946TemporaryFolder on unix-like systems does not limit access to created files in pgjdbc

Medium 4.7

In plain English

A medium-severity information exposure in pgjdbc from pgjdbc. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.6% (higher than 46% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)4.7Medium
Exploit odds (30 days)0.6%top 53.7% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
AlmaLinux:8postgresql-jdbc42.2.14-2.el8ALSA-2023:2867
AlmaLinux:9postgresql-jdbc42.2.27-1.el9ALSA-2023:2378
AlmaLinux:8postgresql-jdbc-javadoc42.2.14-2.el8ALSA-2023:2867
Alpine:v3.20java-postgresql-jdbc42.5.1-r0ALPINE-CVE-2022-41946
Alpine:v3.21java-postgresql-jdbc42.5.1-r0ALPINE-CVE-2022-41946
Alpine:v3.22java-postgresql-jdbc42.5.1-r0ALPINE-CVE-2022-41946
Alpine:v3.23java-postgresql-jdbc42.5.1-r0ALPINE-CVE-2022-41946
Alpine:v3.24java-postgresql-jdbc42.5.1-r0ALPINE-CVE-2022-41946
Debian:12libpgjava42.5.1-1DEBIAN-CVE-2022-41946
Debian:13libpgjava42.5.1-1DEBIAN-CVE-2022-41946
Debian:14libpgjava42.5.1-1DEBIAN-CVE-2022-41946
Mavenorg.postgresql:postgresql42.4.3GHSA-562r-vg33-8x8h
Mavenorg.postgresql:postgresql42.2.27GHSA-562r-vg33-8x8h
Mavenorg.postgresql:postgresql42.3.8GHSA-562r-vg33-8x8h
Mavenorg.postgresql:postgresql42.5.1GHSA-562r-vg33-8x8h
Ubuntu:22.04:LTSlibpgjavano fix listedUBUNTU-CVE-2022-41946
Ubuntu:24.04:LTSlibpgjavano fix listedUBUNTU-CVE-2022-41946
Ubuntu:25.10libpgjavano fix listedUBUNTU-CVE-2022-41946
Ubuntu:26.04:LTSlibpgjavano fix listedUBUNTU-CVE-2022-41946
Ubuntu:26.10libpgjavano fix listedUBUNTU-CVE-2022-41946

Affected products (as reported)

VendorProductVersions
pgjdbc pgjdbc >= 42.2.0, < 42.2.27> 42.3.0, < 42.3.8>= 42.4.0, < 42.4.3>= 42.5.0, < 42.5.1

Weakness: CWE-200, CWE-377 · Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

References