CVE-2026-65066
N/A
Summary
Data::RingBuffer::Shared versions before 0.04 for Perl create a world-readable mmap backing file and open it without O_EXCL or O_NOFOLLOW.
The segment is created in ring.h with open(path, O_RDWR|O_CREAT, 0666). The mode is 0666, so under the default umask 022 the file is created mode 0644 (world-readable). O_NOFOLLOW is absent, so a symlink planted at the path is followed, and O_EXCL is absent, so the open silently uses a pre-planted file instead of failing.
A "Shared" segment naturally lives in a shared directory such as /tmp or /dev/shm, where any local user can read the IPC payloads stored in the world-readable segment, and a pre-planted file or symlink at the path lets a local attacker win a pre-creation race or redirect the open.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| EGOR | Data::RingBuffer::Shared | 0 < 0.04 | affected |
Weaknesses
- CWE-732: CWE-732 Incorrect Permission Assignment for Critical Resource
- CWE-59: CWE-59 Improper Link Resolution Before File Access
Workarounds
For deployments that cannot upgrade to 0.04, set a restrictive umask so the backing file is not world-readable and place it in a directory only the owning user can access.
References
- https://metacpan.org/release/EGOR/Data-RingBuffer-Shared-0.04/diff/EGOR/Data-RingBuffer-Shared-0.03#ring.h
- https://metacpan.org/release/EGOR/Data-RingBuffer-Shared-0.04/changes
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.