CVE-2017-6413 The "OpenID Connect Relying Party and OAuth 2.0 Resource Server" (aka mod_auth_openidc) module before 2.1.6 for the Apache HTTP Server does
High 8.6
Published
Updated
Check this codebase for CVE-2017-6413 and fix it if it is affected.
What it is: CVE-2017-6413 is a high-severity vulnerability in n/a, published on 2 Mar 2017.
Exploitation: There is no known exploitation of CVE-2017-6413 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-2017-6413/ (Markdown: https://insights.sbomify.com/CVE-2017-6413/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2017-6413?
CVE-2017-6413 is a high-severity vulnerability in n/a, published on 2 Mar 2017.
Official description
The "OpenID Connect Relying Party and OAuth 2.0 Resource Server" (aka mod_auth_openidc) module before 2.1.6 for the Apache HTTP Server does not skip OIDC_CLAIM_ and OIDCAuthNHeader headers in an "AuthType oauth20" configuration, which allows remote attackers to bypass authentication via crafted HTTP traffic.
Weakness: CWE-287
Which versions are affected by CVE-2017-6413?
It affects 1 product.
Products include Openidc Mod Auth Openidc.
How do I fix CVE-2017-6413?
Upgrade to a fixed version.
Is CVE-2017-6413 being exploited?
There is no known exploitation of CVE-2017-6413 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as DEBIAN-CVE-2017-6413, GHSA-9r74-cmm5-qv85, UBUNTU-CVE-2017-6413.