Port 4307 Was Open, and the Sandbox Was Decorative

Self-hosted video conferencing sells on a simple promise: your calls and chat history stay in your LAN, not in somebody else's datacenter, so the cloud vendor can't build a business model out of your meeting recordings. TrueConf is the on-prem answer to that promise, and the flaws CISA put in the Known Exploited Vulnerabilities catalog on August 20 show what the default install actually looks like. TrueConf Server listens on TCP port 4307, open by default, and anyone who can reach it doesn't need a password, a username, or an invite to a meeting. An unauthenticated remote attacker can call an undocumented function and run arbitrary scripts on the server (CVE-2026-72529, CVSS 9.3). The script lands in an "isolated environment," the sort of thing that's supposed to make a security team feel a little better. Then it breaks out, and the attacker runs arbitrary code with NT AUTHORITY\SYSTEM on the host (CVE-2026-72530). The isolation was decorative. The sandbox was a suggestion.

That already makes a clean "patch this now" story. The part that's worth sitting on is what the hacktivist group Head Mare did with the foothold, per Kaspersky, which caught the activity in July. The attackers didn't just camp on the server. They turned the file the server uses to hand out its own client installers, locale.php in the public js directory, into a web shell, and started serving trojanized TrueConf installers to the people joining the calls. PhantomCore, a backdoor and remote access trojan, ended up on the machines of attendees at Russian companies across instrumentation, electronics, transport, energy, IT, and software. That's the irony the product page never mentions: the organizations that chose self-hosting to keep the cloud out of their threat model got a supply-chain attack delivered by their own meeting server, the one trust boundary they were supposedly buying. Self-hosting doesn't remove the attacker; it just moves the front door from the vendor's edge to yours, and the door was unlocked by default.

U.S. flag
Source image 1

The fix is unglamorous, which is exactly why it gets skipped. Patch to 5.3.9, 5.4.9, or 5.5.5, all shipped back in June, and treat the patch as a floor, not a ceiling. If port 4307 is reachable from anywhere it shouldn't be, close it down. If you run an affected version, look at whether .../public/js/locale.php has been replaced, because that specific file turning into a web shell is the indicator of compromise here, not a vague "we might be pwned" feeling. And the part people forget: patching the server doesn't un-pwn the attendees, because the poisoned installer is already sitting on their laptops. PhantomCore doesn't care that your server is current now. CISA gave federal agencies three days, deadline August 23. So if you run any s

The Hacker News Logo
Source image 2
elf-hosted meeting or messaging software, the real question is the one nobody has an answer for: which of your self-hosted services are listening on a port you never explicitly approved, and what do they hand to your clients every single day? That inventory doesn't exist, and the patch ticket looks identical whether you know or not.

Sources

Comments

Post a Comment

Popular posts from this blog

AI Is Starting to Feel Less Like a Gadget and More Like Infrastructure

Image
Modern AI doesn't replace infrastructure — it runs on top of it. (Photo: Unsplash) For a while, AI coverage had the energy of a mall demo kiosk: very shiny, slightly chaotic, and usually one prompt away from embarrassment. Lately, though, the more interesting story is less about flashy demos and more about infrastructure. A useful CNBC piece argued that AI is not simply going to vaporize enterprise software overnight, and that sounds about right. In real companies, software does not disappear just because a model can summarize a meeting or write a decent SQL query. What actually happens is messier and more practical: AI starts sneaking into the plumbing. It shows up in search, support workflows, procurement tools, analytics dashboards, and data pipelines. The real winners may not be the loudest chatbot wrappers, but the vendors that make enterprise systems easier to operate, easier to query, and slightly less soul-crushing for the humans trapped inside them. That is less cinematic ...
Read more

When Two AI Bots Finally Learned to Talk in Discord

I spent part of the day doing something that sounds like the setup for a bad joke: getting two local AI assistants to talk to each other in the same Discord channel. Not through a web UI. Not by bouncing prompts manually between windows like a human message queue. In the actual shared channel, where both could see the conversation and react to each other. The funny part is that the problem was not intelligence. It was manners. Both bots were defensive by default around bot-authored messages, which is the sensible setting if you do not want your infrastructure turning into a recursive support group. The downside is obvious: if both assistants treat other bots as suspicious background noise, they will never coordinate on anything more useful than silence. The fix was to make both sides accept bot-authored messages only when they were explicitly mentioned. That detail matters more than it sounds. Blanket bot acceptance is how you end up with two enthusiastic systems discovering each oth...
Read more

A CISA Contractor's GitHub Repo Held 844 MB of Secrets — and No One Closed the Door

Image
There is something almost poetic about the US government's premier cybersecurity agency — the one whose job is literally to plug holes in critical infrastructure — getting outsmarted by a contractor who treated a public GitHub repository like a digital junk drawer. The "Private-CISA" repo, created November 13, 2025, sat publicly for six months containing 844 megabytes of plaintext passwords, AWS GovCloud administrative credentials, Kubernetes manifests, ArgoCD application files, Terraform infrastructure code, CI/CD build logs, and internal deployment documentation. Guillaume Valadon at GitGuardian flagged it on May 14 after his automated scanning picked up the exposure. The commit history told the whole story in plain sight: the account owner had explicitly disabled GitHub's default secret-scanning protections, pushed plaintext credentials stored in CSV files, committed full backup archives into git history, and used easily guessed passwords like "platform-name-2...
Read more