# CVE-2017-10873: OpenAM (Open Source Edition) allows an attacker to bypass authentication and access unauthorized contents via unspecified vectors.


- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4rxj-vw6j-qqrf, UBUNTU-CVE-2017-10873

## What is CVE-2017-10873?

CVE-2017-10873 is a high-severity vulnerability in OpenAM, published on 2 Nov 2017. 

### Official description

OpenAM (Open Source Edition) allows an attacker to bypass authentication and access unauthorized contents via unspecified vectors. Note that this vulnerability affects OpenAM (Open Source Edition) implementations configured as SAML 2.0IdP, and switches authentication methods based on AuthnContext requests sent from the service provider.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2017-10873?

It affects 1 product.


Products: Osstech Openam.

## How do I fix CVE-2017-10873?

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

## Is CVE-2017-10873 being exploited?

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

## Other vulnerabilities in OpenAM

- [CVE-2018-0696](https://insights.sbomify.com/CVE-2018-0696/): Business logic in OpenAM (high 7.5)
- [CVE-2022-31735](https://insights.sbomify.com/CVE-2022-31735/): Open redirect in OpenAM (OpenAM Consortium Edition) (medium 6.1)
- [CVE-2019-5915](https://insights.sbomify.com/CVE-2019-5915/): Open redirect in OpenAM (Open Source Edition) (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-10873 and fix it if it is affected.

What it is: CVE-2017-10873 is a high-severity vulnerability in OpenAM, published on 2 Nov 2017. 
Exploitation: There is no known exploitation of CVE-2017-10873 in the wild and no public exploit code.

Affected product: OpenAM. 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-2017-10873/ (Markdown: https://insights.sbomify.com/CVE-2017-10873/index.md)
```

## Sources

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

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