Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: backport to 1.15.x jwt auth bound audiences #27471

Merged
merged 1 commit into from
Jun 12, 2024
Merged

docs: backport to 1.15.x jwt auth bound audiences #27471

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions website/content/docs/upgrading/upgrade-to-1.15.x.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,3 +78,5 @@ option.
@include 'known-issues/1_15-audit-vault-enterprise-perf-standby-logs-all-headers.mdx'

@include 'known-issues/perf-standbys-revert-to-standby.mdx'

@include 'known-issues/1_15-jwt_auth_bound_audiences.mdx'
31 changes: 31 additions & 0 deletions website/content/partials/known-issues/1_15-jwt_auth_bound_audiences.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
### JWT auth login requires bound audiences on the role

#### Affected versions

- 1.15.9
- 1.15.10
- 1.16.3
- 1.16.4

#### Issue
A behavior change was made in the jwt auth plugin to address CVE-2024-5798.
Since the behavior change was a breaking change, we reverted the change in
the versions after 1.15.10 and 1.16.4. However, the behavior change will go
into effect in 1.17.

The new behavior requires that the `bound_audiences` parameter of "jwt" roles
**must** match at least one of the JWT's associated `aud` claims. The `aud`
claim can be a single string or a list of strings as per
[RFC 7519 Section 4.1.3](https://datatracker.ietf.org/doc/html/rfc7519#section-4.1.3).

Users may not be able to log into Vault if the JWT role is configured
incorrectly. For additional details, refer to the
[JWT auth method (API)](/vault/api-docs/auth/jwt) documentation.

See this [issue](https://github.com/hashicorp/vault/issues/27343) for more details.

#### Workaround

Configure the `bound_audiences` parameter of "jwt" roles to match at least one
of the JWT's associated `aud` claims. This configuratoin will be required for
1.17 and later.
Loading