CVE-2019-17383 json
netaddr before 1.5.3 and 2.0.4 has Incorrect Default Permissions
published 2019-10-09 7 y ago modified 2026-06-17 4 mo ago also GHSA-49pj-69vf-c689 , EUVD-2019-0684
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.4%
- EPSS 2.4% chance of exploitation in 30 days, percentile 83%
- public exploits
- 0
- none known
Summary
The netaddr gem before 2.0.4 for Ruby has misconfigured file permissions, such that a gem install may result in 0777 permissions in the target filesystem.
Patch / fix
- rubygems netaddr 1.5.3, 2.0.4
- netaddr_project netaddr 1.5.3, 2.0.4
- github.com/dspinhirne/netaddr-rb@3aac46c commit
- github.com/dspinhirne/netaddr-rb@c7a7de3 commit
- github.com/dspinhirne/netaddr-rb#20 pull request
Exploit prediction
2.35% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | netaddr | >=2.0.0, <2.0.4 <1.5.3 |
2.0.4 1.5.3 |
Classification
- Weakness
-
- CWE-276 Incorrect Default Permissions
References
-
github.com
/dspinhirne/netaddr-rb/commit/3aac46c00a36e71905eaa619cb94d45bff6e3b51
web, patch, third-party-advisory
-
github.com
/dspinhirne/netaddr-rb/pull/20
web
-
github.com
/dspinhirne/netaddr-rb/commit/c7a7de39b7e1126aef11821f98970db18582948b
web
-
rubygems.org
/gems/netaddr/versions
web, product
-
nvd.nist.gov
/vuln/detail/CVE-2019-17383
advisory
-
github.com
/dspinhirne/netaddr-rb/issues/29
web
-
github.com
/dspinhirne/netaddr-rb
package
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/netaddr/CVE-2019-17383.yml
web
Sources
- CVE List CVE-2019-17383
- GitHub Advisory GHSA-49pj-69vf-c689
- NVD CVE-2019-17383
Fencer Vulns 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.