| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAH8yC8mWWJDVcp=adxApFPBwK=Q_6rM+14RHux0e+KU6nfHnaA@mail.gmail.com> Date: Wed, 17 Jan 2024 15:39:19 -0500 From: Jeffrey Walton <noloader@...il.com> To: Meng Ruijie <ruijie_meng@...us.edu> Cc: "fulldisclosure@...lists.org" <fulldisclosure@...lists.org> Subject: Re: [FD] ODR violation in Redis Raft On Wed, Jan 17, 2024 at 3:29 PM Meng Ruijie <ruijie_meng@...us.edu> wrote: > > [Suggested description] > Redis raft master-1b8bd86 to master-7b46079 was discovered to contain an ODR violation via the component hiredisAllocFns at /opt/fs/redisraft/deps/hiredis/alloc.c. > > [VulnerabilityType Other] > AddressSanitizer: odr-violation > > [Vendor of Product] > Redis > > [Affected Product Code Base] > raft - master-1b8bd86 to master-7b46079 > > [Affected Component] > affected executable > > [Attack Type] > Remote > > [Impact Code execution] > true > > [Impact Denial of Service] > true > > [Attack Vectors] > run redis with redisraft > > [Reference] > https://github.com/RedisLabs/redisraft/issues/600 > > [Has vendor confirmed or acknowledged the vulnerability?] > true > > [Discoverer] > jerrytesting I fail to see how a One Definition Rule (ODR) violation results in a Remote Code Execution. Can you share your PoC, please? Jeff _______________________________________________ Sent through the Full Disclosure mailing list https://nmap.org/mailman/listinfo/fulldisclosure Web Archives & RSS: https://seclists.org/fulldisclosure/
Powered by blists - more mailing lists