Mon–Fri · 6 AM ET
← All Episodes
EP  • 00:07:38

Java4Shell: RCE in OpenJDK when processing Base64 | Build or Be Replaced

Today: Java4Shell: RCE in OpenJDK when processing Base64 | Google's AI answers reducing search traffic by 40% | Introducing GPT-6.2 Astra and Sol Episode date: 2026-11-18.

Download MP3 →

Transcript

JOSH: It's Wednesday, November 18. This is Build or Be Replaced, powered by ScanBrief.dev. I'm Josh, here with Erik Anderson.
ERIK: Today's theme: the thing you trust by default is the thing that gets you.
JOSH: Stick around. Erik's got an AI pro tip at the end about how to test a new model before it touches your work.
[pause]
JOSH: Episode 151. ScanBrief scored 103 items across 56 sources this morning. Erik, what are we looking at?
ERIK: Three things I'd actually act on. A Java bug, Google eating search traffic, and a new GPT release.
JOSH: Quick headlines first. Microsoft's ONNX Runtime has disappeared from GitHub.
ERIK: That's the whole headline. I haven't read more than that, so I won't pretend. But the action item is the same either way. If your build pulls from a repo you don't own, mirror it in Gitea today. Pin the version. Vendors can vanish. Your build shouldn't go down with them.
JOSH: Next. Nvidia stopped disclosing Singapore sales, as revenues hit 104 billion dollars.
ERIK: Stopped disclosing, right when the number got big. The headline says nothing about why, and I'm not going to invent a reason. What I'll say is this: when a supplier gets quieter as it gets bigger, plan for less visibility. Don't build a roadmap that depends on one vendor's GPUs.
JOSH: And uv, the Python package manager written in Rust, is trending again.
ERIK: Good. It's a drop-in swap for pip. If you still run plain pip on a server, try uv on one throwaway virtualenv this week. Time how long your install takes before and after. Ten minutes, and you'll have your own number.
[pause]
JOSH: Okay, first big one. Java4Shell. That name sounds bad.
ERIK: It earned it. It's CVE-2026-114938, and it's a memory-corruption flaw in OpenJDK's optimized Base64 decoder.
JOSH: Base64. The thing everybody uses to shove bytes into text.
ERIK: Exactly. A specially crafted Base64 input overwrites adjacent memory, and that gets you remote code execution. In default-configured Java applications. Default. Nobody had to do anything wrong.
JOSH: Wait, really? Not some exotic setup?
ERIK: That's what the write-up says. And OpenJDK sits under the vast majority of enterprise and mission-critical software. Fortune 500, national security systems. The write-up calls it high severity across all of them.
[beat]
JOSH: So how do you even start? Everything touches Base64.
ERIK: That's the real problem. Base64 decoding is in auth headers, JWTs, file uploads, API payloads. It's the plumbing. Nobody audits plumbing because nobody thinks it's an attack surface.
JOSH: What does that mean for someone running a bunch of services?
ERIK: I've got 141 services running on the production server right now. Not all Java. But the first question isn't "how do I patch." It's "which of these even run a JVM, and which ones accept outside input." If you can't answer that in ten minutes, that's your actual finding.
JOSH: And your monitoring? Would it catch this?
ERIK: PrimeSentinel is the watchdog on the box. It's good at telling me something stopped. It can't tell me something was exploited and kept running fine. A decoder bug is quiet. That's why you want input validation and network limits in front of the thing, so a bug in the plumbing doesn't become a bug in your business.
JOSH: So the takeaway is boring. Know your exposure.
ERIK: Boring wins. Find your Java, find what takes untrusted input, and put it first in the patch queue. Write the list down. A list in a ticket beats a plan in your head.
[pause]
JOSH: Next. Google's AI answers are reducing search traffic by forty percent.
ERIK: AI Overviews now show up on more than half of U.S. searches. Those summaries sit above the organic results. And click-throughs to outside sites drop roughly forty percent.
JOSH: Forty. That's a business killer if you're a publisher.
ERIK: It is. Do the math on your own site. If a thousand people clicked through last month, that's about four hundred who now read the summary and leave. Same ranking, same work, four hundred fewer visitors.
JOSH: And the fix people keep pitching?
ERIK: Generative engine optimization. GEO. It hasn't shown it can win the traffic back. Nobody has a proven way to recoup it. So anyone selling you a guaranteed fix is selling you a guess.
JOSH: So what do you do if search was your front door?
ERIK: Stop treating it as the front door. Treat it as weather. You don't control it.
JOSH: Does that hit you?
ERIK: Directly. ScanBrief goes out by email every morning. An inbox is a channel nobody can put a summary on top of. Google can answer the question, but it can't answer for the person who already subscribed to you.
JOSH: That's the pitch for owning your list.
ERIK: It's the pitch for owning anything. Same goes for the Prime Automation Solutions side. Our best leads don't come from ranking. They come from a message sent to a specific person. PrimeDistro mails a postcard to a business that has no website. No algorithm sits between that postcard and the owner.
JOSH: Postcards beat AI.
ERIK: Postcards don't get summarized. Dry, I know. But true.
[pause]
JOSH: Last one. OpenAI introduced GPT-6.2 Astra and Sol.
ERIK: The announcement says better professional outputs, coding, computer use, and efficiency at lower cost. Across ChatGPT Work, Codex, and the API.
JOSH: That sounds like a lot of promises.
ERIK: It's a press release. Every model announcement says better and cheaper. The text I have gives me no benchmark numbers, no price per token, no latency figures. So I don't have any, and I won't make them up.
JOSH: So what do you do on launch day?
ERIK: Nothing. That's the discipline. A model name is not a routing decision. PrimeRouter is the gateway for the fleet, and a new model doesn't get a lane because the blog post was nice. It gets tested against my own work first, in the dark, with no live traffic.
JOSH: Even if it says lower cost?
ERIK: Especially then. Lower cost per token means nothing if it takes three tries to get the answer. Cost per correct answer is the only number.
JOSH: And Codex is in the announcement. You use that?
ERIK: GPT models sit in the fleet next to Claude, so yes, I care. But I care about my results, not their launch post.
[beat]
JOSH: There's also a note that Astra for Law ranked first in a launch evaluation across 24 areas of law.
ERIK: Ranked first in the vendor's own launch evaluation. I'd say that sentence slowly. Whoever picks the test usually does well on the test.
JOSH: So whose test counts?
ERIK: Yours. Which is a nice way into the tip.
[pause]
ERIK: This episode is sponsored by Prime Automation Solutions. If you're still doing it manually, we automate it. Also, special on a website — $250. primeautomationsolutions.com
[pause]
JOSH: Alright, what's the AI pro tip today?
ERIK: Keep a personal test set. Ten real prompts from your own work. Not benchmark questions. Things you actually asked a model last month, like a messy config to review, a log to explain, or an email to rewrite. Save each one with the output you accepted, so you know what good looks like. When a new model drops, run all ten and compare against what you saved. Score each as pass or fail, then count how many tries it took to get a pass. That's your cost per correct answer. Then add one rule. Every time a model fails you on real work, that prompt goes into the set. After a few months you've got a test no vendor can game, because the vendor never saw it. That's your tip. Use it.
[beat]
ERIK: If you're building toward financial independence through automation, my first book walks through the whole path. Free chapter at erikandersonbook.com.
[pause]
JOSH: One more thing — we started a Discord for builders. If you're shipping AI, automation, or anything that makes a human obsolete — come hang out. Link at buildorbereplaced.dev.
ERIK: Post what you built. We'll post what we're building. Real wins, real builds, no fluff.
[pause]
ERIK: Build or be replaced.
JOSH: If you want these signals in your inbox every morning, scanbrief.dev. See you tomorrow.