Vulnerability in passport-saml (CVE-2021-39171)
Summary
Vulnerability in passport-saml (CVE-2021-39171). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.1.0 or later.
Original description
The description as published by the source.
Impact
A malicious SAML payload can require transforms that consume significant system resources to process, thereby resulting in reduced or denied service. This would be an effective way to perform a denial-of-service attack.
Patches
This has been resolved in version 3.1.0. The resolution is to limit the number of allowable transforms to 2.
References
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-39171 has been found in passport-saml.
Risk of unauthorized operations or information disclosure.
What to do: upgrade passport-saml to 3.1.0 or later.
If unsure, ask your IT team or search "passport-saml CVE-2021-39171" on the vendor's site.
CVE-2021-39171 (passport-saml) — CWE-400
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.1.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-400) exists in passport-saml.
Check the vendor advisory for the affected versions of passport-saml.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 3.1.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'passport-saml' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'passport-saml' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
passport-samlを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade passport-saml to 3.1.0ステージング環境で 3.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com