[#107008] [Ruby master Bug#18465] Make `IO#write` atomic. — "ioquatix (Samuel Williams)" <noreply@...>
Issue #18465 has been reported by ioquatix (Samuel Williams).
16 messages
2022/01/09
[#107150] [Ruby master Feature#18494] [RFC] ENV["RUBY_GC_..."]= changes GC parameters dynamically — "ko1 (Koichi Sasada)" <noreply@...>
Issue #18494 has been updated by ko1 (Koichi Sasada).
4 messages
2022/01/17
[#107170] Re: [Ruby master Feature#18494] [RFC] ENV["RUBY_GC_..."]= changes GC parameters dynamically
— Eric Wong <normalperson@...>
2022/01/17
> https://bugs.ruby-lang.org/issues/18494
[#107302] [Ruby master Bug#18553] Memory leak on compiling method call with kwargs — "ibylich (Ilya Bylich)" <noreply@...>
Issue #18553 has been reported by ibylich (Ilya Bylich).
4 messages
2022/01/27
[#107346] [Ruby master Misc#18557] DevMeeting-2022-02-17 — "mame (Yusuke Endoh)" <noreply@...>
Issue #18557 has been reported by mame (Yusuke Endoh).
18 messages
2022/01/29
[ruby-core:106949] [Ruby master Bug#18431] Ruby 2.6.9, bundler 1.17.2 and CVE-2021-43809
From:
"npic1 (Nat Pic1)" <noreply@...>
Date:
2022-01-03 10:19:22 UTC
List:
ruby-core #106949
Issue #18431 has been updated by npic1 (Nat Pic1). deivid (David Rodr鱈guez) wrote in #note-3: > How is the score for vulnerabilities calculated? I tried to set the score myself to "Low" in the Github Advisory, because the chances that this issue is ever explored seemed very low to me. I also run a CVSS severity calculator by answering some questions and depending on the answers I gave (some of them I was not sure what the best answer was) I would get a Low or Medium score. Where does this 7.3 number come from? > > In principle I totally understand that @hsbt doesn't plan to update it. You can't change the score by yourself; it comes from the CVSS values. For example, NIST and GitHub have used different values for the Attack Complexity field, which produces two different results. https://nvd.nist.gov/vuln/detail/CVE-2021-43809 However, the point here is that ruby 2.6, which is still in the security maintenance phase, includes a vulnerable (and in EOL) package. From my point of view, @hsbt should fix this by removing or upgrading it. Or, if you prefer, you can also declare 2.6 as EOL/EOS. ---------------------------------------- Bug #18431: Ruby 2.6.9, bundler 1.17.2 and CVE-2021-43809 https://bugs.ruby-lang.org/issues/18431#change-95773 * Author: npic1 (Nat Pic1) * Status: Closed * Priority: Normal * Assignee: hsbt (Hiroshi SHIBATA) * Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN ---------------------------------------- Hi, Ruby 2.6.9 ships with bundler 1.17.2, which is affected by CVE-2021-43809. Is there a plan to upgrade it to resolve the issue? I saw that in the past, there was an upgrade and then a downgrade because of some issue: https://git.ruby-lang.org/ruby.git/commit/?id=91533d9ab17a08385381d87991e01e8674e069a1 Thanks a lot, Regards Nat -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>