# Pipe Patch in Chrome 149

#### You:
i didnt test but is pipe patched on 149 chrome

#### ChatGPT:
Can you clarify what you mean by **“pipe”**?

- If you mean a specific exploit, extension, or vulnerability called **Pipe**, I’ll need the exact name or a link.
- If you mean **Picture-in-Picture (PiP)**, that feature is still present in Chrome.
- If you mean a Chrome exploit that people refer to as “pipe,” whether it is patched in Chrome 149 depends on the particular issue.

A bit more context would help me give a definite answer.


#### You:
app bound encryption

#### ChatGPT:
If you're asking whether **App-Bound Encryption (ABE) has been patched around Chrome 149**, the answer is:

- **Chrome 149 still includes App-Bound Encryption protections**; they were introduced in Chrome 127 and expanded to passwords and autofill data by around Chrome 135. ([BleepingComputer](https://www.bleepingcomputer.com/news/security/google-chrome-adds-app-bound-encryption-to-block-infostealer-malware/?utm_source=chatgpt.com), [Reddit](https://www.reddit.com/r/chrome/comments/1k9r7qo?utm_source=chatgpt.com))
- Google has continued hardening ABE and fixed some related weaknesses, such as behavior involving custom user data directories. ([issues.chromium.org](https://issues.chromium.org/issues/394919677?utm_source=chatgpt.com))
- However, researchers have published attacks against ABE, and bypass techniques have been discussed publicly. Whether a particular "Pipe" method still works on 149 depends on the exact technique being referred to. ([Devoteam](https://www.devoteam.com/expert-view/contournement-du-chiffrement-app-bound-sur-google-chrome-sans-droits-administrateurs/?utm_source=chatgpt.com), [TechRadar](https://www.techradar.com/pro/security/google-chrome-cookie-encryption-system-can-be-easily-bypassed-experts-warn?utm_source=chatgpt.com))

So, **I can't say that "Pipe" is definitely patched or unpatched in Chrome 149 without knowing which Pipe bypass you're referring to**. There are multiple publicly discussed approaches.

If you mean the specific exploit or tool commonly called **ChromeKatz/Pipe**, **C4 Bomb**, or another named bypass, tell me which one and I can look into its status on Chrome 149.


#### You:
no what is pipe

#### ChatGPT:
In the context of **Chrome App-Bound Encryption**, **Pipe** usually refers to a technique that abuses **named pipes** (Windows IPC channels) to communicate with or impersonate processes involved in Chrome's encryption service.

A **named pipe** itself is a legitimate Windows feature that allows two processes to exchange data. Security researchers and malware authors have explored ways to use pipes to interact with Chrome or privileged components in order to access encrypted data without directly breaking the encryption.

So:

- **Pipe ≠ a Chrome feature.**
- **Pipe = a class of techniques involving Windows named pipes and inter-process communication.**
- Whether a particular "pipe" attack works depends on the exact implementation and Chrome version.

If you saw "Pipe" mentioned in a GitHub repository, article, or video, sharing the name or source would help identify the specific technique being discussed.
