You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is strongly recommended for all ruby users to upgrade your Ruby installation or take one of the following workarounds as soon as possible.
24
-
After that, you should re-generate RDoc documentation.
22
+
It is strongly recommended for all Ruby users to upgrade your Ruby installation or take one of the following workarounds as soon as possible.
23
+
You also have to re-generate existing RDoc documentations to completely mitigate the vulnerabilities.
25
24
26
25
## Affected Versions
27
26
@@ -31,22 +30,27 @@ After that, you should re-generate RDoc documentation.
31
30
* Ruby 2.6 series: 2.6.3 and earlier
32
31
* prior to master commit f308ab2131ee675000926540cbb8c13c91dc3be5
33
32
33
+
## Required actions
34
+
35
+
RDoc is a static documentation generation tool.
36
+
Patching the tool itself is insufficient to mitigate these vulnerabilities.
37
+
38
+
So, RDoc documentations generated with previous versions have to be re-generated with newer RDoc.
39
+
34
40
## Workarounds
35
41
36
42
In principle, you should upgrade your Ruby installation to the latest version.
37
43
RDoc 6.1.2 or later includes the fix for the vulnerabilities, so upgrade RDoc to the latest version if you can’t upgrade Ruby itself.
38
44
45
+
Note that as mentioned earlier, you have to regenerate existing RDoc documentations.
46
+
39
47
```
40
48
gem install rdoc -f
41
49
```
42
50
43
-
*Update:* The initial version of this post said rdoc-6.1.1.gem which was still vulnerable. Please make sure that you install rdoc-6.1.2 or later.
44
-
45
-
Regarding the development version (master branch), update to HEAD.
51
+
*Update:* The initial version of this post partially mentioned rdoc-6.1.1.gem, which was still vulnerable. Please make sure that you install rdoc-6.1.2 or later.
46
52
47
-
RDoc is a static documentation generation tool.
48
-
Patching the library itself is insufficient to correct this exploit.
49
-
Those hosting rdoc documentation will need to re-generate it with security-fixed RDoc.
53
+
Regarding the development version, update to the latest HEAD of master branch.
50
54
51
55
## Credits
52
56
@@ -56,3 +60,4 @@ Thanks to [Chris Seaton](https://hackerone.com/chrisseaton) for reporting the is
0 commit comments