Bug #21181: LoadError in P4Ruby on Windows (MSYS2) After Ruby Security Update

• Status: Feedback
• Assignee: -
• Target version: -
• ruby -v: 3.0.7, 3.1.5, 3.2.4, 3.3.1
• Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN

[hjain (Himanshu Jain)]

After updating to Ruby versions 3.0.7, 3.1.5, 3.2.4, and 3.3.1, P4Ruby fails to load with the following error:

<internal:c:/Ruby/x64/ruby-3.0.7-devkit/lib/ruby/3.0.0/rubygems/core_ext/kernel_require.rb>:85:in `require':  
126: The specified module could not be found. - C:/build/p4ruby/lib/P4.so (LoadError)

This issue started occurring after the release of CVE-2024-27282: Arbitrary memory address read vulnerability with Regex search. The same P4Ruby build worked on earlier Ruby versions but now consistently fails.

Environment:

• OS: Windows 10/11
• Ruby Versions Affected: 3.0.7, 3.1.5, 3.2.4, 3.3.1
• MSYS2 Version: mingw-w64-x86_64 toolchain
• Perforce P4Ruby Version: Latest from source
• Compiler Used: x86_64-w64-mingw32-gcc (from MSYS2)

[hjain (Himanshu Jain)]

After updating to Ruby versions 3.0.7, 3.1.5, 3.2.4, and 3.3.1, P4Ruby fails to load with the following error:
internal:c:/Ruby/x64/ruby-3.0.7-devkit/lib/ruby/3.0.0/rubygems/core_ext/kernel_require.rb:85:in `require':
126: The specified module could not be found. - C:/build/p4ruby/lib/P4.so (LoadError)

This issue started occurring after the release of CVE-2024-27282: Arbitrary memory address read vulnerability with Regex search.

I am able to load the P4Ruby build from previous Ruby versions in these new versions.
However, P4Ruby built with these new Ruby versions fails to load on both old and new Ruby versions.

Environment:

OS: Windows 10/11
Ruby Versions Affected: 3.0.7, 3.1.5, 3.2.4, 3.3.1
MSYS2 Version: mingw-w64-x86_64 toolchain
Perforce P4Ruby Version: Latest from source
Compiler Used: x86_64-w64-mingw32-gcc (from MSYS2)

[alanwu (Alan Wu)]

• Status changed from Open to Feedback

Make sure P4.so exists and try passing an absolute path of it to require.

[nobu (Nobuyoshi Nakada)]

• Description updated (diff)

Seems like a DLL used by that P4.so lacked.
Check the DLLs by ldd C:/build/p4ruby/lib/P4.so.