{"answers":{"affected":"2 open source packages ship an affected version, including birdcage.","exploited":"There is no known exploitation of GHSA-wj7f-468m-6mv8 in the wild and no public exploit code.","fix":"Upgrade birdcage to 0.7.0 or later.","what":"GHSA-wj7f-468m-6mv8 is a vulnerability in birdcage, published on 1 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-wj7f-468m-6mv8 and fix it if it is affected.\n\nWhat it is: GHSA-wj7f-468m-6mv8 is a vulnerability in birdcage, published on 1 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-wj7f-468m-6mv8 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- birdcage (crates.io): affected all versions; fixed in 0.7.0\n- birdcage (crates.io): affected all versions; fixed in 0.7.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-wj7f-468m-6mv8/ (Markdown: https://insights.sbomify.com/GHSA-wj7f-468m-6mv8/index.md)","id":"GHSA-wj7f-468m-6mv8","markdown":"https://insights.sbomify.com/GHSA-wj7f-468m-6mv8/index.md","name":"GHSA-wj7f-468m-6mv8","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Rust sandboxing library","requires_auth":"none","summary":"Attackers can read sensitive environment variables from /proc/self/environ within the Birdcage sandbox, bypassing intended isolation.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\n\nEnvironment variables can be read from procfs unless a new process is started.\n\n### PoC\n\n```\nuse birdcage::{Birdcage, Sandbox};\nuse std::{env, fs};\n\nfn main() {\n    Birdcage::new().lock().unwrap();\n\n    assert_eq!(env::var_os(\"SECRET\"), None);\n\n    let environ = fs::read_to_string(\"/proc/self/environ\").unwrap();\n    assert!(!environ.contains(\"SECRET\"), \"ENVIRON CONTAINS SECRET:\\n{environ}\");\n}\n```\n\n```\n$  SECRET=test cargo run\nthread 'main' panicked at src/main.rs:10:5:\nENVIRON CONTAINS SECRET:\n [truncated]\n ```\n\n### Possible Solutions\n\nThe simplest solution would be relying on the ptrace isolation and **always** spawning a new process by changing birdcage's API to create a new command. With an additional PID namespace the guarantees could be even further reinforced.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Environment variables still accessible through /proc","id":"GHSA-wj7f-468m-6mv8","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.7.0"],"introduced":["0"],"last_affected":[],"package":"birdcage","purl":null,"source":"GHSA-wj7f-468m-6mv8"},{"ecosystem":"crates.io","fixed":["0.7.0"],"introduced":["0"],"last_affected":[],"package":"birdcage","purl":"pkg:cargo/birdcage","source":"GHSA-wj7f-468m-6mv8"}],"products":null,"published":"2023-12-01","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can read sensitive environment variables from /proc/self/environ within the Birdcage sandbox, bypassing intended isolation.","url":"https://insights.sbomify.com/GHSA-wj7f-468m-6mv8/"}