Loading video...

Video Failed to Load

Go Home

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

185,886 views • 3 months ago •via X (Twitter)

15 Comments

V12's profile picture
V123 months ago

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's profile picture
YogSotho3 months ago

Where's PoC? Technical details?

ᑯƌǨ's profile picture
ᑯƌǨ3 months ago

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

Sylvie's profile picture
Sylvie3 months ago

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

thingwhere's profile picture
thingwhere3 months ago

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

V12's profile picture
V123 months ago

this is a 26 year old vulnerablity

thingwhere's profile picture
thingwhere3 months ago

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)'s profile picture
kernelstub (Prepakis Georgios)3 months ago

Forgot the brainrot </3

Hannah Genie's profile picture
Hannah Genie3 months ago

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's profile picture
.hxrtcamilla3 months ago

any details??? link to poc?

V12's profile picture
V123 months ago

this shit is stuck in disclosure. Very sad

DK's profile picture
DK3 months ago

Can you turn down the fucking music next time

V12's profile picture
V122 months ago

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

x1a0's profile picture
x1a02 months ago

pycrypto?

Sebastian Buzdugan's profile picture
Sebastian Buzdugan3 months ago

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

Related Videos

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 views • 7 months ago