CVE-2019-1020001 is a high-severity path traversal vulnerability in yard (rubygems), affecting versions < 0.9.20. It is fixed in 0.9.20.
Possible arbitrary path traversal and file access via yard server Impact A path traversal vulnerability was discovered in YARD <= 0.9.19 when using yard server to serve documentation. This bug would allow unsanitized HTTP requests to access arbitrary files on the machine of a yard server host under certain conditions. Thanks to CuongMX from Viettel Cyber Security for discovering this vulnerability. Patches Please upgrade to YARD v0.9.20 immediately if you are relying on yard server to host documentation in any untrusted environments. Workarounds For users who cannot upgrade, it is possible to perform path sanitization of HTTP requests at your webserver level. WEBrick, for example, can perform such sanitization by default (which you can use via yard server -s webrick), as can certain rules in your webserver configuration.
Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.
CVE-2019-1020001 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (0.9.20). Upgrading removes the vulnerable code path.
rubygems
yard (< 0.9.20)yard → 0.9.20 (rubygems)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2019-1020001 is reachable in your applications. Explore open-source security for your team.
See if CVE-2019-1020001 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2019-1020001 in your environment →Upgrade yard to 0.9.20 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2019-1020001 is a high-severity path traversal vulnerability in yard (rubygems), affecting versions < 0.9.20. It is fixed in 0.9.20. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
CVE-2019-1020001 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
yard (rubygems) versions < 0.9.20 is affected.
Yes. CVE-2019-1020001 is fixed in 0.9.20. Upgrade to this version or later.
Whether CVE-2019-1020001 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade yard to 0.9.20 or later.