CVE-2022-41946 Vulnerability Analysis & Exploit Details

CVE-2022-41946
Vulnerability Scoring

4.7
/10
Medium Risk

The vulnerability CVE-2022-41946 could compromise system integrity but typically requires user interaction to be exploited.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Local
    Vulnerability requires local system access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2022-41946 Details

Status: Modified

Last updated: 🕖 21 Nov 2024, 07:24 UTC
Originally published on: 🕗 23 Nov 2022, 20:15 UTC

Time between publication and last update: 728 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

CVE-2022-41946 Vulnerability Summary

CVE-2022-41946: 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.

Assessing the Risk of CVE-2022-41946

Access Complexity Graph

The exploitability of CVE-2022-41946 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2022-41946

This vulnerability, CVE-2022-41946, requires a high level of attack complexity and low privileges, making it difficult but not impossible to exploit. Organizations should ensure robust security configurations to mitigate risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2022-41946, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2022-41946, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2022-41946 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2022-41946 poses no threat to data integrity.
  • Availability: None
    CVE-2022-41946 does not impact system availability.

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.052% (probability of exploit)

EPSS Percentile: 23.49% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 76.51% of others.

CVE-2022-41946 References

External References

CWE Common Weakness Enumeration

CWE-668

Vulnerable Configurations

  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.4:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.5:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.6:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.6:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.7:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.7:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.8:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.8:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.9:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.9:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.10:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.10:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.11:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.11:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.12:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.12:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.13:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.13:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.13:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.13:rc1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.14:-:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.14:-:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.14:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.14:rc1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.15:-:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.15:-:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.15:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.15:rc1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.15:rc2:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.15:rc2:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.16:-:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.16:-:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.16:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.16:rc1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.16:rc2:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.16:rc2:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.17:-:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.17:-:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.17:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.17:rc1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.18:-:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.18:-:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.18:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.18:rc1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.19:-:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.19:-:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.19:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.19:rc1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.19:rc2:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.19:rc2:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.20:-:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.20:-:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.20:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.20:rc1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.20:rc2:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.20:rc2:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.21:-:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.21:-:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.21:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.21:rc1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.21:rc2:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.21:rc2:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.22:-:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.22:-:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.22:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.22:rc1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.23:-:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.23:-:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.23:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.23:rc1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.23:rc3:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.23:rc3:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.23:rc4:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.23:rc4:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.23:rc5:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.23:rc5:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.23:rc6:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.23:rc6:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.24:-:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.24:-:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.24:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.24:rc1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.24:rc2:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.24:rc2:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.25:-:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.25:-:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.25:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.25:rc1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.26:-:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.26:-:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.26:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.26:rc1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.26:rc2:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.2.26:rc2:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.0:-:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.0:-:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.1:-:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.1:-:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.1:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.1:rc1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.1:rc2:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.1:rc2:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.2:-:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.2:-:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.2:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.2:rc1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.2:rc2:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.2:rc2:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.3:-:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.3:-:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.3:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.3:rc1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.4:-:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.4:-:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.4:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.4:rc1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.5:-:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.5:-:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.5:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.5:rc1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.6:-:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.6:-:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.6:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.6:rc1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.7:-:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.7:-:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.7:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.3.7:rc1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.4.0:-:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.4.0:-:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.4.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.4.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.4.1:-:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.4.1:-:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.4.1:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.4.1:rc1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.4.2:-:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.4.2:-:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.4.2:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.4.2:rc1:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.5.0:-:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.5.0:-:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.5.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql_jdbc_driver:42.5.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*
    cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2022-41946: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-43903 – NSSCryptoSignBackend.cc in Poppler before 25.04.0 does not verify the adbe.pkcs7.sha1 signatures on documents, resulting in potential signature forgeries.
  • CVE-2025-3796 – A vulnerability classified as critical has been found in PHPGurukul Men Salon Management System 1.0. This affects an unknown part of the file /admi...
  • CVE-2025-32953 – z80pack is a mature emulator of multiple platforms with 8080 and Z80 CPU. In version 1.38 and prior, the `makefile-ubuntu.yml` workflow file uses `...
  • CVE-2025-29058 – An issue in Qimou CMS v.3.34.0 allows a remote attacker to execute arbitrary code via the upgrade.php component.
  • CVE-2024-53591 – An issue in the login page of Seclore v3.27.5.0 allows attackers to bypass authentication via a brute force attack.