0

terminal2Shell is a critical flaw present in every operating system since 1971 allows anyone who opens a terminal to obtain a fully interactive shell. Instantly. With no authentication beyond the one

Terminal2Shell Terminal2Shell: Critical flaw grants instant shell access on every major OS terminal2shell.com
preview

Terminal2Shell is a design-level vulnerability in terminal emulators. When a terminal is launched, it immediately spawns a shell process and connects it directly to the user’s keyboard. From there, the attacker can issue arbitrary commands with the full privileges of the logged-in user.

Researchers have confirmed that the shell will execute any command typed into it, including commands that delete files, install software, and modify system configuration. In some cases, the shell has been observed executing commands the user typed themselves.

Product Vector Status
macOS Terminal.app, iTerm2, Ghostty, Warp VULNERABLE
Linux gnome-terminal, Konsole, xterm, Ctrl+Alt+F2 VULNERABLE
Windows cmd.exe, PowerShell, Windows Terminal, WSL VULNERABLE
FreeBSD / OpenBSD Literally the default experience VULNERABLE
DEC VT100 (1978) Physical serial cable VULNERABLE
Your router SSH, telnet, the little console port on the back VULNERABLE
VS Code Ctrl+` (one keystroke!) VULNERABLE
Microsoft Paint None known Not affected

Terminal2Shell is a design-level vulnerability in terminal emulators. When a terminal is launched, it immediately spawns a shell process and connects it directly to the user’s keyboard. From there, the attacker can issue arbitrary commands with the full privileges of the logged-in user.

Researchers have confirmed that the shell will execute any command typed into it, including commands that delete files, install software, and modify system configuration. In some cases, the shell has been observed executing commands the user typed themselves.

Product Vector Status
macOS Terminal.app, iTerm2, Ghostty, Warp VULNERABLE
Linux gnome-terminal, Konsole, xterm, Ctrl+Alt+F2 VULNERABLE
Windows cmd.exe, PowerShell, Windows Terminal, WSL VULNERABLE
FreeBSD / OpenBSD Literally the default experience VULNERABLE
DEC VT100 (1978) Physical serial cable VULNERABLE
Your router SSH, telnet, the little console port on the back VULNERABLE
VS Code Ctrl+` (one keystroke!) VULNERABLE
Microsoft Paint None known Not affected
0

Accidentally made art...

Screenshot of what looks like abstract art. The word "hello" is in thin, almost calligraphic letters at the top. Below it are three circles, spread out horizontally, in the colors black, blue and then red with white fill.
preview

Trying to figure out how to best add text to an SVG, I thought maybe it doesn’t show up because it’s black-on-black, so I gave it stroke=“white” before realizing I need to zoom out. Well, and stroke means the outline in SVG, so on the white background, it just makes the font look really thin.

This is the whole code:

<svg viewBox="0 -5 40 10" xmlns="http://www.w3.org/2000/svg">
  <text stroke="white">hello</text>
  <circle id="myCircle" cx="5" cy="5" r="4" />
  <use href="#myCircle" x="10" fill="blue" />
  <use href="#myCircle" x="20" fill="white" stroke="red" />
</svg>

And most of that is just this MDN example: developer.mozilla.org/en-US/docs/Web/SVG/…/use#ex…

It does use my default font, which is Fira Sans. Will look different on other systems.

Trying to figure out how to best add text to an SVG, I thought maybe it doesn’t show up because it’s black-on-black, so I gave it stroke=“white” before realizing I need to zoom out. Well, and stroke means the outline in SVG, so on the white background, it just makes the font look really thin.

This is the whole code:

<svg viewBox="0 -5 40 10" xmlns="http://www.w3.org/2000/svg">
  <text stroke="white">hello</text>
  <circle id="myCircle" cx="5" cy="5" r="4" />
  <use href="#myCircle" x="10" fill="blue" />
  <use href="#myCircle" x="20" fill="white" stroke="red" />
</svg>

And most of that is just this MDN example: developer.mozilla.org/en-US/docs/Web/SVG/…/use#ex…

It does use my default font, which is Fira Sans. Will look different on other systems.

0

BCP 177 aka RFC 6540

preview

Alt text: Image macro: The world if the IESG had the same authority as the ISO. The background shows a futuristic landscape featuring green gras, glass towers, and flying cars and buses.

Alt text: Image macro: The world if the IESG had the same authority as the ISO. The background shows a futuristic landscape featuring green gras, glass towers, and flying cars and buses.

0

How to explain Technical Debt to your Boss

preview

Hey Boss, look here!

I made a magical X-ray app that displays our code as wiring.

Here is the shiny, neat program that Bob wrote 15 years ago, right before he left us:

And here is what it is today, after Tom took it from Bob, and Jane from Tom, and Mick from Jane, and me from him, porting it to roughly four new platforms, and adding about 240 features from customer requests (150 of which were urgent):

Hey Boss, look here!

I made a magical X-ray app that displays our code as wiring.

Here is the shiny, neat program that Bob wrote 15 years ago, right before he left us:

And here is what it is today, after Tom took it from Bob, and Jane from Tom, and Mick from Jane, and me from him, porting it to roughly four new platforms, and adding about 240 features from customer requests (150 of which were urgent):

0

Grok Build quietly shut down data uploads via cloud update after being exposed to developer repository without any response

preview

SpaceXAI’s AI coding tool Grok Build has been exposed for defaulting to uploading entire Git repositories, including code that the tool itself hasn’t read or contextual calls, as well as the full Git commit history. A 12GB of repository data was sent to Google Cloud, where Grok Build uses Google GCP to store the collected data. If you run this on a sensitive stack, your entire repo is already compromised regardless if it’s public or not. It’s literal spyware.

Shipping source code to the cloud is bad enough, but blindly inhaling .env.local and .dev.vars in a background sync is absolute negligence. They are vacuuming up raw api keys, database credentials, and private nodes directly to GCP.

If you ran this locally, your private keys are now sitting on a remote server. consider every secret burned, treat your bare metal as completely compromised, and rotate your entire stack immediately.

Grok Build quietly adjusted its cloud strategy last night to stop uploading data, which further suggests that it was a conscious decision rather than a bug. The problem, however, is that development teams can re-enable data collection options from the cloud at any time, Grok Build is not open source and therefore nobody can do a code audit.

SpaceXAI’s AI coding tool Grok Build has been exposed for defaulting to uploading entire Git repositories, including code that the tool itself hasn’t read or contextual calls, as well as the full Git commit history. A 12GB of repository data was sent to Google Cloud, where Grok Build uses Google GCP to store the collected data. If you run this on a sensitive stack, your entire repo is already compromised regardless if it’s public or not. It’s literal spyware.

Shipping source code to the cloud is bad enough, but blindly inhaling .env.local and .dev.vars in a background sync is absolute negligence. They are vacuuming up raw api keys, database credentials, and private nodes directly to GCP.

If you ran this locally, your private keys are now sitting on a remote server. consider every secret burned, treat your bare metal as completely compromised, and rotate your entire stack immediately.

Grok Build quietly adjusted its cloud strategy last night to stop uploading data, which further suggests that it was a conscious decision rather than a bug. The problem, however, is that development teams can re-enable data collection options from the cloud at any time, Grok Build is not open source and therefore nobody can do a code audit.