In Apache httpd 2.2.x before 2.2.33 and 2.4.x before 2.4.26, use of the ap_get_basic_auth_pw() by third-party modules outside of the authentication phase may lead to authentication requirements being bypassed.
CVE-2017-3167
CRITICALNVD 9.89.8ElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: EPSS in the top 5%.EchelonGraph confidence 38%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to NVD's CVSS score.
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-13. NVD baseline CVSS 9.8; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 20%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 9.8
- EG Score
- 9.8CRITICALmedium confidence
- EG Risk
- 60EG Risk 60/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity98% × 45%The EG Score, 9.8 of 10.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 20%
- EPSS %ILE
- 97th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
June 20, 2017
Last Modified
June 17, 2026
Advisory Details (9)
Auto-updated Oct 6, 2026Patch available. Sources: redhat.
Red HatMentions a patch (unverified)
Affected: Red Hat Enterprise Linux 6.7 Extended Update Support.
https://access.redhat.com/errata/RHSA-2017:3195Red HatMentions a patch (unverified)
Affected: Red Hat Enterprise Linux 7.3 Extended Update Support.
https://access.redhat.com/errata/RHSA-2017:3194Red HatMentions a patch (unverified)
Affected: Red Hat Enterprise Linux 7.2 Extended Update Support.
https://access.redhat.com/errata/RHSA-2017:3193Red HatMentions a patch (unverified)
Red HatMentions a patch (unverified)
Affected: Red Hat Enterprise Linux 7.
https://access.redhat.com/errata/RHSA-2017:2479Red HatMentions a patch (unverified)
Affected: Red Hat Enterprise Linux 6.
https://access.redhat.com/errata/RHSA-2017:2478Patch Availability(11)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| ubuntu | apache2.2-bin (2.2.22-1ubuntu1.12) @ precise | 2026-05-20 | ubuntu |
| ubuntu | apache2-bin (2.4.25-3ubuntu2.1) @ zesty | 2026-05-20 | ubuntu |
| redhat | jbcs-httpd24-mod_cluster-native-0:1.3.8-1.Final_redhat_1.jbcs.el6 | 2017-12-15 | redhat |
| redhat | jbcs-httpd24-mod_cluster-native-0:1.3.8-1.Final_redhat_1.jbcs.el7 | 2017-12-15 | redhat |
| redhat | httpd | 2017-12-15 | redhat |
| redhat | httpd-0:2.4.6-45.el7_3.5 | 2017-11-13 | redhat |
| redhat | httpd-0:2.2.15-47.el6_7.5 | 2017-11-13 | redhat |
| redhat | httpd-0:2.4.6-40.el7_2.6 | 2017-11-13 | redhat |
| redhat | httpd24-httpd-0:2.4.25-9.el7.1 | 2017-08-16 | redhat |
| redhat | httpd-0:2.2.15-60.el6_9.5 | 2017-08-15 | redhat |
| redhat | httpd-0:2.4.6-67.el7_4.2 | 2017-08-15 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(29 across 29 ecosystems)
Alpine:v3.10(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.15(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.16(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.17(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.18(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.19(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.20(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.21(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.22(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.23(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.24(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.3(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.4(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.5(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.6(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.7(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.8(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.9(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Debian:7(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | 2.2.22-13 ... 2.2.22-13+deb7u8 (9 versions) |
| — |
Debian:8(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | 2.4.10-10 ... 2.4.10-10+deb8u8 (9 versions) |
| — |
Debian:9(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | 2.4.25-3 |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(11)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
- Red HatRHSA-2017:2478MODERATE2017-06-20
RHSA-2017:2478 — Moderate
- Red HatRHSA-2017:2479MODERATE2017-06-20
RHSA-2017:2479 — Moderate
- Red HatRHSA-2017:2483MODERATE2017-06-20
RHSA-2017:2483 — Moderate
- Red HatRHSA-2017:3193MODERATE2017-06-20
RHSA-2017:3193 — Moderate
- Red HatRHSA-2017:3194MODERATE2017-06-20
RHSA-2017:3194 — Moderate
- Red HatRHSA-2017:3195MODERATE2017-06-20
RHSA-2017:3195 — Moderate
- Red HatRHSA-2017:3475MODERATE2017-06-20
RHSA-2017:3475 — Moderate
- Red HatRHSA-2017:3476MODERATE2017-06-20
RHSA-2017:3476 — Moderate
- Red HatRHSA-2017:3477MODERATE2017-06-20
RHSA-2017:3477 — Moderate
- UbuntuUSN-3340-1MEDIUM
Apache HTTP Server vulnerabilities
- UbuntuUSN-3373-1MEDIUM
Apache HTTP Server vulnerabilities
Data Freshness Timeline
(refreshed 7× in last 7d / 19× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 85 of 153 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 15 repeat rows among the latest 100 are merged into the row they repeat. The 68 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-12 00:52 UTCEG score recompute
- 2026-10-11 13:41 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-10-10 19:55 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-10-09 20:02 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-10-08 16:36 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-10-07 23:41 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-10-06 15:12 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-10-04 11:31 UTCOSV refresh
- 2026-10-03 14:21 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-09-30 14:59 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-09-30 09:33 UTCEG score recompute
- 2026-09-27 13:40 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-09-26 15:53 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-09-24 13:59 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-09-18 19:22 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-09-17 19:22 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-09-15 03:05 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-09-15 01:14 UTCOSV refresh
- 2026-09-12 14:55 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-09-11 09:31 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-09-07 15:56 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-09-06 13:43 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-09-05 15:23 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-09-04 13:56 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-09-02 14:07 UTCEPSS rescoreEPSS 20% · 97th percentile
Show 60 moreShow fewer
- 2026-09-01 03:31 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-08-30 19:13 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-08-27 14:21 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-08-27 01:00 UTCOSV refresh
- 2026-08-26 14:41 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-08-25 13:44 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-08-21 23:44 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-08-20 22:51 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-08-19 16:59 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-08-18 13:43 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-08-16 14:51 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-08-16 02:10 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-08-15 01:26 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-08-12 13:46 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-08-10 14:38 UTCOSV refresh
- 2026-08-07 16:22 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-08-06 13:42 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-08-05 19:12 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-08-04 15:05 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-08-02 02:23 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-07-30 16:24 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-07-30 01:26 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-07-28 15:32 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-07-26 14:51 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-07-25 15:30 UTCOSV refresh
- 2026-07-23 14:15 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-07-23 01:29 UTCEG score recompute
- 2026-07-22 22:08 UTCEG score recompute
- 2026-07-22 14:04 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-07-21 15:21 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-07-20 17:04 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-07-19 02:26 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-07-18 10:00 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-07-16 16:59 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-07-15 16:54 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-07-13 22:26 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-07-12 05:43 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-07-11 08:24 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-07-09 19:06 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-07-08 15:10 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-07-08 09:57 UTCOSV refresh
- 2026-07-07 13:42 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-07-06 16:24 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-07-06 02:20 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-07-05 02:27 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-07-04 06:28 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-07-02 16:54 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-07-01 15:02 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-06-30 23:19 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-06-28 14:04 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-06-28 04:53 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-06-27 03:05 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-06-25 13:47 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-06-24 14:02 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-06-23 21:30 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-06-22 14:23 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-06-21 14:54 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-06-21 01:57 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-06-19 21:52 UTCOSV refresh
- 2026-06-19 19:23 UTCEPSS rescoreEPSS 20% · 97th percentile
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownAlpine:v3.3:apache2 · Alpine:v3.4:apache2
- CVE-2017-7679EG 9.8EPSS p99CRITICAL
- CVE-2017-3169EG 9.8EPSS p97CRITICAL
- CVE-2017-9798NVD 7.5EG 9.0EPSS p100CRITICAL
- CVE-2017-7668NVD 7.5EG 8.2EPSS p99HIGH
- CVE-2018-1312EG 9.8EPSS p97CRITICAL
- CVE-2017-15710EG 7.5EPSS p97HIGH
- CVE-2018-1301EG 5.9EPSS p97MEDIUM
- CVE-2017-15715NVD 8.1EG 9.0EPSS p100CRITICAL
- CVE-2018-1303NVD 7.5EG 8.6EPSS p99HIGH
- CVE-2018-1283EG 5.3EPSS p95MEDIUM
Same vendor
8 shownredhat:RHSA-2017:2478 · redhat:RHSA-2017:3193 · redhat:RHSA-2017:2479
Frequently asked(5)
What is CVE-2017-3167?
CVE-2017-3167 is a critical-severity vulnerability; its CVE record was published on June 20, 2017. In Apache httpd 2.2.x before 2.2.33 and 2.4.x before 2.4.26, use of the apgetbasicauthpw() by third-party modules outside of the authentication phase may lead to authentication requirements being bypassed.
When was CVE-2017-3167 made public?
CVE-2017-3167 was made public on June 19, 2017: that is the date its CVE record's CNA, Apache Software Foundation, gives for when the vulnerability was made public. The CVE record itself was published on June 20, 2017. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2017-3167 actively exploited?
CVE-2017-3167 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20% probability of exploitation in the next 30 days (97th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-3167?
CVE-2017-3167 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-3167?
A fix for CVE-2017-3167 is available: update to the fixed version the vendor names in its advisory.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-3167
Is Your Infrastructure Affected by CVE-2017-3167?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.