Improper Verification of Cryptographic Signature in dashbit nimble_zta Cloudflare strategy
dashbit nimble_zta
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| dashbit nimble_zta |
| No fix yet |
| dashbit nimble_zta |
| No fix yet |
Original description
Improper Verification of Cryptographic Signature vulnerability in dashbit nimble_zta allows an unauthenticated remote attacker to authenticate as an arbitrary Cloudflare service token. Applications using the Cloudflare Zero Trust authentication strategy are affected.
verify_token/2 in lib/nimble_zta/cloudflare.ex matches the result of JOSE.JWT.verify/2 against {_, token, _s}, which discards the boolean verification result and returns the decoded token after a failed signature check. The attacker sends a forged JWT in the cf-access-jwt-assertion header, carrying the expected iss claim and the seven service token claims. verify_iss/2 reads the iss claim from the forged token, so it rejects nothing, and the service token path then returns those claims as the authenticated identity.