# CVE-2015-5372: Auth bypass in n/a

> Remote attackers can bypass authentication and inject arbitrary SAML assertions in AdNovum nevisAuth by exploiting improper certificate validation in SAML POST-Binding.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r97q-42f3-866f

## What is CVE-2015-5372?

CVE-2015-5372 is a medium-severity authentication bypass vulnerability in n/a, published on 28 Sep 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The SAML 2.0 implementation in AdNovum nevisAuth 4.13.0.0 before 4.18.3.1, when using SAML POST-Binding, does not match all attributes of the X.509 certificate embedded in the assertion against the certificate from the identity provider (IdP), which allows remote attackers to inject arbitrary SAML assertions via a crafted certificate.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2015-5372?

It affects 1 product.


Products: Adnovum Nevisauth.

## How do I fix CVE-2015-5372?

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

## Is CVE-2015-5372 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-5372 and fix it if it is affected.

What it is: CVE-2015-5372 is a medium-severity authentication bypass vulnerability in n/a, published on 28 Sep 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-5372 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-2015-5372/ (Markdown: https://insights.sbomify.com/CVE-2015-5372/index.md)
```

## Sources

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

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