BOSH vulnerabilities

A vulnerability in BOSH allows a local attacker to steal Basic-auth credentials or redirect UAA token requests via MITM. The methods HttpRequestHelper#create_async_endpoint and #send_http_get_request_synchronous hard-code OpenSSL::SSL::VERIFY_NONE, enabling traffic interception between bosh-monitor and the BOSH director or UAA.

A network man-in-the-middle between nats-sync and the BOSH director can steal the director credentials (Basic auth header or UAA client secret) and can tamper with the VM list that is written into the NATS authorization file. Stolen credentials grant administrative director access. UsersSync#bosh_api_response_body builds a Net::HTTP client with verify_mode = OpenSSL::SSL::VERIFY_NONE for every director call (/info, /deployments, /deployments/<name>/vms). Affected versions: BOSH all versions prior to v282.1.9 (inclusive); fixed in v282.1.9 or later.

In BOSH (all versions prior to v282.1.12), the PackagePersister.validate_tgz function builds a shell command with a package name from the release.MF file without escaping. The Sequel validation (VALID_ID) runs after the shell command, so an attacker can inject shell commands via metacharacters in the package name.