Welcome To openEuler Community

Hey @tong_1001 , thanks for your contribution to the community.

Bot Usage Manual

I'm the Bot here serving you. You can find the instructions on how to interact with me at Here . That means you can comment below every pull request or issue to trigger Bot Commands. You can self-configure the PR merge rules for this repository. For more details, please refer to Here.

Contact Guide

If you have any questions, please contact the SIG: sig-ruby ,
and any of the maintainers: @shinwell_hu, @small_leek ,
and any of the committers: @hubin1305, @shenyangyang .

issue处理注意事项:
1. 提交正常修复分支的修复PR时,必须关联当前issue,否则无法关闭当前issue;
2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容;
3. 以下为模板中需要填写完整的内容, 请复制到评论区回复;
注: 内容的关键词(影响性分析说明, openEuler评分, 受影响版本排查(受影响/不受影响), 修复是否涉及abi变化(是/否), 原因说明)不能省略,省略后cve-manager将无法正常解析填写内容.

影响性分析说明:

openEuler评分: (评分和向量)

受影响版本排查(受影响/不受影响):
1.master(3.2.8):
2.openEuler-20.03-LTS-SP4(2.5.8):
3.openEuler-22.03-LTS-SP4(3.0.3):
4.openEuler-24.03-LTS-Next(3.2.2):
5.openEuler-24.03-LTS-SP1(3.2.2):
6.openEuler-24.03-LTS-SP3(3.2.2):
7.openEuler-24.03-LTS-SP4(3.2.2):

修复是否涉及abi变化(是/否)：
1.master(3.2.8):
2.openEuler-20.03-LTS-SP4(2.5.8):
3.openEuler-22.03-LTS-SP4(3.0.3):
4.openEuler-24.03-LTS-Next(3.2.2):
5.openEuler-24.03-LTS-SP1(3.2.2):
6.openEuler-24.03-LTS-SP3(3.2.2):
7.openEuler-24.03-LTS-SP4(3.2.2):

原因说明：
1.master(3.2.8):
2.openEuler-20.03-LTS-SP4(2.5.8):
3.openEuler-22.03-LTS-SP4(3.0.3):
4.openEuler-24.03-LTS-Next(3.2.2):
5.openEuler-24.03-LTS-SP1(3.2.2):
6.openEuler-24.03-LTS-SP3(3.2.2):
7.openEuler-24.03-LTS-SP4(3.2.2):

原因说明填写请参考下方表格(注意：版本是否受影响和版本的原因说明必须对应，例如master版本分支受影响，那原因说明只能是受影响对应的原因之一!)：

issue处理具体操作请参考:
https://atomgit.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
pr关联issue具体操作请参考:
https://docs.atomgit.com/docs/help/home/org_project/pullrequests/pr-related-issue

说明：补丁链接仅供初步排查参考，实际可用性请人工再次确认，补丁下载验证可使用CVE补丁工具。
若补丁不准确，烦请在此issue下评论 '/report-patch 参考网址 补丁链接1,补丁链接2' 反馈正确信息，便于我们不断优化工具，不胜感激。
如 /report-patch https://security-tracker.debian.org/tracker/CVE-2021-3997 https://github.com/systemd/systemd/commit/5b1cf7a9be37e20133c0208005274ce4a5b5c6a1

@tong_1001 CVE信息从NVD同步失败, 请稍后重试, 或者数据源不存在.

https://github.com/ruby/rubygems/pull/9493
Fixed by (merge): https://github.com/ruby/rubygems/commit/103ca4230deacb31b9fcd813de109e83b5fc71ac

/branches master /name shixuantong /email sxt1001@qq.com

正在自动化处理任务，任务编号:TASK-gitcode__ruby-138-20260831092431，指定分支:master

✅ 任务结束 (用时: 47分钟)

CVE-2026-82455

是否需要修复：是
是否存在适配：是
上游社区补丁：https://github.com/ruby/rubygems/commit/643e0235fd7ea2bcb464c97eb2336a81d31b81b4.patch
https://github.com/ruby/rubygems/commit/fc2310629ac93fcdd46d0d4f32dd4d3f9d02b4b3.patch

