[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
▼ Settings Mobile Home
/g/ - Technology

Name
Options
Comment
Verification
4chan Pass users can bypass this verification. [Learn More] [Login]
File
  • Please read the Rules and FAQ before posting.
  • You may highlight syntax and preserve whitespace by using [code] tags.

08/21/20New boards added: /vrpg/, /vmg/, /vst/ and /vm/
05/04/17New trial board added: /bant/ - International/Random
10/04/16New board for 4chan Pass users: /vip/ - Very Important Posts
[Hide] [Show All]


[Advertise on 4chan]


File: media-HVWQHuIaAAAgt4.jpg (135 KB, 680x680)
135 KB JPG
Hahah PHP is shit, good thing use nodebros and pythonchads are safe with our cool modern languages... ACK!
>>
*us
fuck me and my minor typo
>>
>>110147627
does it affect nginx?
>>
Webslop apocalypse
>>
>>110147627
>AI helps quickly discover vulnerabilities
omg this is terrible! If only they could dedicated like 5% of their computer to just fixing and patching things
>>
>>110147627
>>110147670
blame vibecoding incompetence.
>>
>>110147861
>it's... le heckin vibecoding!
lol. programmers have spent decades saying their code barely works and everyone would be horrified to learn that the world runs on broken code from the 80s/90s and excel.
>>
File: tiredsome.jpg (28 KB, 739x415)
28 KB JPG
>another hyped-up vuln that's impractical impossible to exploit outside a very tightly controlled lab environment
>>
>>110147627
I'd never heard of HTTP before today
>>
>>110147627
This is a vulnerability in Brotli, which has been inseparably embedded in every web browser for the past ten years. This means you can instantly get silently rooted on any device you use just by visiting the wrong website. You don't even need to visit a malicious site for it to happen to you. You could visit a typical news website that loads a thousand shady ad networks and telemetry partners, and all it takes is for just ONE of them to send a malicious Brotli payload to your browser, and then you are FUCKED FOR LIFE as it encrypts all your data and infiltrates all your shameful secrets and blackmails you with crypto ransomware. Clients can also send malicious Brotli payloads to servers to instantly gain root access on those servers, and then alter the servers to spread Brotli payloads to any clients that load webpages from those servers, zigzagging the payloads back and forth at an exponential rate until the entire world has been infected. This is actually the end of everything. The only possible way to prevent this is if a benevolent worm exploits this to spread itself for the sole purpose of disabling Brotli in everything
>>
>>110148331
>all it takes is for just ONE of them to send a malicious Brotli payload to your browser, and then you are FUCKED FOR LIFE
then why does the PoC show it having to retry dozens, sometimes hundreds of times before popping a shell
>>
File: 1764487468128599.jpg (59 KB, 478x1024)
59 KB JPG
So AI is bad at writing secure code.
But at the same time it's good at finding vulnerabilities.
>>
File: 1766445556990501.png (6 KB, 720x400)
6 KB PNG
>>110148365
I've been having AI write the code, then recursively asking it to find bugs and exploits while resetting the context between passes. I'd like to think it's doing a good job.
>>
And you know what the funniest and most ironic part is? Vibegods who built the backend in Rust, without even looking at the source code, are more secure than tradcoders who wrote the PHP by hand.

TOTAL VIBEGOD VICTORY (once again).
>>
>>110148448
more like TOTAL RETARD FAIL
the rust backend calls the brotli decoder, which is written in C
>>
>>110148465
don't tell slopcoders that, they may realize that they have no clue how their own systems work
>>
>>110148365
Incorrect—SI is incredible at writing secure code, and incredible at finding vulnerabilities. SI is simply better than any human ever was—or ever could be.
>>
File: 1764864023095195.jpg (23 KB, 640x471)
23 KB JPG
>10.0 CVE for the Pillow dependency for Python
>Go to update it
>Unsigned yt-dlp with a Singapore IP requests firewall permissions
The end times are upon us.
>>
>>110147627
Don't use HTTP
>>
>>110147861
It's a complete VIBEAPOCALYPSE

Shitty code AND vibecoded slop is getting buttfucked by AI agents.
It's like the wild west of agents now since people realized they can just release thousands of agents bruteforcing their ways into any hole.
>>
>>110147627
PHP was proven bullshit. The "vuln" was known 10 years prior and is impossible to exploit. Even the labs swearing by the 2026 CVEs said it's only possible in lab conditions because it requires deliberately breaking the config of the webserver, and guessing the memory map of the server you hit, and guessing the set of all software used. Let me guess, this one is also bullshit.
>>
>>110147915
That's the thing: vibeslop is even worse than that. "It barely works and it's all duck tape and chewing gum" looks like genius god-code compared to the vibeslop.
>>
>>110148331
wtf is brotli
>>
File: 1788510812570440.png (111 KB, 1634x2224)
111 KB PNG
Wake me up when it affects a real language.
>>
>>110148787
A shitty format that was called broli (obviously a dragon ball reference) but the sjw's unironically had a melty because it has "bro" in the name, so he changed it to "brotli" (which still has bro in the name but the sjw's were satisfied by having their way on this).
>>
>>110148289
I saw an article today saying 'Zuckerberg got rich making Facebook with PHP, but the author of PHP never saw one cent of it'.



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.