# DRUPAL-CONTRIB-2020-038: This module enables your users residing at a SAML 2.0 compliant Identity Provider to login to your Drupal website.

> An authentication bypass in the Drupal SAML module allows attackers to log in without valid credentials, potentially taking over accounts.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Nov 2020

## What is DRUPAL-CONTRIB-2020-038?

DRUPAL-CONTRIB-2020-038 is an authentication bypass vulnerability in drupal/miniorange_saml, published on 18 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This module enables your users residing at a SAML 2.0 compliant Identity Provider to login to your Drupal website.

The module has two Authentication Bypass vulnerabilities.

## Which versions are affected by DRUPAL-CONTRIB-2020-038?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/miniorange_saml` | Packagist:https://packages.drupal.org/8 | All versions | 2.14.0 |

## How do I fix DRUPAL-CONTRIB-2020-038?

Upgrade to a fixed version.

## Is DRUPAL-CONTRIB-2020-038 being exploited?

There is no known exploitation of DRUPAL-CONTRIB-2020-038 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for DRUPAL-CONTRIB-2020-038 and fix it if it is affected.

What it is: DRUPAL-CONTRIB-2020-038 is an authentication bypass vulnerability in drupal/miniorange_saml, published on 18 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of DRUPAL-CONTRIB-2020-038 in the wild and no public exploit code.

Affected product: drupal/miniorange_saml. 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/DRUPAL-CONTRIB-2020-038/ (Markdown: https://insights.sbomify.com/DRUPAL-CONTRIB-2020-038/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2020-038

---
From sbomify Insights: https://insights.sbomify.com/DRUPAL-CONTRIB-2020-038/
Summaries are generated and may contain mistakes; the official description above is the record.