Dashbit nimble_zta
Improper Verification of Cryptographic Signature in dashbit nimble_zta Cloudflare strategy
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. This issue affects nimble_zta: from 0.1.2 before 0.1.3.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 0.1.2, < 0.1.3
Fixed in 0.1.3
- >= bc004b70985ae5763901baab3a4e204047899768, < 6458fd18a5ba41166d4973214c519e98fe05b72d
Fixed in 6458fd18a5ba41166d4973214c519e98fe05b72d
Mitigation
Upgrade nimble_zta to 0.1.3 or later.
Upgrade nimble_zta to 6458fd18a5ba41166d4973214c519e98fe05b72d or later.
Workaround
Disable the Cloudflare authentication strategy. To keep the user identity strategy available, reject the service token requests yourself. Examine each request before you call NimbleZTA.Cloudflare.authenticate/3, and reject it if its JWT carries the common_name claim and the type claim.
References
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.