分支修复情况：
1.master(3.2.8): 已修复

PR：

• master: https://gitcode.com/src-openeuler/ruby/merge_requests/345

补丁适配报告 (CVE-2026-82455)

1. backport-CVE-2026-82455-1.patch

• 状态: 适配成功 (status=adapted)
• 置信度: high

适配冲突说明

适配说明

• Both hunks required context adaptation due to version differences between upstream rubygems and Ruby 3.2.8 bundled rubygems. Hunk 1 (package.rb): upstream uses copy_stream(tar.io, out, entry.size) and File.open do/end block while Ruby 3.2.8 uses out.write entry.read and inline block
• context lines adjusted, 1-space indentation offset corrected. Hunk 2 (test_gem_package.rb): anchor methods test_extract_tar_gz_symlink_directory and test_extract_symlink_into_symlink_dir don't exist in Ruby 3.2.8
• context re-anchored on test_extract_tar_gz_symlink_relative_path (ends with File.read(extracted) at line 573) and test_extract_tar_gz_symlink_broken_relative_path. Additionally, symlink_supported? method was inlined from installer_test_case.rb (lines 232-247) since it is not available in TestGemPackage's inheritance chain (TestGemPackage < Gem::Package::TarTestCase < Gem::TestCase
• symlink_supported? only defined in Gem::InstallerTestCase, a sibling subclass). All core + lines preserved byte-for-byte (verified: diff of + lines between original and adapted = empty). Divergence score: 0 (no structural changes - no inheritance/method_signature/variable_access/syntax_sugar/class_relocation changes).

--- 原补丁/lib/rubygems/package.rb
+++ 适配补丁/lib/rubygems/package.rb
@@ -1,4 +1,4 @@
-@@ -453,6 +453,11 @@ def extract_tar_gz(io, destination_dir, pattern = "*") # :nodoc:
+@@ -445,6 +445,11 @@ EOM
            directories << mkdir
          end
  
@@ -8,5 +8,5 @@
 +        end
 +
          if entry.file?
-           File.open(destination, "wb") do |out|
-             copy_stream(tar.io, out, entry.size)
+           File.open(destination, "wb") {|out| out.write entry.read }
+           FileUtils.chmod file_mode(entry.header.mode), destination

--- 原补丁/test/rubygems/test_gem_package.rb
+++ 适配补丁/test/rubygems/test_gem_package.rb
@@ -1,7 +1,23 @@
-@@ -615,6 +615,33 @@ def test_extract_tar_gz_symlink_directory
+@@ -573,6 +573,49 @@ class TestGemPackage < Gem::Package::TarTestCase
                   File.read(extracted)
    end
  
++  @@symlink_supported = nil
++
++  # This is needed for Windows environment without symlink support enabled (the default
++  # for non admin) to be able to skip test for features using symlinks.
++  def symlink_supported?
++    if @@symlink_supported.nil?
++      begin
++        File.symlink("", "")
++      rescue Errno::ENOENT, Errno::EEXIST
++        @@symlink_supported = true
++      rescue NotImplementedError, SystemCallError
++        @@symlink_supported = false
++      end
++    end
++    @@symlink_supported
++  end
 +
 +  def test_extract_tar_gz_rejects_preexisting_symlink_escape
 +    omit "Symlinks not supported or not enabled" unless symlink_supported?
@@ -29,6 +45,6 @@
 +    refute File.exist?(escaped), "must not write outside extraction root via symlink"
 +  end
 +
-   def test_extract_symlink_into_symlink_dir
-     omit "Symlinks not supported or not enabled" unless symlink_supported?
+   def test_extract_tar_gz_symlink_broken_relative_path
      package = Gem::Package.new @gem
+     package.verify

需人工处理的补丁

以下补丁未能自动完成适配，需要人工介入处理，请勿视为已修复。

