An issue was discovered in OpenSSH 7.9. Due to the scp implementation being derived from 1983 rcp, the server chooses which files/directories are sent to the client. However, the scp client only performs cursory validation of the object name returned (only directory traversal attacks are prevented). A malicious scp server (or Man-in-The-Middle attacker) can overwrite arbitrary files in the scp client target directory. If recursive operation (-r) is performed, the server can manipulate subdirectories as well (for example, to overwrite the .ssh/authorized_keys file).
CVE-2019-6111
HIGHNVD 5.97.5Trending — 4 sources updated this weekWeaponizedEG-KEV Tier 2: WeaponizedEG-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 2 is not evidence of exploitation. It means a Metasploit module exists, or Exploit-DB marks a public exploit verified, or CISA's SSVC data says "public PoC" and EPSS is 50% or more. EchelonGraph does not test whether exploit code works.Signals for this CVE: CISA's SSVC exploitation value: public PoC, EPSS in the top 5%, EPSS 50% or more, other public exploit code (a GitHub or vendor proof of concept, or an Exploit-DB entry not marked verified).First public exploit code on record: 2019-01-11 (Exploit-DB EDB-46516)EchelonGraph confidence 70%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreHIGH confidence
“▲” beside the score: it is higher than NVD's CVSS score.
Score elevated to 7.5 because EPSS predicted 58% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 5.9 retained for reference. Confidence: see factors.
Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Also known asEUVD-2019-15678 (ENISA EUVD) · GHSA-jr78-hfw4-xp7g (GitHub Security Advisories)Source: ENISA EUVD
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
- 2,548 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 58%
- Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 58%CVSS: 5.9Exploit: Public PoCExposed services: 2,548
A fix is available — apply it.
Internet exposure · derived from Shodan data
2,548 internet-facing services (distinct ip:port) on record running a version that maps to CVE-2019-6111, in our KEV-Exposure radar’s Shodan-derived sample.
across 53 countries (China, United States, Germany, Japan, Singapore)top: openssh
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
- 5.9
- EG Score
- 7.5HIGHhigh confidence
- EG Risk
- 53EG Risk 53/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity59% × 45%Impact severity (EG Severity): CVSS 5.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation65% × 40%EchelonGraph's fixed weight for EG-KEV Tier 2 (Weaponized): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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
- 58%
- EPSS %ILE
- 99th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 5.9 MEDIUM): a likelihood of exploitation, not impact.
- EG Severity
- 5.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 58% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
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 public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). 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
January 31, 2019
Last Modified
October 14, 2026
Advisory Details (8)
Auto-updated Oct 14, 2026🔬 Proof of concept available. Patch available. Sources: redhat.
Web page
OpenSSH: Multiple vulnerabilities (GLSA 201903-16) — Gentoo security
https://security.gentoo.org/glsa/201903-16Web page
SCP Client - Multiple Vulnerabilities (SSHtranger Things) - Multiple remote Exploit
https://www.exploit-db.com/exploits/46193/Web page🟡 PoC Available
Red Hat
1677794 – CVE-2019-6111 affects krb5-appl kerberized rcp
https://bugzilla.redhat.com/show_bug.cgi?id=1677794Web page
[SECURITY] [DSA 4387-1] openssh security update
https://www.debian.org/security/2019/dsa-4387Vendor Advisories for CVE-2019-6111(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(3)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| ubuntu | ssh-krb5 (1:7.2p2-4ubuntu2.8) @ xenial | 2026-10-28 | ubuntu |
| ubuntu | ssh-krb5 (1:7.2p2-4ubuntu2.7) @ xenial | 2026-10-28 | ubuntu |
| redhat | openssh-0:8.0p1-3.el8 | 2019-11-05 | 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
(26 across 25 ecosystems)
Alpine:v3.24(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| dropbear | — |
| — |
| openssh | — |
| — |
Alpine:v3.10(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssh | — |
| — |
Alpine:v3.11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssh | — |
| — |
Alpine:v3.12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssh | — |
| — |
Alpine:v3.13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssh | — |
| — |
Alpine:v3.14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssh | — |
| — |
Alpine:v3.15(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssh | — |
| — |
Alpine:v3.16(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssh | — |
| — |
Alpine:v3.17(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssh | — |
| — |
Alpine:v3.18(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssh | — |
| — |
Alpine:v3.19(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssh | — |
| — |
Alpine:v3.20(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssh | — |
| — |
Alpine:v3.21(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssh | — |
| — |
Alpine:v3.22(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssh | — |
| — |
Alpine:v3.23(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssh | — |
| — |
Alpine:v3.6(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssh | — |
| — |
Alpine:v3.7(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssh | — |
| — |
Alpine:v3.8(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssh | — |
| — |
Alpine:v3.9(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssh | — |
| — |
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssh | — |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssh | — |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssh | — |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssh | — |
| — |
Debian:8(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssh | 1:6.7p1-5 ... 1:6.7p1-5+deb8u7 (8 versions) |
| — |
Debian:9(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssh | 1:7.4p1-10 ... 1:7.4p1-10+deb9u5 (6 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(3)
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.
Data Freshness Timeline
(refreshed 8× in last 7d / 38× 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 94 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. 6 repeat rows among the latest 100 are merged into the row they repeat. The 59 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-31 16:28 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-10-30 16:29 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-10-29 16:28 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-10-28 23:33 UTCEG score recompute
- 2026-10-28 23:33 UTCVendor advisory
- 2026-10-28 23:33 UTCGHSA enrichmentGHSA-jr78-hfw4-xp7g · GitHub CVSS 5.9
- 2026-10-28 16:27 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-10-27 16:27 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-10-25 18:57 UTCEG score recompute
- 2026-10-25 16:27 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-10-24 16:28 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-10-23 16:27 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-10-21 17:33 UTCEG score recompute
- 2026-10-21 17:33 UTCVendor advisory
- 2026-10-21 17:32 UTCGHSA enrichmentGHSA-jr78-hfw4-xp7g · GitHub CVSS 5.9
- 2026-10-21 16:27 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-10-20 16:28 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-10-19 16:27 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-10-18 09:43 UTCEG score recompute
- 2026-10-17 16:28 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-10-16 16:32 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-10-15 16:27 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-10-14 16:28 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-10-14 07:26 UTCVendor advisory
- 2026-10-14 07:26 UTCGHSA enrichmentGHSA-jr78-hfw4-xp7g · GitHub CVSS 5.9
Show 69 moreShow fewer
- 2026-10-14 07:02 UTCEG score recompute
- 2026-10-14 07:02 UTCVendor advisory
- 2026-10-14 07:02 UTCGHSA enrichmentGHSA-jr78-hfw4-xp7g · GitHub CVSS 5.9
- 2026-10-13 16:28 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-10-12 19:53 UTCEG score recompute
- 2026-10-12 16:28 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-10-12 00:17 UTCEG score recompute
- 2026-10-11 13:42 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-10-10 19:56 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-10-09 20:03 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-10-08 16:37 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-10-07 23:43 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-10-06 15:13 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-10-03 14:22 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-09-30 14:59 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-09-30 10:26 UTCEG score recompute
- 2026-09-28 13:46 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-09-28 13:42 UTCOSV refresh
- 2026-09-27 13:40 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-09-26 15:54 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-09-24 13:59 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-09-22 14:43 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-09-21 20:28 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-09-18 19:23 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-09-17 19:22 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-09-16 14:04 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-09-15 03:06 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-09-12 14:56 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-09-11 09:32 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-09-08 21:55 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-09-08 18:04 UTCOSV refresh
- 2026-09-07 15:57 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-09-06 13:44 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-09-05 15:24 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-09-04 13:56 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-09-02 14:08 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-08-27 14:21 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-08-26 14:42 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-08-25 13:45 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-08-22 03:07 UTCOSV refresh
- 2026-08-19 17:00 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-08-18 13:44 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-08-17 13:43 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-08-15 01:26 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-08-13 21:57 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-08-12 13:47 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-08-08 16:33 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-08-07 16:23 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-08-06 06:54 UTCOSV refresh
- 2026-08-01 04:12 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-07-30 01:27 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-07-28 15:32 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-07-26 14:51 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-07-25 14:14 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-24 14:14 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-23 14:15 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-07-23 01:46 UTCEG score recompute▲ 1.60
- 2026-07-22 22:28 UTCEG score recompute
- 2026-07-22 14:05 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-21 15:22 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-20 23:32 UTCOSV refresh
- 2026-07-20 17:04 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-19 14:28 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-19 02:26 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-16 16:59 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-15 16:55 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-15 01:57 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-13 06:10 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-12 05:43 UTCEPSS rescoreEPSS 58% · 98th percentile
Publicly available exploits
(3 references)Public exploit code is referenced for this CVE (2 Exploit-DB entries, 1 GitHub PoC). Defenders should treat patch urgency accordingly.
- GitHub PoC53n7hu/SNPPublished May 12, 2020
CVE-2019-6111 vulnerability exploitation
Open source ↗ - Exploit-DBEDB-46193Published Jan 18, 2019
SCP Client - Multiple Vulnerabilities (SSHtranger Things)
Open source ↗ - Exploit-DBEDB-46516Published Jan 11, 2019
OpenSSH SCP Client - Write Arbitrary Files
Open source ↗
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownDebian:9:openssh · Alpine:v3.10:openssh · Alpine:v3.11:openssh
- CVE-2018-20685EG 5.3EPSS p90MEDIUM
- CVE-2018-15473NVD 5.3EG 9.0EPSS p100CRITICAL
- CVE-2019-6109EG 6.8EPSS p90MEDIUM
- CVE-2016-10012EG 7.8HIGH
- CVE-2016-10009NVD 7.3EG 7.5EPSS p99HIGH
- CVE-2016-10011EG 6.2MEDIUM
- CVE-2017-15906EG 5.3MEDIUM
- CVE-2016-10010EG 7.0EPSS p91HIGH
- CVE-2021-41617EG 7.0HIGH
- CVE-2021-28041EG 7.1HIGH
Same vendor
2 shownredhat:RHSA-2019:3702
Frequently asked(5)
What is CVE-2019-6111?
CVE-2019-6111 is a high-severity vulnerability; its CVE record was published on January 31, 2019. An issue was discovered in OpenSSH 7.9. Due to the scp implementation being derived from 1983 rcp, the server chooses which files/directories are sent to the client. However, the scp client only performs cursory validation of the object name returned (only directory traversal attacks are…
When was CVE-2019-6111 made public?
CVE-2019-6111 was made public on January 31, 2019: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on January 31, 2019. EchelonGraph's copy of the record carries a last-modified date of October 14, 2026; the record at its source may have been updated since.
Is CVE-2019-6111 actively exploited?
CVE-2019-6111 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: CISA's SSVC data says a public PoC exists and its EPSS is 50% or more. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 58% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2019-6111?
CVE-2019-6111 has a CVSS v3 base score of 5.9 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 7.5 (HIGH).
How do I remediate CVE-2019-6111?
A fix for CVE-2019-6111 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2019-6111 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-6111
Is Your Infrastructure Affected by CVE-2019-6111?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.