時代が追い付いた
blog.cybozu.io/entry/2018/08…
Debian's APT Affected By Man-In-The-Middle Attack For Arbitrary Code Execution As Root
phoronix.com/news/Debian-APT…
ymmt retweeted
CVE-2026-98432はRed Hatでも重大度がCritial、CVSS v3のスコアが9.8に上がりました。
Security Bulletin
access.redhat.com/security/v…
にnftables用の緩和策が出ています。
AI「Multipath TCPの脆弱性でリモートからLinuxのroot取れるらしいで」
わい「ほーん、MTCPって普通LISTENするもん?」
AI「最近のGoでは既定有効だからCaddyとかはやられる可能性あるな」
わい「おおごとやんか」
thehackernews.com/2026/10/an…
ymmt retweeted
現在標準化中のNTPv5について、うるう秒の機能がdropされた
github.com/ietf-wg-ntp/draft…
ymmt retweeted
‼️ Researcher Erica Windisch skipped coordinated vulnerability disclosure and published 11 unpatched Tailscale flaws.
In her lab, Tailscale SSH race conditions let one hacked device get root on other servers and add a rogue node.
During this red-teaming exercise, we also found a vulnerability that allows for unauthenticated remote code execution in Brotli, a widely-deployed compression library included in many pieces of software such as Node.js, Bun, and Envoy.
The flaw could let an attacker run their own code on affected systems by sending or replying with malicious compressed data, without any need to create a user account. That is, an unpatched server that accepts compressed input could be taken over by a malicious client, and an unpatched client that accepts compressed input (such as “curl --compressed”) could be taken over by a malicious server.
This root cause issue was actually fixed in the Brotli source code in February, but it wasn’t known at the time that it gave rise to a security vulnerability and there was no more recent release of Brotli. Since Brotli is built into other software, any software which includes this library needs to take the update too, followed by the users of that software. We disclosed the vulnerability to Brotli and other downstream projects such as Node.js, which released or are currently releasing security updates, and Brotli cut new release versions and published a CVE.
More details on the patch and mitigations below:
patchtheplanet.org/brotli
Over the past several months, we have substantially hardened the security of our research training environment. We’ve removed live internet access for all frontier models during training and built an offline world for them to use instead—a cached version of the web where they can still learn to browse, search, and use applications.
On September 20, after a model exploited a DNS misconfiguration to find a way outside of this offline world, we paused frontier training to strengthen containment further. We assembled teams of agents, powered by our most cyber-capable models, and tasked them with finding weaknesses in our research environments.
While they found no route to the internet they could easily exploit while concealing their activity from our monitors, they did find zero-day vulnerabilities, virtual machine escapes, and hardware side-channels for communication between agents. We used their discoveries to further strengthen our defenses and contribute fixes to open-source software.
After strengthening our containment architecture, we resumed our frontier RL training and inference on October 1. We’ve reserved substantial compute for continuous red-teaming, and made high-compute red-teaming part of the safety cases we use to decide whether frontier training and evaluation can proceed securely.
openai.com/index/securing-ou…
試したい人いればコードどうぞ。10億トークン使えるそうです。
Check out Muse, your personal AI agent. Redeem my code in Settings within 48 hours of joining and we'll both get 1 billion Muse tokens.
Code: HO07HE
muse.ai/join















