CWE
668 200 377
Advisory Published
Advisory Published
Updated

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

First published: Wed Nov 23 2022(Updated: )

**Vulnerability** `PreparedStatement.setText(int, InputStream)` and `PreparedStatemet.setBytea(int, InputStream)` will create a temporary file if the InputStream is larger than 51k Example of vulnerable code: ```java String s = "some very large string greater than 51200 bytes"; PreparedStatement.setInputStream(1, new ByteArrayInputStream(s.getBytes()) ); ``` This will create a temporary file which is readable by other users on Unix like systems, but not MacOS. Impact 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. When analyzing the impact of this vulnerability, here are the important questions to ask: Is the driver running in an environment where the OS has other untrusted users. If yes, and you answered 'yes' to question 1, this vulnerability impacts you. If no, this vulnerability does not impact you. Patches 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.8 and higher users: this vulnerability is fixed in 42.2.27, 42.3.8, 42.4.3, 42.5.1 Java 1.7 users: this vulnerability is fixed in 42.2.27.jre7 Java 1.6 and lower users: no patch is available; you must use the workaround below. Workarounds 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 fix this vulnerability. References [CWE-200: Exposure of Sensitive Information to an Unauthorized Actor](https://cwe.mitre.org/data/definitions/200.html) Fix commit https://github.com/pgjdbc/pgjdbc/commit/9008dc9aade6dbfe4efafcd6872ebc55f4699cf5 Similar Vulnerabilities Google Guava - https://github.com/google/guava/issues/4011 Apache Ant - https://nvd.nist.gov/vuln/detail/CVE-2020-1945 JetBrains Kotlin Compiler - https://nvd.nist.gov/vuln/detail/CVE-2020-15824

Credit: security-advisories@github.com security-advisories@github.com

Affected SoftwareAffected VersionHow to fix
redhat/postgresql-jdbc<0:42.2.14-2.el8
0:42.2.14-2.el8
redhat/postgresql-jdbc<0:42.2.27-1.el9
0:42.2.27-1.el9
redhat/candlepin<0:4.1.20-1.el8
0:4.1.20-1.el8
redhat/candlepin<0:4.2.13-1.el8
0:4.2.13-1.el8
Postgresql Postgresql Jdbc Driver>=42.2.0<42.2.27
Postgresql Postgresql Jdbc Driver>=42.3.0<42.3.8
Postgresql Postgresql Jdbc Driver>=42.4.0<42.4.3
Postgresql Postgresql Jdbc Driver=42.5.0
Postgresql Postgresql Jdbc Driver=42.5.0-rc1
Debian Debian Linux=10.0
redhat/postgres<42.2.27.
42.2.27.
redhat/postgres<42.2.27
42.2.27
redhat/postgres<42.3.8
42.3.8
redhat/postgres<42.4.3
42.4.3
redhat/postgres<42.5.1
42.5.1
IBM Cloud Pak for Business Automation<=V22.0.2
IBM Cloud Pak for Business Automation<=V21.0.3 - V21.0.3-IF016
IBM Cloud Pak for Business Automation<=V22.0.1 - V22.0.1-IF006 and later fixes V21.0.2 - V21.0.2-IF012 and later fixesV21.0.1 - V21.0.1-IF007 and later fixesV20.0.1 - V20.0.3 and later fixesV19.0.1 - V19.0.3 and later fixesV18.0.0 - V18.0.2 and later fixes
maven/org.postgresql:postgresql>=42.3.0<42.3.8
42.3.8
maven/org.postgresql:postgresql>=42.5.0<42.5.1
42.5.1
maven/org.postgresql:postgresql>=42.4.0<42.4.3
42.4.3
maven/org.postgresql:postgresql>=42.2.0<42.2.27
42.2.27

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Reference Links

Frequently Asked Questions

  • What is CVE-2022-41946?

    CVE-2022-41946 is a vulnerability in pgjdbc, the PostgreSQL JDBC Driver, which allows the creation of a temporary file when using certain methods.

  • How does CVE-2022-41946 affect the software?

    CVE-2022-41946 affects versions of PostgreSQL JDBC Driver before 42.2.14-2.el8 and 42.2.27-1.el9.

  • What is the severity of CVE-2022-41946?

    The severity of CVE-2022-41946 is medium, with a CVSS score of 6.3.

  • How can CVE-2022-41946 be fixed?

    To fix CVE-2022-41946, upgrade to PostgreSQL JDBC Driver version 42.2.14-2.el8 or 42.2.27-1.el9.

  • Where can I find more information about CVE-2022-41946?

    More information about CVE-2022-41946 can be found on CVE.org, NVD, Red Hat Bugzilla, and Red Hat Errata.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203