Client-supplied URI scheme trusted without transport verification in bandit
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 1.11.0 and 45feea20dea8af7ffd7245271107b695c040e667.
Reliance on Untrusted Inputs in a Security Decision vulnerability in mtrudel bandit allows unauthenticated transport-state spoofing on plaintext HTTP connections. Bandit.Pipeline.determine_scheme/2 in lib/bandit/pipeline.ex returns the client-supplied URI scheme verbatim, ignoring the transport's secure? flag. HTTP/1.1 absolute-form request targets (e.g. GET https://victim/path HTTP/1.1) and the HTTP/2 :scheme pseudo-header are both attacker-controlled strings that flow through this function. Over a plaintext TCP connection, a client can declare https and Bandit will set conn.scheme = :https even though no TLS was negotiated. Downstream Plug consumers that branch on conn.scheme are silently misled: Plug.SSL's already-secure branch skips its HTTP→HTTPS redirect, cookies emitted with secure: true are sent over plaintext, audit logs record requests as having arrived over HTTPS, and CSRF/SameSite gating may make incorrect decisions. This issue affects bandit: from 1.0.0-pre.6 before 1.11.0.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| mtrudel | >=1.0.0-pre.6 <1.11.0, >=ff2f829326cd5dcf7335939aef9775269d881e28 <45feea20dea8af7ffd7245271107b695c040e667 | 1.11.0, 45feea20dea8af7ffd7245271107b695c040e667 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket