nono-py
Affected
- introduced
0, fixed0.11.0(ecosystem)
Fixed versions
0.11.0
Fix
- Fixed version
0.11.0pip install --upgrade nono-py==0.11.0
Advisory
Also known as: None
nono-py vulnerable to authorization bypass / policy confusion
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:
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.
Medium Basis: The source's own band: MODERATE
0, fixed 0.11.0 (ecosystem)0.11.0
0.11.0pip install --upgrade nono-py==0.11.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0