openai/codex
1
0
Fork 0
mirror of https://github.com/openai/codex.git synced 2026-08-23 13:09:46 +00:00
Code Issues Packages Projects Releases Wiki Activity

Document secure devcontainer DNS exfiltration risk (#39283)

Browse Source 
## Why

The secure devcontainer's firewall does not apply its domain allowlist to DNS
traffic, so it does not provide secure DNS resolution for untrusted code.

## What changed

Document the DNS exfiltration risk, limit the devcontainer recommendation to
trusted repositories, and describe filtering DNS through a restricted resolver
as a partial mitigation. Clarify that allowlisted HTTPS destinations remain a
possible exfiltration path.

GitOrigin-RevId: 73cc7d29f8de17013c01411f8c20b8b5e1199b24
This commit is contained in:
viyatb-oai
2026-08-18 21:11:17 +00:00
committed by copyberry
parent 681c82f497
commit 2fe4e06cc2
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.devcontainer/README.md
View File

@@ -22,6 +22,8 @@ Use `devcontainer.secure.json` when you want a stricter runtime profile for runn
This profile keeps the stricter networking isolated to the customer path instead of changing the default Codex contributor container.
The firewall does not apply its domain allowlist to DNS traffic, so code from an untrusted repository can exfiltrate data through DNS. This devcontainer does not provide secure DNS resolution. Use it only with trusted repositories. To mitigate DNS exfiltration, implement your own DNS filtering and restrict outbound DNS traffic to the filtered resolver; this does not make untrusted repositories safe because they can still exfiltrate data through allowed HTTPS destinations.
Start it from the CLI with:
```bash