Advisory

GHSA-wj7f-468m-6mv8

Also known as: None

Summary

Environment variables still accessible through /proc

Details

Impact

Environment variables can be read from procfs unless a new process is started.

PoC

use birdcage::{Birdcage, Sandbox};
use std::{env, fs};

fn main() {
    Birdcage::new().lock().unwrap();

    assert_eq!(env::var_os("SECRET"), None);

    let environ = fs::read_to_string("/proc/self/environ").unwrap();
    assert!(!environ.contains("SECRET"), "ENVIRON CONTAINS SECRET:\n{environ}");
}
$  SECRET=test cargo run
thread 'main' panicked at src/main.rs:10:5:
ENVIRON CONTAINS SECRET:
 [truncated]

Possible Solutions

The 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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2023-12-01 22:46 UTC
Modified
2023-12-01 22:46 UTC

Affected packages and fixes

birdcage

crates.io · All systems

Affected

  • introduced 0, fixed 0.7.0 (semver)

Fixed versions

0.7.0

Fix

  • Fixed version 0.7.0
    cargo update -p birdcage --precise 0.7.0

Fix 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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences