You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(security): stop curl_command from carrying the bearer token across a redirect
curl_command() passed -L, so a redirect was followed with the OAuth bearer
token still on curl's configuration input. curl fixed the cross-host case in
7.58.0 as CVE-2018-1000007, which leaves roughly 7.30 through 7.57 exposed.
Measured against the live API: every endpoint curl_command touches answers in a
single hop on the correct region, including download-installer/v3 and the
registry tags list. So -L never fired on a correct-region run.
-L only did work when FALCON_CLOUD named the wrong region, because the API
answers a wrong region with a 308 to the right one. That never worked on a curl
that strips the header, which is every supported version: on curl 7.29.0 and
8.5.0 the redirect was followed, the header was dropped, the call came back 401
and the run died with a misleading "No sensor found for OS" error. The only
versions where -L produced a working request are the same versions that leak the
token.
Dropped -L, and with it --proto-redir, keeping the convention from #521 that
--proto-redir appears only next to -L. The wrong-region case is now handled the
way the OAuth token request already handles it: the x-cs-region hint is adopted
instead of the redirect being followed, so it works on every curl version rather
than only the leaky band. The warning naming the real region still prints.
falcon-container-sensor-pull.sh already adopted the hint; install, uninstall and
migrate only warned and kept the wrong region.
Fixes#523
0 commit comments