1. 21 7月, 2023 1 次提交
    • I
      Fixed API token authentication bypassed when path contains `/healthz` · 99d6799c
      ItalyPaleAle 提交于
      The APITokenAuthMiddleware allowed bypassing the check if the path included `/healthz`. An attacker only needed to include `/healthz` in the URL, even the querystring, to bypass the API token check, for example `/v1.0/invoke/myapp/method/something?foo=/healthz`.
      
      Additionally, this was not checking the method of the request, so requests to `POST /healthz` would cause a service invocation to happen.
      
      This fixes the issue by making the check a lot more strict. The API token check can be bypassed only if:
      
      - The path is exactly `/v1.0/healthz` or `/v1.0/healthz/outbound` (slashes are trimmed on each side)
      - The method is `GET`
      Signed-off-by: NItalyPaleAle <43508+ItalyPaleAle@users.noreply.github.com>
      99d6799c
  2. 18 7月, 2023 1 次提交
  3. 22 6月, 2023 1 次提交
  4. 21 6月, 2023 4 次提交
  5. 20 6月, 2023 1 次提交
  6. 17 6月, 2023 4 次提交
  7. 12 5月, 2023 1 次提交
  8. 11 5月, 2023 1 次提交
  9. 06 5月, 2023 2 次提交
  10. 04 5月, 2023 1 次提交
  11. 26 4月, 2023 1 次提交
  12. 14 4月, 2023 1 次提交
  13. 11 4月, 2023 1 次提交
  14. 31 3月, 2023 5 次提交
  15. 30 3月, 2023 1 次提交
  16. 21 3月, 2023 1 次提交
  17. 17 3月, 2023 2 次提交
  18. 14 3月, 2023 1 次提交
  19. 11 3月, 2023 1 次提交
  20. 09 3月, 2023 1 次提交
  21. 04 3月, 2023 1 次提交
  22. 03 3月, 2023 1 次提交
  23. 01 3月, 2023 1 次提交
  24. 28 2月, 2023 1 次提交
  25. 24 2月, 2023 1 次提交
  26. 21 2月, 2023 3 次提交