How severe is CVE-2017-10784?

CVE-2017-10784 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2017-10784?

CVE-2017-10784 affects the following packages: webrick (RubyGems). Ecosystems affected: RubyGems.

How do I fix CVE-2017-10784?

Update webrick to 1.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-10784 is resolved across your whole dependency graph.

How do I detect CVE-2017-10784 in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for webrick, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2017-10784 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2017-10784 actively exploited in the wild?

No public exploit code has been indexed for CVE-2017-10784 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2017-10784?

CVE-2017-10784 has an EPSS (Exploit Prediction Scoring System) score of 16.4%, placing it in the 97th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2017-10784?

CVE-2017-10784 is classified as Improper Authentication (CWE-287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2017-10784 published, and has it been updated?

CVE-2017-10784 was published on September 19, 2017 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎

💎 RubyGems

Not in CISA KEV

HIGH severity

CVE-2017-10784 — webrick

HIGHFix: ruby/ruby@6617c41

CVE-2017-10784 is a high-severity (CVSS 8.8) Improper Authentication vulnerability in webrick. EPSS puts its 30-day exploitation probability at 16.4% (97th percentile). A fix is available for webrick — see the affected versions and patch details below.

WEBrick RCE Vulnerability

Also known asGHSA-369m-2gv6-mw28

Published

Sep 19, 2017

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

16.4%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

💎webrick

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

The Basic authentication code in WEBrick library in Ruby before 2.2.8, 2.3.x before 2.3.5, and 2.4.x through 2.4.1 allows remote attackers to inject terminal emulator escape sequences into its log and possibly execute arbitrary commands via a crafted user name.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`webrick`	all versions	1.4.0`bundle update webrick --conservative`

Affected Products

1 product · 14 configurations

Application

rubyruby-lang

≤ 2.2.7

7 versions

2.3.02.3.12.3.22.3.32.3.42.4.02.4.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for webrick, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update webrick to 1.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-10784 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This issue affects the versions of ruby as shipped with Red Hat Enterprise Linux 5, 6, and 7, as well as the versions of rh-ruby22-ruby and rh-ruby23-ruby as shipped with Red Hat Software Collections 3. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this…

Product	Fixed in	Advisory
Red Hat Enterprise Linux 7	`ruby-0:2.0.0.648-33.el7_4`	RHSA-2018:0378
Red Hat Software Collections for Red Hat Enterprise Linux 6	`rh-ruby24-ruby-0:2.4.2-86.el6`	RHSA-2017:3485
Red Hat Software Collections for Red Hat Enterprise Linux 6	`rh-ruby22-ruby-0:2.2.9-19.el6`	RHSA-2018:0583
Red Hat Software Collections for Red Hat Enterprise Linux 6	`rh-ruby23-ruby-0:2.3.6-67.el6`	RHSA-2018:0585
Red Hat Hardened Images	`ruby3-3-main-3.3.10-23.1.hum1`	RHSA-2026:7305
Red Hat Hardened Images	`ruby3-4-main-3.4.8-31.1.hum1`	RHSA-2026:7307
Red Hat Hardened Images	`ruby4-0-main-4.0.0-33.3.hum1`	RHSA-2026:8838

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2017-10784 in your dependencies?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works