
#devops | #devrelations | KE Developers | https://xitter.gq/t.co/q2qUGEp4Sl
Nairobi, Kenya
Joined April 2012
- Tweets2.4K
- Following716
- Followers590
- Likes2.1K
KE Developers retweeted
You know it’s possible to report a vuln, get it patched and *not* make a giant firework show about it? If you care about defensive outcomes it’s perhaps even a better way of doing it.
KE Developers retweeted
The vulnpocalypse is caused by security vendors.
Their inability to convey risk accurately, due to either incompetence or ignorance, causes tremendous damage and stress on responding teams.
There is a lot of weight associated with vulnerability announcements. We can no longer trust many security vendors’ blog posts, since their purpose is marketing & fanfare, not accuracy.
Exploitability needs to be demonstrated, in realistic environments, and its likelihood accurately conveyed. So that responders can make informed decisions on what to prioritize. But instead we are seeing fake PoC videos set in contrived & controlled lab environments, that give an illusion of exploitability when it’s unrealistic in any real-world scenario.
And vendors now try to show off who found it first, rush to send you marketing emails and call you without your consent; to sell you snake oil they pulled out of their ass two hours earlier, with no intention on actually making anyone safer, only to meet their quarterly sales quotas.
The core responsibility of a security professional is to accurately communicate risk, and let people make informed decisions. Too many vendors are failing at this, that I cannot consider them security vendors, only snake oil salesmen taking advantage of people in vulnerable positions due to their lies.
KE Developers retweeted
Replying to @x0rz
Also is it me or did we just give up on trying to find cool vuln names? It's like "okay you'll be product2problem2000 I guess"
KE Developers retweeted
Pre-auth RCE in nginx is the bug every hacker dreams of finding. It almost never happens.
Today we’re disclosing nginx2root: five nginx vulnerabilities, and an exploit that takes an unauthenticated attacker all the way to root.
One of themhits the default config.
If you run nginx, patch now. Then read: nginx2root.com
CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810, CVE-2026-113425
KE Developers retweeted
This one looks legitimate. It’s x86 specific and is a consequence of a bug in the JIT.
Long story short, the java.util.Base64 decoder has an AVX-512 (SIMD) routine swapped in at runtime to speed up the decoding. Except there’s a bug in the routine which could lead to memory corruption.
The primary concern here is that Base64 is used in a number of application servers for HTTP basic authentication, Kerberos, SAML, WebSockets, etc. You might not even use these features, but if the server decodes the string before rejecting it, it may be too late.
Until a fix is in place the workaround is to add the flag -XX:-UseBASE64Intrinsics to your application startup to disable the AVX-512 routine.
KE Developers retweeted
If you are new to spring boot and you migrate to 4.x and see your whole project turn red, don't panic, you just need some additional Spring boot starter dependencies and change in import statements.
It will be fine.
KE Developers retweeted
😂😂
🤖 Made with AI
...wadau.. homepage tu, inaweza ama haiwezi?
na ujue everything on that bongopoints.com/ homepage is 100% CODE.
I vibe coded every animation, every ripple, every wave, i pictured it in my mind first, then brought it to life with code.
Not long before we have Software companies with their sole premise being #OrganicProgramming
'Code written by hand with love and care'
2
34
KE Developers retweeted
Stripe is not selling software. It’s selling compliance.
You can accept payments without having a legal department or even knowing what FATF is.
Many such cases. If your moat is software, you should be a little bit scared.
KE Developers retweeted
But they’re not paid to sell. They’re paid to build.
Hakuna siku nimeamka nikaona Jira board yangu iko na sales targets.
Is anyone else experiencing abnormally low connectivity to servers in Europe..I think Safaricom has an issue on their undersea cables.
41
KE Developers retweeted
In September 1992, Unicode had a problem on Unix. Storing characters as 16-bit values could introduce zero bytes that C programs mistook for string terminators. Earlier encodings had compatibility problems of their own.
One evening, Ken Thompson and Rob Pike went to a diner in New Jersey. Thompson sketched a new encoding on a paper placemat.
ASCII stayed exactly as it was. Other characters used multiple bytes, without accidentally introducing null bytes or Unix path separators.
They went back to Bell Labs and started coding. By Friday, their Plan 9 operating system was running entirely on the new encoding.
They called it UTF-8.
Today, it powers over 99% of websites with known character encodings.
KE Developers retweeted
Developers, this is for you. please take your payment callbacks seriously. 🔐
Yesterday, out of curiosity, I tested an M-Pesa integration on a critical live system. To my shock, I was able to submit a crafted payload that resulted in a payment being marked as successful.
Never trust a payment callback blindly.
Best practices:
- Verify callbacks against the payment provider.
- Validate the Merchant Request ID and transaction details.
- Verify payment status independently where possible.
- Restrict callback access by IP where supported.
- Make callbacks idempotent to prevent duplicate processing.
- Never mark a payment as successful based on an unverified payload.
One weak payment integration can undermine the integrity of an entire system.
Security is not just about protecting your APIs. It's about protecting the business logic behind them. 🔒

