backport-CVE-2026-82455-2.patch

无需应用：该补丁被判定为不适用于当前 baseline（skipped）。

原因：

• Patch-2 removes a redundant blank line between test_extract_tar_gz_symlink_directory and test_extract_tar_gz_rejects_preexisting_symlink_escape in test/rubygems/test_gem_package.rb. Patch-1 (backport-CVE-2026-82455-1.patch) already applied, inserted the symlink_supported? method and class variable between these two methods, eliminating the double blank line that patch-2 targets. The entire file now uses single-blank-line separators
• no redundant blank line exists to delete. The patch's change is effectively a no-op in the current baseline.

https://cve.imfht.com/intel/747203

修复补丁：
https://github.com/ruby/rubygems/commit/643e0235fd7ea2bcb464c97eb2336a81d31b81b4

修复补丁：
https://github.com/ruby/rubygems/commit/643e0235fd7ea2bcb464c97eb2336a81d31b81b4

@tong_1001

后置补丁：https://github.com/ruby/rubygems/commit/20e729f9a5d52aaa5a01aa4712ebfeb3ed6c2db0
同类问题，建议回合

新增测试用例执行失败，报错主要信息：

NoMethodError: undefined method `symlink_supported?'

ruby-2.5.8适配补丁缺少函数normalize_path函数，需要回合下面补丁：
https://github.com/ruby/rubygems/commit/35984510e0a3c192e66571b5bd1ce80f281ad0e8

/assign

影响性分析说明：RubyGems 在提取 Gem 包时，未能在文件系统符号链接解析后重新验证路径包含性。当目标目录中已存在指向提取根目录之外的符号链接时，原本看似写入目标目录内的文件实际会被写入目录外部，从而破坏了提取操作的安全边界。

openEuler评分：
6.9
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N

受影响版本排查(受影响/不受影响)：
1.master(3.2.8):受影响
2.openEuler-20.03-LTS-SP4(2.5.8):受影响
3.openEuler-22.03-LTS-SP4(3.0.3):受影响
4.openEuler-24.03-LTS-Next(3.2.2):受影响
5.openEuler-24.03-LTS-SP1(3.2.2):受影响
6.openEuler-24.03-LTS-SP3(3.2.2):受影响
7.openEuler-24.03-LTS-SP4(3.2.2):受影响

修复是否涉及abi变化(是/否)：
1.master(3.2.8):否
2.openEuler-20.03-LTS-SP4(2.5.8):否
3.openEuler-22.03-LTS-SP4(3.0.3):否
4.openEuler-24.03-LTS-Next(3.2.2):否
5.openEuler-24.03-LTS-SP1(3.2.2):否
6.openEuler-24.03-LTS-SP3(3.2.2):否
7.openEuler-24.03-LTS-SP4(3.2.2):否

原因说明：
1.master(3.2.8):正常修复
2.openEuler-20.03-LTS-SP4(2.5.8):正常修复
3.openEuler-22.03-LTS-SP4(3.0.3):正常修复
4.openEuler-24.03-LTS-Next(3.2.2):正常修复
5.openEuler-24.03-LTS-SP1(3.2.2):正常修复
6.openEuler-24.03-LTS-SP3(3.2.2):正常修复
7.openEuler-24.03-LTS-SP4(3.2.2):正常修复

@tong_1001 经过 cve-manager 解析, 已分析的内容如下表所示:

请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.

经过cve-manager解析，部分分支PR未合入，如红色字体所示：

原因说明：
1.master:正常修复
2.openEuler-20.03-LTS-SP4:正常修复
3.openEuler-22.03-LTS-SP4:正常修复
4.openEuler-24.03-LTS-Next:正常修复(PR未合入)
5.openEuler-24.03-LTS-SP1:正常修复(PR未合入)
6.openEuler-24.03-LTS-SP3:正常修复(PR未合入)
7.openEuler-24.03-LTS-SP4:正常修复

/close

经过cve-manager解析，所有PR均已合入

经过cve-manager解析，所有PR均已合入