Skip to content
Fencer Intel
high 8.6

CVE-2017-6413 json

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…

published 2017-03-02 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-15470

cvss
8.6
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.3%
EPSS 4.3% chance of exploitation in 30 days, percentile 91%
public exploits
0
none known

Summary

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.

Patch / fix

  • libapache2-mod-auth-openidc Debian 14, Debian 13, Debian 12 2.1.6-1

debian advisories DEBIAN-CVE-2017-6413

  • mod_auth_openidc RHEL 7 1.8.8-5.el7

red hat advisories RHSA-2019:2112

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-6413 updated cvss 5.9

mod_auth_openidc: OIDC_CLAIM and OIDCAuthNHeader not skipped in an "AuthType oauth20" configuration

  • Red Hat Enterprise Linux Server (v. 7) mod_auth_openidc 1.8.8-5.el7 Red Hat Enterprise Linux Workstation (v. 7) mod_auth_openidc 1.8.8-5.el7
    fixed: vendor fix RHSA-2019:2112
  • Red Hat Enterprise Linux 8 cjose, mod_auth_openidc
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

4.25% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 8.6 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.