A bug exists in the way mod_ssl handled client renegotiations. A remote attacker could send a carefully crafted request that would cause mod_ssl to enter a loop leading to a denial of service. This bug can be only triggered with Apache HTTP Server version 2.4.37 when using OpenSSL version 1.1.1 or later, due to an interaction in changes to handling of renegotiation attempts.
CVE-2019-0190
HIGHNVD 7.58.3▲Elevated
EchelonGraph scoreHIGH confidence
Score elevated to 8.3 because EPSS predicts 59% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.
Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
8.3EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
- 113 internet-facing services (distinct ip:port) on record running an affected version — derived from Shodan data (© Shodan); a patched service can stay counted while its port stays open
- High exploitation likelihood — EPSS 59%
CISA-KEV: Not listedEPSS PROB: 59%CVSS: 7.5Exploit: Elevated riskExposed services: 113
A fix is available — apply it.
Internet exposure · derived from Shodan data
113 internet-facing services (distinct ip:port) on record running a version that maps to CVE-2019-0190, in our KEV-Exposure radar’s Shodan-derived sample.
across 31 countries (United States, Japan, Germany, United Kingdom, India)top: http_server
See the KEV-Exposure radar →Derived from Shodan data. Shodan data is owned by Shodan, which holds its copyright (© Shodan). EchelonGraph claims no ownership of it or copyright in it. Aggregate, host-redacted.
How it counts: every 12 hours, when Shodan query credits allow, the radar runs one Shodan query per tracked product, reads up to 100 ip:port services per query, and keeps a service when its banner version matches a CISA-KEV or high-EPSS CVE; a service is dropped when neither a search nor a Shodan InternetDB port re-check has refreshed it for 21 days. A re-check that finds the port still listed by Shodan InternetDB refreshes the service without re-reading the banner, so a patched service can stay counted while its port stays open. A count is a banner-version inference over a sample, not an exploit test and not an internet-wide census, and the unit is a service, not a machine: a machine answering on two ports counts twice.
- CVSS v3
- 7.5
- EG Score
- 8.3HIGHhigh confidence
- EG Risk
- 65EG Risk 65/100CISA SSVC
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 computedSeverity83% × 45%Exploitation59% × 40%Automatability30% × 15%CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 59%
- EPSS %ILE
- 99th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (EG-KEV: elevated) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
January 30, 2019
Last Modified
November 21, 2024
References (40)
- security@apachehttp://www.securityfocus.com/bid/106743
- security@apachehttps://httpd.apache.org/security/vulnerabilities_24.html
- security@apachehttps://lists.apache.org/thread.html/56c2e7cc9deb1c12a843d0dc251ea7fd3e7e80293cde02fcd65286ba%40%3Ccvs.httpd.apache.org%3E
- security@apachehttps://lists.apache.org/thread.html/84a3714f0878781f6ed84473d1a503d2cc382277e100450209231830%40%3Ccvs.httpd.apache.org%3E
- security@apachehttps://lists.apache.org/thread.html/r03ee478b3dda3e381fd6189366fa7af97c980d2f602846eef935277d%40%3Ccvs.httpd.apache.org%3E
- security@apachehttps://lists.apache.org/thread.html/r06f0d87ebb6d59ed8379633f36f72f5b1f79cadfda72ede0830b42cf%40%3Ccvs.httpd.apache.org%3E
- security@apachehttps://lists.apache.org/thread.html/r76142b8c5119df2178be7c2dba88fde552eedeec37ea993dfce68d1d%40%3Ccvs.httpd.apache.org%3E
- security@apachehttps://lists.apache.org/thread.html/r9f93cf6dde308d42a9c807784e8102600d0397f5f834890708bf6920%40%3Ccvs.httpd.apache.org%3E
- security@apachehttps://lists.apache.org/thread.html/rc998b18880df98bafaade071346690c2bc1444adaa1a1ea464b93f0a%40%3Ccvs.httpd.apache.org%3E
- security@apachehttps://lists.apache.org/thread.html/rd18c3c43602e66f9cdcf09f1de233804975b9572b0456cc582390b6f%40%3Ccvs.httpd.apache.org%3E
- security@apachehttps://lists.apache.org/thread.html/rd2fb621142e7fa187cfe12d7137bf66e7234abcbbcd800074c84a538%40%3Ccvs.httpd.apache.org%3E
- security@apachehttps://lists.apache.org/thread.html/rd336919f655b7ff309385e34a143e41c503e133da80414485b3abcc9%40%3Ccvs.httpd.apache.org%3E
- security@apachehttps://lists.apache.org/thread.html/re3d27b6250aa8548b8845d314bb8a350b3df326cacbbfdfe4d455234%40%3Ccvs.httpd.apache.org%3E
- security@apachehttps://lists.apache.org/thread.html/re473305a65b4db888e3556e4dae10c2a04ee89dcff2e26ecdbd860a9%40%3Ccvs.httpd.apache.org%3E
- security@apachehttps://lists.apache.org/thread.html/rf6449464fd8b7437704c55f88361b66f12d5b5f90bcce66af4be4ba9%40%3Ccvs.httpd.apache.org%3E
Affected Packages
(23 across 23 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.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 | — |
| — |
Data Freshness Timeline
(refreshed 5× in last 7d / 18× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
Showing the most recent 100 of 130 total refreshes for this CVE.
- 2026-10-04 23:18 UTCEPSS rescore
- 2026-10-03 14:21 UTCEPSS rescore
- 2026-10-01 19:44 UTCEPSS rescore
- 2026-09-30 14:59 UTCEPSS rescore
- 2026-09-30 10:06 UTCEG score recompute
- 2026-09-28 13:17 UTCOSV refresh
- 2026-09-26 15:53 UTCEPSS rescore
- 2026-09-24 13:59 UTCEPSS rescore
- 2026-09-23 13:42 UTCEPSS rescore
- 2026-09-21 20:27 UTCEPSS rescore
- 2026-09-19 15:36 UTCEPSS rescore
- 2026-09-18 19:22 UTCEPSS rescore
- 2026-09-17 19:22 UTCEPSS rescore
- 2026-09-15 03:05 UTCEPSS rescore
- 2026-09-15 03:05 UTCEPSS rescore
- 2026-09-11 14:48 UTCEPSS rescore
- 2026-09-08 17:04 UTCOSV refresh
- 2026-09-06 13:44 UTCEPSS rescore
- 2026-09-04 13:56 UTCEPSS rescore
- 2026-09-02 14:07 UTCEPSS rescore
- 2026-08-30 19:13 UTCEPSS rescore
- 2026-08-30 01:18 UTCEPSS rescore
- 2026-08-28 21:36 UTCEPSS rescore
- 2026-08-27 14:21 UTCEPSS rescore
- 2026-08-26 14:42 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-25 13:45 UTCEPSS rescore
- 2026-08-24 14:11 UTCEPSS rescore
- 2026-08-22 02:37 UTCOSV refresh
- 2026-08-21 23:45 UTCEPSS rescore
- 2026-08-20 22:51 UTCEPSS rescore
- 2026-08-19 17:00 UTCEPSS rescore
- 2026-08-18 13:44 UTCEPSS rescore
- 2026-08-17 13:43 UTCEPSS rescore
- 2026-08-16 02:10 UTCEPSS rescore
- 2026-08-15 01:26 UTCEPSS rescore
- 2026-08-13 21:56 UTCEPSS rescore
- 2026-08-12 13:47 UTCEPSS rescore
- 2026-08-07 16:23 UTCEPSS rescore
- 2026-08-06 13:42 UTCEPSS rescore
- 2026-08-06 06:54 UTCOSV refresh
- 2026-08-04 15:05 UTCEPSS rescore
- 2026-08-04 10:33 UTCEPSS rescore
- 2026-07-30 16:24 UTCEPSS rescore
- 2026-07-30 01:27 UTCEPSS rescore
- 2026-07-28 15:32 UTCEPSS rescore
- 2026-07-26 14:51 UTCEPSS rescore
- 2026-07-25 14:14 UTCEPSS rescore
- 2026-07-25 14:14 UTCEPSS rescore
- 2026-07-24 14:14 UTCEPSS rescore
- 2026-07-24 14:14 UTCEPSS rescore
- 2026-07-23 14:15 UTCEPSS rescore
- 2026-07-23 14:15 UTCEPSS rescore
- 2026-07-23 01:38 UTCEG score recompute▲ 0.80
- 2026-07-22 22:18 UTCEG score recompute
- 2026-07-22 14:05 UTCEPSS rescore
- 2026-07-21 15:22 UTCEPSS rescore
- 2026-07-20 23:02 UTCOSV refresh
- 2026-07-20 17:04 UTCEPSS rescore
- 2026-07-20 17:04 UTCEPSS rescore
- 2026-07-19 14:28 UTCEPSS rescore
- 2026-07-19 14:28 UTCEPSS rescore
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-16 16:59 UTCEPSS rescore
- 2026-07-16 16:59 UTCEPSS rescore
- 2026-07-15 16:55 UTCEPSS rescore
- 2026-07-15 01:56 UTCEPSS rescore
- 2026-07-13 22:27 UTCEPSS rescore
- 2026-07-13 06:10 UTCEPSS rescore
- 2026-07-09 19:06 UTCEPSS rescore
- 2026-07-07 13:42 UTCEPSS rescore
- 2026-07-07 13:42 UTCEPSS rescore
- 2026-07-05 02:27 UTCEPSS rescore
- 2026-07-03 18:26 UTCOSV refresh
- 2026-07-01 15:03 UTCEPSS rescore
- 2026-07-01 15:03 UTCEPSS rescore
- 2026-06-30 23:20 UTCEPSS rescore
- 2026-06-30 23:20 UTCEPSS rescore
- 2026-06-28 04:53 UTCEPSS rescore
- 2026-06-28 04:53 UTCEPSS rescore
- 2026-06-27 03:06 UTCEPSS rescore
- 2026-06-27 03:06 UTCEPSS rescore
- 2026-06-25 13:47 UTCEPSS rescore
- 2026-06-25 13:47 UTCEPSS rescore
- 2026-06-23 21:30 UTCEPSS rescore
- 2026-06-23 21:30 UTCEPSS rescore
- 2026-06-21 01:57 UTCEPSS rescore
- 2026-06-21 01:57 UTCEPSS rescore
- 2026-06-18 17:50 UTCEPSS rescore
- 2026-06-18 17:50 UTCEPSS rescore
- 2026-06-17 17:50 UTCEPSS rescore
- 2026-06-16 17:50 UTCEPSS rescore
- 2026-06-16 17:50 UTCEPSS rescore
- 2026-06-15 17:45 UTCEPSS rescore
- 2026-06-15 06:43 UTCOSV refresh
- 2026-06-14 23:15 UTCEPSS rescore
- 2026-06-14 23:15 UTCEPSS rescore
- 2026-06-13 22:58 UTCEPSS rescore
- 2026-06-12 23:09 UTCEPSS rescore
- 2026-06-12 23:09 UTCEPSS rescore
Related CVEs(same product)
Same product
10 shownAlpine:v3.6:apache2
- CVE-2018-1312EG 9.8EPSS p97CRITICAL
- CVE-2017-7679EG 9.8EPSS p99CRITICAL
- CVE-2017-3169EG 9.8EPSS p97CRITICAL
- CVE-2017-3167EG 9.8EPSS p97CRITICAL
- CVE-2019-0211NVD 7.8EG 9.0 KEVEPSS p99CRITICAL
- CVE-2017-15715NVD 8.1EG 9.0EPSS p100CRITICAL
- CVE-2017-9798NVD 7.5EG 9.0EPSS p100CRITICAL
- CVE-2018-1303NVD 7.5EG 8.6EPSS p99HIGH
- CVE-2018-8011NVD 7.5EG 8.2EPSS p99HIGH
- CVE-2017-7659NVD 7.5EG 8.2EPSS p99HIGH
Frequently asked(5)
What is CVE-2019-0190?
CVE-2019-0190 is a high vulnerability published on January 30, 2019. A bug exists in the way modssl handled client renegotiations. A remote attacker could send a carefully crafted request that would cause modssl to enter a loop leading to a denial of service. This bug can be only triggered with Apache HTTP Server version 2.4.37 when using OpenSSL version 1.1.1 or…
When was CVE-2019-0190 disclosed?
CVE-2019-0190 was first published on January 30, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-0190 actively exploited?
CVE-2019-0190 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 59% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2019-0190?
CVE-2019-0190 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.3 (HIGH).
How do I remediate CVE-2019-0190?
A fix for CVE-2019-0190 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-2019-0190
Is Your Infrastructure Affected by CVE-2019-0190?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.