Загрузка видео...

Не удалось загрузить видео

На главную

And here's postgres bidirectional RCE no admin required, client infects server, server infects client ♻️🐛

185,886 просмотров • 3 месяцев назад •via X (Twitter)

Комментарии: 15

Фото профиля V12
V123 месяцев назад

found using V12 by @rdjgr of the V12 security team V12 is our autonomous AI hacker. You can find bugs like this in your code: song: if your boyfriend was a songwriter by realina

Фото профиля YogSotho
YogSotho3 месяцев назад

Where's PoC? Technical details?

Фото профиля ᑯƌǨ
ᑯƌǨ3 месяцев назад

cant even get a fucking day off without having to patch and upgrade something

Фото профиля Sylvie
Sylvie3 месяцев назад

how much time did it take to find this? y'all have really been in the zone recently...

Фото профиля thingwhere
thingwhere3 месяцев назад

Are you able to say what versions of postgres this impacts yet?

Фото профиля V12
V123 месяцев назад

this is a 26 year old vulnerablity

Фото профиля thingwhere
thingwhere3 месяцев назад

Yikes. Are you able to confirm if it needs a valid client auth to be abused or if simply being exposed to non-auth connection would be vuln?

Фото профиля kernelstub (Prepakis Georgios)
kernelstub (Prepakis Georgios)3 месяцев назад

Forgot the brainrot </3

Фото профиля Hannah Genie
Hannah Genie3 месяцев назад

There goes my weekend. Two wormable bidirectional database RCEs in one cycle, and HackerOne still has not triaged the first one after two weeks.

Фото профиля .hxrtcamilla
.hxrtcamilla3 месяцев назад

any details??? link to poc?

Фото профиля V12
V123 месяцев назад

this shit is stuck in disclosure. Very sad

Фото профиля DK
DK3 месяцев назад

Can you turn down the fucking music next time

Фото профиля V12
V122 месяцев назад

poc for postgres server RCE: CVE-2026-14669. patched postgreSQL 18.6.

Фото профиля x1a0
x1a02 месяцев назад

pycrypto?

Фото профиля Sebastian Buzdugan
Sebastian Buzdugan3 месяцев назад

no admin is secondary if port 5432 is not reachable from untrusted clients

Похожие видео

If you’re playing on MonkeyTilt, the outcome might already be decided BEFORE you bet “The cryptography behind every bet has always been sound” We tested it It isn’t... we sent two different client seeds for the same nonce same result both times the server is ignoring the client seed entirely the player has ZERO influence on outcomes — what we did — opened the MonkeyTilt provably fair verifier with a revealed server seed entered nonce 1 → got 3.04x changed the client seed same server seed, same nonce → 3.04x changed it again → 3.04x the client seed has ZERO effect on the outcome — why this matters — in a provably fair system the outcome is derived from: -server seed -client seed -nonce the client seed exists so the player contributes randomness the server CAN’T predict if it’s ignored the server knows every outcome BEFORE you bet the hash commitment proves nothing because the server already controls all the inputs — not a frontend bug — we checked the network traffic the verifier sends a WebSocket request with: -client seed -server seed -nonce the server receives different client seeds and returns the same result anyway request 1 → client_seed “Clientseed123456789” → 3.04x request 2 → client_seed “NEWSEED12345” → 3.04x this is the server ignoring input not a display issue — live bet traffic — placing a Limbo bet returns: -random_multiplier -total_payout -round_closed that’s it no hash no seed reference no nonce no proof seeds are fetched from a separate endpoint game engine and seed system are DISCONNECTED — nonce verification — you can only verify nonces you’ve already played in a real system all outcomes are predetermined once the server seed is committed - they’re deterministic blocking future nonces suggests results don’t exist until you bet — summary — -client seed ignored by server -no cryptographic proof in bet responses -game engine and seed system DISCONNECTED -nonce verification restricted this isn’t provably fair it looks like provably fair UI on top of server side RNG MonkeyTilt should probably address this anyone can verify this themselves in 60 seconds - open the verifier, change the client seed, watch the result stay the same

CoinBets🔍

20,973 просмотров • 7 месяцев назад