Boruta accepts expired JWT client assertions due to missing exp claim validation
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| malach-it | boruta | unaffected |
|
||||||
| malach-it | boruta | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Malach-it | Boruta |
|
||||||||||||||||
| Malach-it | Boruta |
|
||||||||||||||||
| Malach-it | Boruta Auth |
|
Vendor Workaround
Restrict the use of JWT-based client authentication (client_secret_jwt and private_key_jwt) to highly trusted clients, and prefer non-JWT client authentication methods (client_secret_basic or client_secret_post) where possible. Where JWT client authentication must remain enabled, issue short-lived client assertions and protect them from exposure in application logs, fronting proxies, browser tooling, and observability systems to reduce the window for replay.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.511% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Malach-it boruta
|
|
| Vendors & Products |
Malach-it boruta
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Authentication Bypass by Capture-replay vulnerability in malach-it Boruta allows an attacker who has obtained a previously valid JWT client assertion to authenticate as the issuing OAuth client after the assertion has expired. Boruta accepts JWT-based client authentication (client_secret_jwt and private_key_jwt token endpoint authentication methods) but never enforces that the assertion's exp claim is in the future. The pre-check helper Boruta.Oauth.Request.Base.check_expiration/1 in lib/boruta/oauth/request/base.ex only verifies that an exp claim is present (it pattern-matches on the existence of the key and returns success), and the Joken token configuration used for signature verification, Boruta.Oauth.Authorization.Client.Token.token_config/0 in lib/boruta/oauth/authorization/client.ex, returns an empty map, so Joken's default exp claim validator is not engaged either. Any attacker who obtains a validly-signed client assertion (for example through logs, reverse proxies, browser tooling, or other observability surfaces) can replay it indefinitely to authenticate as the client and obtain access tokens with that client's privileges. This issue affects boruta: from 2.3.0 before 2.3.7. | |
| Title | Boruta accepts expired JWT client assertions due to missing exp claim validation | |
| First Time appeared |
Malach-it
Malach-it boruta Auth |
|
| Weaknesses | CWE-294 | |
| CPEs | cpe:2.3:a:malach-it:boruta_auth:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Malach-it
Malach-it boruta Auth |
|
| References |
|
|
| Metrics |
cvssV4_0
|