# CVE-2021-3196: Auth bypass in n/a

> Attackers can inject unsigned data into SAML responses to impersonate high-privilege users, bypassing authentication controls in Hitachi ID Bravura Security Fabric.

- **Severity:** High 8.8 (`CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:L/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jun 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-9mcv-r5rj-7f62

## What is CVE-2021-3196?

CVE-2021-3196 is a high-severity authentication bypass vulnerability in n/a, published on 9 Jun 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Hitachi ID Bravura Security Fabric 11.0.0 through 11.1.3, 12.0.0 through 12.0.2, and 12.1.0. When using federated identity management (authenticating via SAML through a third-party identity provider), an attacker can inject additional data into a signed SAML response being transmitted to the service provider (ID Bravura Security Fabric). The application successfully validates the signed values but uses the unsigned malicious values. An attacker with lower-privilege access to the application can inject the username of a high-privilege user to impersonate that user.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2021-3196?

It affects 1 product.


Products: Hitachi Id Bravura Security Fabric.

## How do I fix CVE-2021-3196?

No fix has been published for CVE-2021-3196 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-3196 being exploited?

There is no known exploitation of CVE-2021-3196 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-3196 and fix it if it is affected.

What it is: CVE-2021-3196 is a high-severity authentication bypass vulnerability in n/a, published on 9 Jun 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-3196 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-3196/ (Markdown: https://insights.sbomify.com/CVE-2021-3196/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-3196
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-3196
- OSV: https://osv.dev/vulnerability/CVE-2021-3196

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-3196/
Summaries are generated and may contain mistakes; the official description above is the record.