GHSA-9j7f-3r4p-pwh6
GHSA-9j7f-3r4p-pwh6 · nono-py vulnerable to authorization bypass / policy confusion
This page contains facts from public vulnerability sources. Check the original advisory before updating.
The python API made a restrictive-looking configuration unsafe by default. A caller could configure only reverse- proxy credential routes, put the child in CapabilitySet.proxy_only, and reasonably expect network access to be limited to those routes. Instead, because empty allowed_hosts meant allow-all inside nono-proxy, the child could use the local proxy as a transparent CONNECT tunnel to non-route nominated hosts (not including metadata endpoints). That is an authorization bypass / policy confusion issue: - Intended policy: route-only proxy access. - Actual policy: route-only plus arbitrary transparent CONNECT. - Boundary crossed: sandboxed child gains broader outbound network reach than the Python policy appears to grant. - Impact depends on environment, but it can allow exfiltration or access to unintended internet/internal services through the unsandboxed proxy. This should be classified as medium severity by default, potentially high if users rely on route-only configs for strict egress control around untrusted code or sensitive credentials. The fix is security-relevant because it changes the default from implicit allow-all to explicit opt-in.
CVSS 5.2 · Medium · Fix available
- Published
- Updated
Stack: python
Affected products and versions
nono-py PyPI
- Versions
- 0.1.0
- 0.10.0
- 0.10.1
- 0.2.0
- 0.3.1
- 0.4.0
- 0.4.2
- 0.5.0
- 0.6.0
- 0.7.0
- 0.7.2
- 0.8.0
- 0.9.0
- 0.9.2
- Affected ranges
- ECOSYSTEM: < 0.11.0
Update to 0.11.0