CVE-2022-39299 Vulnerability Analysis & Exploit Details

CVE-2022-39299
Vulnerability Scoring

7.4
/10
Very High Risk

Highly exploitable, CVE-2022-39299 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2022-39299 Details

Status: Modified

Last updated: 🕖 21 Nov 2024, 07:17 UTC
Originally published on: 🕘 12 Oct 2022, 21:15 UTC

Time between publication and last update: 770 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2022-39299 Vulnerability Summary

CVE-2022-39299: Passport-SAML is a SAML 2.0 authentication provider for Passport, the Node.js authentication library. A remote attacker may be able to bypass SAML authentication on a website using passport-saml. A successful attack requires that the attacker is in possession of an arbitrary IDP signed XML element. Depending on the IDP used, fully unauthenticated attacks (e.g without access to a valid user) might also be feasible if generation of a signed message can be triggered. Users should upgrade to passport-saml version 3.2.2 or newer. The issue was also present in the beta releases of `node-saml` before version 4.0.0-beta.5. If you cannot upgrade, disabling SAML authentication may be done as a workaround.

Assessing the Risk of CVE-2022-39299

Access Complexity Graph

The exploitability of CVE-2022-39299 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-39299

CVE-2022-39299 presents a challenge to exploit due to its high attack complexity, but the absence of privilege requirements still makes it a viable target for skilled attackers. A thorough security review is advised.

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-39299, 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-39299, 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-39299 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2022-39299 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: None
    CVE-2022-39299 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: 1.351% (probability of exploit)

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

CVE-2022-39299 References

External References

CWE Common Weakness Enumeration

CWE-347

CAPEC Common Attack Pattern Enumeration and Classification

  • Padding Oracle Crypto Attack CAPEC-463 An adversary is able to efficiently decrypt data without knowing the decryption key if a target system leaks data on whether or not a padding error happened while decrypting the ciphertext. A target system that leaks this type of information becomes the padding oracle and an adversary is able to make use of that oracle to efficiently decrypt data without knowing the decryption key by issuing on average 128*b calls to the padding oracle (where b is the number of bytes in the ciphertext block). In addition to performing decryption, an adversary is also able to produce valid ciphertexts (i.e., perform encryption) by using the padding oracle, all without knowing the encryption key.
  • Signature Spoofing by Improper Validation CAPEC-475 An adversary exploits a cryptographic weakness in the signature verification algorithm implementation to generate a valid signature without knowing the key.

Vulnerable Configurations

  • cpe:2.3:a:passport-saml_project:passport-saml:-:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:-:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.0.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.0.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.0.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.0.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.0.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.0.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.2.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.2.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.4.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.4.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.5.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.5.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.5.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.5.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.5.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.5.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.5.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.5.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.6.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.6.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.6.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.6.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.6.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.6.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.7.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.7.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.8.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.8.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.9.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.9.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.9.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.9.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.9.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.9.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.10.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.10.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.11.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.11.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.11.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.11.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.12.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.12.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.13.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.13.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.14.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.14.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.15.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.15.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.16.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.16.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.16.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.16.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.16.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.16.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.20.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.20.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.20.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.20.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.20.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.20.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.30.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.30.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.31.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.31.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.32.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.32.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.32.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.32.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.33.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.33.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.34.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.34.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:0.35.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:0.35.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:1.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:1.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:1.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:1.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:1.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:1.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:1.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:1.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:1.3.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:1.3.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:1.3.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:1.3.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:1.3.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:1.3.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:1.3.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:1.3.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:1.3.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:1.3.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:1.4.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:1.4.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:1.4.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:1.4.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:1.4.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:1.4.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:1.5.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:1.5.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:2.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:2.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:2.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:2.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:2.0.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:2.0.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:2.0.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:2.0.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:2.0.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:2.0.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:2.0.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:2.0.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:2.0.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:2.0.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:2.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:2.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:2.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:2.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:3.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:3.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:3.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:3.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:3.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:3.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:3.1.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:3.1.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:3.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:3.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:3.2.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:3.2.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:4.0.0:beta1:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:4.0.0:beta1:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:4.0.0:beta2:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:4.0.0:beta2:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:4.0.0:beta3:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:4.0.0:beta3:*:*:*:node.js:*:*
  • cpe:2.3:a:passport-saml_project:passport-saml:4.0.0:beta4:*:*:*:node.js:*:*
    cpe:2.3:a:passport-saml_project:passport-saml:4.0.0:beta4:*:*:*:node.js:*:*

Protect Your Infrastructure against CVE-2022-39299: 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-2024-43107 – Improper Certificate Validation (CWE-295) in the Gallagher Milestone Integration Plugin (MIP) permits unauthenticated messages (e.g. alarm events) ...
  • CVE-2024-41724 – Improper Certificate Validation (CWE-295) in the Gallagher Command Centre SALTO integration allowed an attacker to spoof the SALTO server. Thi...
  • CVE-2025-2133 – A vulnerability classified as problematic was found in ftcms 2.1. Affected by this vulnerability is an unknown functionality of the file /admin/ind...
  • CVE-2025-2132 – A vulnerability classified as critical has been found in ftcms 2.1. Affected is an unknown function of the file /admin/index.php/web/ajax_all_lists...
  • CVE-2025-2131 – A vulnerability was found in dayrui XunRuiCMS up to 4.6.3. It has been rated as problematic. This issue affects some unknown processing of the comp...