Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2020-5261

Vulnerability in Sustainsys.Saml2 (CVE-2020-5261)

Summary

Vulnerability in Sustainsys.Saml2 (CVE-2020-5261). Confidential information can be exposed externally. Mitigation: upgrade to 2.5.0 or later.

Original description

The description as published by the source.

Impact

Token Replay Detection is an important defence in depth measure for Single Sign On solutions. In all previous 2.X versions, the Token Replay Detection is not properly implemented.

Note that version 1.0.1 is not affected. It has a correct Token Replay Implementation and is safe to use.

Patches

The 2.5.0 version is patched.

Workarounds

There are no workarounds with existing versions. Fixing the issue requires code updates.

References

https://en.wikipedia.org/wiki/Replay_attack

For more information

If you have any questions or comments about this advisory:

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-2020-5261 has been found in Sustainsys.Saml2.
Confidential information can be exposed externally.
What to do: upgrade Sustainsys.Saml2 to 2.5.0 or later.
If unsure, ask your IT team or search "Sustainsys.Saml2 CVE-2020-5261" on the vendor's site.

CVE-2020-5261 (Sustainsys.Saml2) — CWE-294
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.5.0 — apply immediately
Workaround: There are no workarounds with existing versions.
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.

❓ What is the problem

A vulnerability (CWE-294) exists in Sustainsys.Saml2.

📍 Affected scope

Check the vendor advisory for the affected versions of Sustainsys.Saml2.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 2.5.0.

🛡️ Workaround

Workaround: There are no workarounds with existing versions.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Sustainsys.Saml2' . 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

  1. 1
    Identify exposure identify 
    grep -r 'Sustainsys.Saml2' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Sustainsys.Saml2 を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    There are no workarounds with existing versions.

    パッチが適用されるまでの応急処置として、There are no workarounds with existing versions. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade Sustainsys.Saml2 to 2.5.0

    ステージング環境で 2.5.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

NuGet Sustainsys.Saml2
[{"type":"ECOSYSTEM","events":[{"introduced":"2.0.0"},{"fixed":"2.5.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details