# GHSA-hw46-3hmr-x9xv: omniauth-saml has dependency on ruby-saml version with Signature Wrapping Attack issue


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 12 Mar 2025

## What is GHSA-hw46-3hmr-x9xv?

GHSA-hw46-3hmr-x9xv is a vulnerability in omniauth-saml, published on 12 Mar 2025. 

### Official description

### Summary
There are 2 new Critical Signature Wrapping Vulnerabilities (CVE-2025-25292, CVE-2025-25291) and a potential DDOS Moderated Vulneratiblity (CVE-2025-25293) affecting ruby-saml, a dependency of omniauth-saml.

The fix will be applied to ruby-saml and released 12 March 2025, under version 1.18.0.

Please [upgrade](https://github.com/omniauth/omniauth-saml/blob/master/omniauth-saml.gemspec#L16) the ruby-saml requirement to v1.18.0.

### Impact
Signature Wrapping Vulnerabilities allows an attacker to impersonate a user.

## Which versions are affected by GHSA-hw46-3hmr-x9xv?

6 open source packages ship an affected version, including omniauth-saml.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `omniauth-saml` | RubyGems | All versions | 1.10.6 |
| `omniauth-saml` | RubyGems | All versions | 1.10.6 |
| `omniauth-saml` | RubyGems | From 2.0.0 | 2.1.3 |
| `omniauth-saml` | RubyGems | From 2.0.0 | 2.1.3 |
| `omniauth-saml` | RubyGems | From 2.2.0 | 2.2.3 |
| `omniauth-saml` | RubyGems | From 2.2.0 | 2.2.3 |

## How do I fix GHSA-hw46-3hmr-x9xv?

Upgrade omniauth-saml to a fixed version for your release line: 1.10.6, 2.1.3 or 2.2.3.

## Is GHSA-hw46-3hmr-x9xv being exploited?

There is no known exploitation of GHSA-hw46-3hmr-x9xv in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-hw46-3hmr-x9xv and fix it if it is affected.

What it is: GHSA-hw46-3hmr-x9xv is a vulnerability in omniauth-saml, published on 12 Mar 2025. 
Exploitation: There is no known exploitation of GHSA-hw46-3hmr-x9xv in the wild and no public exploit code.

Affected packages and fixed versions:
- omniauth-saml (RubyGems): affected all versions; fixed in 1.10.6
- omniauth-saml (RubyGems): affected all versions; fixed in 1.10.6
- omniauth-saml (RubyGems): affected from 2.0.0; fixed in 2.1.3
- omniauth-saml (RubyGems): affected from 2.0.0; fixed in 2.1.3
- omniauth-saml (RubyGems): affected from 2.2.0; fixed in 2.2.3
- omniauth-saml (RubyGems): affected from 2.2.0; fixed in 2.2.3

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/GHSA-hw46-3hmr-x9xv/ (Markdown: https://insights.sbomify.com/GHSA-hw46-3hmr-x9xv/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-hw46-3hmr-x9xv

---
From sbomify Insights: https://insights.sbomify.com/GHSA-hw46-3hmr-x9xv/
Summaries are generated and may contain mistakes; the official description above is the record.