Project: Vault (Provisioning / Key Management)
File: CHANGELOG-pre-v1.10.md

SECURITY: secrets/pki: Vaults TLS certificate auth method did not initially load the optionally-configured CRL issued by the roles CA into memory on startup, resulting in the revocation list not being checked, if the CRL has not yet been retrieved. This vulnerability, CVE-2022-41316, is fixed in Vault 1.12.0, 1.11.4, 1.10.7, and 1.9.10. ] BUG FIXES: auth/cert: Vault does not initially load the CRLs in cert auth unless the read/write CRL endpoint is hit. ] replication (enterprise): Fix data race in SaveCheckpoint() ui: Fix lease force revoke action ] SECURITY: core: When entity aliases mapped to a single entity share the same alias name, but have different mount accessors, Vault can leak metadata between the aliases. This metadata leak may result in unexpected access if templated policies are using alias metadata for path names. This vulnerability, CVE-2022-40186, is fixed in 1.11.3, 1.10.6, and 1.9.9. ] CHANGES: core: Bump Go version to 1.17.13. BUG FIXES: core (enterprise): Fix some races in merkle index flushing code found in testing core: Increase the allowed concurrent gRPC streams over the cluster port. ] database: Invalidate queue should cancel context first to avoid deadlock ] secrets/database: Fix a bug where the secret engine would queue up a lot of WAL deletes during startup. ] ui: Fix OIDC callback to accept namespace flag in different formats ] ui: Fix issue logging in with JWT auth method ] SECURITY: identity/entity: When entity aliases mapped to a single entity share the same alias name, but have different mount accessors, Vault can leak metadata between the aliases. This metadata leak may result in unexpected access if templated policies are using alias metadata for path names. ] SECURITY: storage/raft: Vault Enterprise (Vault) clusters using Integrated Storage expose an unauthenticated API endpoint that could be abused to override the voter status of a node within a Vault HA cluster, introducing potential for future data loss or catastrophic failure. This vulnerability, CVE-2022-36129, was fixed in Vault 1.9.8, 1.10.5, and 1.11.1. ] CHANGES: core: Bump Go version to 1.17.12. IMPROVEMENTS: secrets/ssh: Allow additional text along with a template definition in defaultExtension value fields. ] BUG FIXES: core/identity: Replicate memberentityids and policies in identity/group across nodes identically ] core/replication (enterprise): Don't flush merkle tree pages to disk after losing active duty core/seal: Fix possible keyring truncation when using the file backend. ] storage/raft (enterprise): Prevent unauthenticated voter status change with rejoin ] transform (enterprise): Fix a bug in the handling of nested or unmatched capture groups in FPE transformations. ui: Fix issue where metadata tab is hidden even though policy grants access ] ui: Updated `leasId` to `leaseId` in the "Copy Credentials" section of "Generate AWS Credentials" ] CHANGES: core: Bump Go version to 1.17.11. ] IMPROVEMENTS: ui: Allow namespace param to be parsed from state queryParam ] BUG FIXES: agent: Redact auto auth token from renew endpoints ] auth/ldap: The logic for setting the entity alias when `usernameasalias` is set has been fixed. The previous behavior would make a request to the LDAP server to get `user_attr` before discarding it and using the username instead. This would make it impossible for a user to connect if this attribute was missing or had multiple values, even though it would not be used anyway. This has been fixed and the username is now used without making superfluous LDAP searches. ] core (enterprise): Fix overcounting of lease count quota usage at startup. core/config: Only ask the system about network interfaces when address configs contain a template having the format: {{

}} ] core: Prevent changing file permissions of audit logs when mode 0000 is used. ] core: Prevent metrics generation from causing deadlocks. ] core: fixed systemd reloading notification ] core: pre-calculate namespace specific paths when tainting a route during postUnseal ] storage/raft (enterprise): Auto-snapshot configuration now forbids slashes in file prefixes for all types, and "/" in path prefix for local storage type. Strip leading prefix in path prefix for AWS. Improve error handling/reporting. transform (enterprise): Fix non-overridable column default value causing tokenization tokens to expire prematurely when using the MySQL storage backend. ui: Fixes client count timezone bug ] ui: Fixes issue logging in with OIDC from a listed auth mounts tab ] BUG FIXES: raft: fix Raft TLS key rotation panic that occurs if active key is more than 24 hours old ] sdk: Fix OpenApi spec generator to properly convert TypeInt64 to OAS supported int64 ] CHANGES: core: A request that fails path validation due to relative path check will now be responded to with a 400 rather than 500. ] core: Bump Go version to 1.17.9. ] IMPROVEMENTS: auth/ldap: Add usernameasalias configurable to change how aliases are named ] core: Systemd unit file included with the Linux packages now sets the service type to notify. ] sentinel (enterprise): Upgrade sentinel to to avoid potential naming collisions in the remote installer website/docs: added a link to an Enigma secret plugin. ] BUG FIXES: api/sys/raft: Update RaftSnapshotRestore to use net/http client allowing bodies larger than allocated memory to be streamed ] api: Respect increment value in grace period calculations in LifetimeWatcher ] auth/approle: Add maximum length for input values that result in SHA56 HMAC calculation ] cassandra: Update gocql Cassandra client to fix "no hosts available in the pool" error ] cli: Fix panic caused by parsing key=value fields whose value is a single backslash ] core (enterprise): Allow local alias create RPCs to persist alias metadata core/metrics: Fix incorrect table size metric for local mounts ] core: Fix panic caused by parsing JSON integers for fields defined as comma-delimited integers ] core: Fix panic caused by parsing JSON integers for fields defined as comma-delimited strings ] core: Fix panic caused by parsing policies with empty slice values. ] core: Fix panic for help request URL paths without /v1/ prefix ] core: fixing excessive unix file permissions ] core: fixing excessive unix file permissions on dir, files and archive created by vault debug command ] core: report unused or redundant keys in server configuration ] core: time.After() used in a select statement can lead to memory leak ] identity/token: Fixes a bug where duplicate public keys could appear in the .well-known JWKS ] metrics/autosnapshots (enterprise) : Fix bug that could cause vault.autosnapshots.save.errors to not be incremented when there is an autosnapshot save error. replication (enterprise): fix panic due to missing entity during invalidation of local aliases. ] ui: Fix Generated Token's Policies helpText to clarify that comma separated values are not excepted in this

] ui: Fix issue where UI incorrectly handled API errors when mounting backends ] ui: Fixes caching issue on kv new version create ] ui: Fixes edit auth method capabilities issue ] ui: Fixes issue logging out with wrapped token query parameter ] ui: Fixes issue with correct auth method not selected when logging out from OIDC or JWT methods ] ui: Redirects to managed namespace if incorrect namespace in URL param ] ui: fix search-select component showing blank selections when editing group member entity ] ui: masked values no longer give away length or location of special characters ] SECURITY: secrets/pki: Vault and Vault Enterprise (Vault) allowed the PKI secrets engine under certain configurations to issue wildcard certificates to authorized users for a specified domain, even if the PKI role policy attribute allow_subdomains is set to false. This vulnerability, CVE-2022-25243, was fixed in Vault 1.8.9 and 1.9.4. transform (enterprise): Vault Enterprise (Vault) clusters using the tokenization transform feature can expose the tokenization key through the tokenization key configuration endpoint to authorized operators with read permissions on this endpoint. This vulnerability, CVE-2022-25244, was fixed in Vault Enterprise 1.7.10, 1.8.9, and 1.9.4. CHANGES: secrets/azure: Changes the configuration parameter `usemicrosoftgraph_api` to use the Microsoft Graph API by default. ] IMPROVEMENTS: core: Bump Go version to 1.17.7. ] secrets/pki: Restrict issuance of wildcard certificates via role parameter (`allowwildcardcertificates`) ] BUG FIXES: Fixed bug where auth method only considers system-identity when multiple identities are available. ] auth/kubernetes: Properly handle the migration of role storage entries containing an empty `aliasnamesource` ] auth/kubernetes: ensure valid entity alias names created for projected volume tokens ] identity/oidc: Adds support for port-agnostic validation of loopback IP redirect URIs. ] identity/oidc: Fixes inherited group membership when evaluating client assignments ] secrets/azure: Fixed bug where Azure environment did not change Graph URL ] secrets/azure: Fixes the operation for upgraded configurations with a `rootpasswordttl` of zero. ] secrets/gcp: Fixed bug where error was not reported for invalid bindings ] secrets/openldap: Fix panic from nil logger in backend ] secrets/pki: Fix issuance of wildcard certificates matching glob patterns ] storage/raft: Fix issues allowing invalid nodes to become leadership candidates. ] ui: Fix default TTL display and set on database role ] ui: Fix incorrect validity message on transit secrets engine ] ui: Fix kv engine access bug ] ui: Fix issue removing raft storage peer via cli not reflected in UI until refresh ] ui: Trigger background token self-renewal if inactive and half of TTL has passed ] IMPROVEMENTS: auth/kubernetes: Added support for dynamically reloading short-lived tokens for better Kubernetes 1.21+ compatibility ] auth/ldap: Add username to alias metadata ] core/identity: Support updating an alias' `custom_metadata` to be empty. ] core: Fixes code scanning alerts ] http (enterprise): Serve /sys/license/status endpoint within namespaces BUG FIXES: auth/oidc: Fixes OIDC auth from the Vault UI when using the implicit flow and `form_post` response mode. ] cli: Fix using kv patch with older server versions that don't support HTTP PATCH. ] core (enterprise): Workaround AWS CloudHSM v5 SDK issue not allowing read-only sessions core/identity: Address a data race condition between local updates to aliases and invalidations ] core: add support for go-sockaddr templates in the top-level cluster_addr field ] identity/oidc: Check for a nil signing key on rotation to prevent panics. ] kmip (enterprise): Fix locate by name operations fail to find key after a rekey operation. secrets/database/mssql: Accept a boolean for `contained_db`, rather than just a string. ] secrets/gcp: Fixes role bindings for BigQuery dataset resources. ] secrets/pki: Fix regression causing performance secondaries to forward certificate generation to the primary. ] storage/raft: On linux, use map_populate for bolt files to improve startup time. ] storage/raft: Units for bolt metrics now given in milliseconds instead of nanoseconds ] ui: Fixes breadcrumb bug for secrets navigation ] ui: Fixes issue saving KMIP role correctly ] CHANGES: go: Update go version to 1.17.5 ] IMPROVEMENTS: auth/jwt: The Authorization Code flow makes use of the Proof Key for Code Exchange (PKCE)

] BUG FIXES: ui: Fix client count current month data not showing unless monthly history data exists ] SECURITY: storage/raft: Integrated Storage backend could be caused to crash by an authenticated user with write permissions to the KV secrets engine. This vulnerability, CVE-2021-45042, was fixed in Vault 1.7.7, 1.8.6, and 1.9.1. IMPROVEMENTS: storage/aerospike: Upgrade `aerospike-client-go` to v5.6.0. ] BUG FIXES: auth/approle: Fix regression where unset cidrlist is returned as nil instead of zero-length array. ] ha (enterprise): Prevents performance standby nodes from serving and caching stale data immediately after performance standby election completes http:Fix /sys/monitor endpoint returning streaming not supported ] identity/oidc: Make the `nonce` parameter optional for the Authorization Endpoint of OIDC providers. ] identity: Fixes a panic in the OIDC key rotation due to a missing nil check. ] sdk/queue: move lock before length check to prevent panics. ] secrets/azure: Fixes service principal generation when assigning roles that have . ] secrets/pki: Recognize ed25519 when requesting a response in PKCS8 format ] storage/raft: Fix a panic when trying to store a key > 32KB in a transaction. ] storage/raft: Fix a panic when trying to write a key > 32KB ] ui: Do not show verify connection value on database connection config page ] ui: Fixes issue restoring raft storage snapshot ] ui: Fixes issue with OIDC auth workflow when using MetaMask Chrome extension ] ui: Fixes issue with automate secret deletion value not displaying initially if set in secret metadata edit view ] ui: Fixes issue with placeholder not displaying for automatically deleted secrets when deletion time has passed ] ui: Fixes node-forge error when parsing EC (elliptical curve) certs ] CHANGES: auth/kubernetes: `disableissvalidation` defaults to true. ] expiration: VAULT16REVOKE_PERMITPOOL environment variable has been removed. ] expiration: VAULTLEASEUSELEGACYREVOCATION_STRATEGY environment variable has been removed. ] go: Update go version to 1.17.2 secrets/ssh: Roles with empty allowed_extensions will now forbid end-users specifying extensions when requesting ssh key signing. Update roles setting allowed_extensions to `*` to permit any extension to be specified by an end-user. ] FEATURES: Customizable HTTP Headers: Add support to define custom HTTP headers for root path (`/`) and also on API endpoints (`/v1/`) ] Deduplicate Token With Entities in Activity Log*: Vault tokens without entities are now tracked with client IDs and deduplicated in the Activity Log ] Elasticsearch Database UI*: The UI now supports adding and editing Elasticsearch connections in the database secret engine. ] KV Custom Metadata*: Add ability in kv-v2 to specify version-agnostic custom key metadata via the metadata endpoint. The data will be present in responses made to the data endpoint independent of the calling token's `read` access to the metadata endpoint. ] KV patch (Tech Preview)*: Add partial update support for the `/<mount>/data/:path` kv-v2 endpoint through HTTP `PATCH`. A new `patch` ACL capability has been added and is required to make such requests. ] Key Management Secrets Engine (Enterprise)*: Adds support for distributing and managing keys in GCP Cloud KMS. Local Auth Mount Entities (enterprise)*: Logins on `local` auth mounts will generate identity entities for the tokens issued. The aliases of the entity resulting from local auth mounts (local-aliases), will be scoped by the cluster. This means that the local-aliases will never leave the geographical boundary of the cluster where they were issued. This is something to be mindful about for those who have implemented local auth mounts for complying with GDPR guidelines. Namespaces (Enterprise)*: Adds support for locking Vault API for particular namespaces. OIDC Identity Provider (Tech Preview)*: Adds support for Vault to be an OpenID Connect (OIDC)

] Oracle Database UI*: The UI now supports adding and editing Oracle connections in the database secret engine. ] Postgres Database UI*: The UI now supports adding and editing Postgres connections in the database secret engine. ] SECURITY: core/identity: A Vault user with write permission to an entity alias ID sharing a mount accessor with another user may acquire this other users policies by merging their identities. This vulnerability, CVE-2021-41802, was fixed in Vault and Vault Enterprise 1.7.5, 1.8.4, and 1.9.0. core/identity: Templated ACL policies would always match the first-created entity alias if multiple entity aliases existed for a specified entity and mount combination, potentially resulting in incorrect policy enforcement. This vulnerability, CVE-2021-43998, was fixed in Vault and Vault Enterprise 1.7.6, 1.8.5, and 1.9.0. IMPROVEMENTS: agent/cache: Process persistent cache leases in dependency order during restore to ensure child leases are always correctly restored ] agent/cache: Use an in-process listener between consul-template and vault-agent when caching is enabled and either templates or a listener is defined ] agent/cache: tolerate partial restore failure from persistent cache ] agent/template: add support for new 'writeToFile' template function ] api: Add configuration option for ensuring isolated read-after-write semantics for all Client requests. ] api: adds native Login method to Go client module with different auth method interfaces to support easier authentication ] api: Move mergeStates and other required utils from agent to api module ] api: Support VAULTHTTPPROXY environment variable to allow overriding the Vault client's HTTP proxy ] auth/approle: The `role/:name/secret-id-accessor/lookup` endpoint now returns a 404 status code when the `secretidaccessor` cannot be found ] auth/approle: expose secretidaccessor as WrappedAccessor when creating wrapped secret-id. ] auth/aws: add profile support for AWS credentials when using the AWS auth method ] auth/kubernetes: validate JWT against the provided role on alias look ahead operations ] auth/kubernetes: Add ability to configure entity alias names based on the serviceaccount's namespace and name. ] auth/ldap: include support for an optional user filter field when searching for users ] auth/oidc: Adds the `skip_browser` CLI option to allow users to skip opening the default browser during the authentication flow. ] auth/okta: Send x-forwarded-for in Okta Push Factor request ] auth/token: Add `allowedpoliciesglob` and `disallowedpoliciesglob` fields to token roles to allow glob matching of policies ] cli: Operator diagnose now tests for missing or partial telemetry configurations. ] cli: add new http option : -header which enable sending arbitrary headers with the cli ] command: operator generate-root -decode: allow passing encoded token via stdin ] core/token: Return the tokennodefault_policy config on token role read if set ] core: Add support for go-sockaddr templated addresses in config. ] core: adds custom_metadata field for aliases ] core: Update Oracle Cloud library to enable seal integration with the uk-gov-london-1 region ] core: Update github.com/ulikunitz/xz to fix security vulnerability GHSA-25xm-hr59-7c27. ] core: Upgrade github.com/gogo/protobuf ] core: build with Go

and mitigate a breaking change they made that could impact how approle and ssh interpret IPs/CIDRs ] core: observe the client counts broken down by namespace for partial month client count ] core: Artifact builds will now only run on merges to the release branches or to `main` core: The that is used to build the vault docker image available at now lives in the root of this repo, and the entrypoint is available under core: The vault linux packaging service configs and pre/post install scripts are now available under core: Vault linux packages are now available for all supported linux architectures including arm, arm64, 386, and amd64 db/cassandra: make the connect_timeout config option actually apply to connection timeouts, in addition to non-connection operations ] identity/token: Only return keys from the `.well-known/keys` endpoint that are being used by roles to sign/verify tokens. ] identity: fix issue where Cache-Control header causes stampede of requests for JWKS keys ] physical/etcd: Upgrade etcd3 client to v3.5.0 and etcd2 to v2.305.0. ] pki: adds signature_bits field to customize signature algorithm on CAs and certs signed by Vault ] plugin: update the couchbase gocb version in the couchbase plugin ] replication (enterprise): Add merkle.flushDirty.numpagesoutstanding metric which specifies number of outstanding dirty pages that were not flushed. ] sdk/framework: The '+' wildcard is now supported for parameterizing unauthenticated paths. ] secrets/aws: Add conditional template that allows custom usernames for both STS and IAM cases ] secrets/azure: Adds support for rotate-root. ] secrets/azure: Adds support for using Microsoft Graph API since Azure Active Directory API is being removed in 2022. ] secrets/database: Update MSSQL dependency github.com/denisenkom/go-mssqldb to v0.11.0 and include support for contained databases in MSSQL plugin ] secrets/pki: Allow signing of self-issued certs with a different signature algorithm. ] secrets/pki: Use entropy augmentation when available when generating root and intermediate CA key material. ] secrets/pki: select appropriate signature algorithm for ECDSA signature on certificates. ] secrets/pki: Support ed25519 as a key for the pki backend ] secrets/rabbitmq: Update dependency github.com/michaelklishin/rabbit-hole to v2 and resolve UserInfo.tags regression from RabbitMQ v3.9 ] secrets/ssh: Let allowed_users template mix templated and non-templated parts. ] secrets/ssh: Use entropy augmentation when available for generation of the signing key. ] serviceregistration: add `external-source: "vault"` metadata value for Consul registration. ] storage/raft: Best-effort handling of cancelled contexts. ] transform (enterprise): Add advanced features for encoding and decoding for Transform FPE transform (enterprise): Add a `reference` field to batch items, and propogate it to the response ui: Add KV secret search box when no metadata list access. ] ui: Add custom metadata to KV secret engine and metadata to config ] ui: Creates new StatText component ] ui: client count monthly view ] ui: creates bar chart component for displaying client count data by namespace ] ui: Add creation time to KV 2 version history and version view ] ui: Added resize for JSON editor ] ] ui: Adds warning about white space in KV secret engine. ] ui: Click to copy database static role last rotation value in tooltip ] ui: Filter DB connection attributes so only relevant attrs POST to backend ] ui: Removes empty rows from DB config views ] ui: Standardizes toolbar presentation of destructive actions ] ui: Updates font for table row value fields ] ui: namespace search in client count views ] ui: parse and display pki cert metadata ] ui: replaces Vault's use of elazarl/go-bindata-assetfs in building the UI with Go's native Embed package ] ui: updated client tracking config view ] DEPRECATIONS: auth/kubernetes: deprecate `disableissvalidation` and `issuer` configuration fields ] BUG FIXES: activity log (enterprise): allow partial monthly client count to be accessed from namespaces ] agent: Avoid possible `unexpected fault address` panic when using persistent cache. ] api: Fixes storage APIs returning incorrect error when parsing responses ] auth/aws: Fix ec2 auth on instances that have a cert in their PKCS7 signature ] auth/aws: Fixes ec2 login no longer supporting DSA signature verification ] auth/aws: fix config/rotate-root to store new key ] auth/jwt: Fixes OIDC auth from the Vault UI when using `formpost` as the

] cli/api: Providing consistency for the use of comma separated parameters in auth/secret enable/tune ] cli: fixes CLI requests when namespace is both provided as argument and part of the path ] cli: fixes CLI requests when namespace is both provided as argument and part of the path ] cli: vault debug now puts newlines after every captured log line. ] core (enterprise): Allow deletion of stored licenses on DR secondary nodes core (enterprise): Disallow autogenerated licenses to be used in diagnose even when config is specified core (enterprise): Fix bug where password generation through password policies do not work on namespaces if performed outside a request callback or from an external plugin. ] core (enterprise): Fix data race during perf standby sealing core (enterprise): Fixes reading raft auto-snapshot configuration from performance standby node ] core (enterprise): Only delete quotas on primary cluster. ] core (enterprise): namespace header included in responses, Go client uses it when displaying error messages ] core/api: Fix an arm64 bug converting a negative int to an unsigned int ] core/identity: Address a data race condition between local updates to aliases and invalidations ] core/identity: Cleanup alias in the in-memory entity after an alias deletion by ID ] core/identity: Disallow entity alias creation/update if a conflicting alias exists for the target entity and mount combination ] core: Fix a deadlock on HA leadership transfer ] core: Fix warnings logged on perf standbys re stored versions ] core: fix byte printing for diagnose disk checks ] core: revert some unintentionally downgraded dependencies from 1.9.0-rc1 ] database/couchbase: change default template to truncate username at 128 characters ] database/postgres: Update postgres library (github.com/lib/pq) to properly remove terminated TLS connections from the connection pool. ] http (enterprise): Always forward internal/counters endpoints from perf standbys to active node http: removed unpublished true from logical_system path, making openapi spec consistent with documentation ] identity/token: Adds missing call to unlock mutex in key deletion error handling ] identity: Fail alias rename if the resulting (name,accessor) exists already ] identity: Fix a panic on arm64 platform when doing identity I/O. ] identity: Fix regression preventing startup when aliases were created pre-1.9. ] identity: dedup fromentityids when merging two entities ] identity: disallow creation of role without a key parameter ] identity: do not allow a role's tokenttl to be longer than the signing key's verificationttl ] identity: merge associated entity groups when merging entities ] identity: suppress duplicate policies on entities ] kmip (enterprise): Fix handling of custom attributes when servicing GetAttributes requests kmip (enterprise): Fix handling of invalid role parameters within various vault api calls kmip (enterprise): Forward KMIP register operations to the active node license: ignore stored terminated license while autoloading is enabled ] licensing (enterprise): Revert accidental inclusion of the TDE feature from the `prem` build. physical/raft: Fix safeio.Rename error when restoring snapshots on windows ] pki: Fix regression preventing email addresses being used as a common name within certificates ] plugin/couchbase: Fix an issue in which the locking patterns did not allow parallel requests. ] plugin/snowflake: Fixed bug where plugin would crash on 32 bit systems ] raft (enterprise): Fix panic when updating auto-snapshot config replication (enterprise): Fix issue where merkle.flushDirty.num_pages metric is not emitted if number of dirty pages is 0. ] replication (enterprise): Fix merkle.saveCheckpoint.num_dirty metric to accurately specify the number of dirty pages in the merkle tree at time of checkpoint creation. ] sdk/database: Fix a DeleteUser error message on the gRPC client. ] secrets/db: Fix bug where Vault can rotate static role passwords early during start up under certain conditions. ] secrets/gcp: Fixes a potential panic in the service account policy rollback for rolesets. ] secrets/keymgmt (enterprise): Fix support for Azure Managed HSM Key Vault

] secrets/openldap: Fix bug where Vault can rotate static role passwords early during start up under certain conditions. ] secrets/transit: Enforce minimum cache size for transit backend and init cache size on transit backend without restart. ] storage/postgres: Update postgres library (github.com/lib/pq) to properly remove terminated TLS connections from the connection pool. ] storage/raft (enterprise): Ensure that raft autosnapshot backoff retry duration never hits 0s storage/raft: Detect incomplete raft snapshots in api.RaftSnapshot(), and thereby in `vault operator raft snapshot save`. ] storage/raft: Fix regression in 1.9.0-rc1 that changed how time is represented in Raft logs; this prevented using a raft db created pre-1.9. ] storage/raft: Support `addrtype=publicv6` in auto-join ] transform (enterprise): Enforce minimum cache size for Transform backend and reset cache size without a restart transform (enterprise): Fix an error where the decode response of an expired token is an empty result rather than an error. ui: Adds pagination to auth methods list view ] ui: Fix bug where capabilities check on secret-delete-menu was encoding the forward slashes. ] ui: Fix bug where edit role form on auth method is invalid by default ] ui: Fixed api explorer routing bug ] ui: Fixed text overflow in flash messages ] ui: Fixes issue with the number of PGP Key inputs not matching the key shares number in the initialization form on change ] ui: Fixes metrics page when read on counter config not allowed ] ui: Remove spinner after token renew ] ui: Removes ability to tune token_type for token auth methods ] ui: Show day of month instead of day of year in the expiration warning dialog ] ui: fix issue where on MaskedInput on auth methods if tab it would clear the value. ] ui: fix missing navbar items on login to namespace ] ui: update bar chart when model changes ] ui: updating database TTL picker help text. ] BUG FIXES: agent: Redact auto auth token from renew endpoints ] core: Prevent changing file permissions of audit logs when mode 0000 is used. ] core: fixed systemd reloading notification ] core: pre-calculate namespace specific paths when tainting a route during postUnseal ] storage/raft (enterprise): Auto-snapshot configuration now forbids slashes in file prefixes for all types, and "/" in path prefix for local storage type. Strip leading prefix in path prefix for AWS. Improve error handling/reporting. transform (enterprise): Fix non-overridable column default value causing tokenization tokens to expire prematurely when using the MySQL storage backend. BUG FIXES: raft: fix Raft TLS key rotation panic that occurs if active key is more than 24 hours old ] sdk: Fix OpenApi spec generator to properly convert TypeInt64 to OAS supported int64 ] CHANGES: core: A request that fails path validation due to relative path check will now be responded to with a 400 rather than 500. ] core: Bump Go version to 1.16.15. ] IMPROVEMENTS: auth/ldap: Add usernameasalias configurable to change how aliases are named ] core: Systemd unit file included with the Linux packages now sets the service type to

] sentinel (enterprise): Upgrade sentinel to to avoid potential naming collisions in the remote installer BUG FIXES: api/sys/raft: Update RaftSnapshotRestore to use net/http client allowing bodies larger than allocated memory to be streamed ] auth/approle: Add maximum length for input values that result in SHA56 HMAC calculation ] cassandra: Update gocql Cassandra client to fix "no hosts available in the pool" error ] cli: Fix panic caused by parsing key=value fields whose value is a single backslash ] core: Fix panic caused by parsing JSON integers for fields defined as comma-delimited integers ] core: Fix panic caused by parsing JSON integers for fields defined as comma-delimited strings ] core: Fix panic caused by parsing policies with empty slice values. ] core: Fix panic for help request URL paths without /v1/ prefix ] core: fixing excessive unix file permissions ] core: fixing excessive unix file permissions on dir, files and archive created by vault debug command ] core: report unused or redundant keys in server configuration ] core: time.After() used in a select statement can lead to memory leak ] metrics/autosnapshots (enterprise) : Fix bug that could cause vault.autosnapshots.save.errors to not be incremented when there is an autosnapshot save error. ui: Fix Generated Token's Policies helpText to clarify that comma separated values are not excepted in this field. ] ui: Fixes edit auth method capabilities issue ] ui: Fixes issue logging out with wrapped token query parameter ] ui: Fixes issue with correct auth method not selected when logging out from OIDC or JWT methods ] ui: fix search-select component showing blank selections when editing group member entity ] ui: masked values no longer give away length or location of special characters ] secrets/pki: Vault and Vault Enterprise (Vault) allowed the PKI secrets engine under certain configurations to issue wildcard certificates to authorized users for a specified domain, even if the PKI role policy attribute allow_subdomains is set to false. This vulnerability, CVE-2022-25243, was fixed in Vault 1.8.9 and 1.9.4. transform (enterprise): Vault Enterprise (Vault) clusters using the tokenization transform feature can expose the tokenization key through the tokenization key configuration endpoint to authorized operators with read permissions on this endpoint. This vulnerability, CVE-2022-25244, was fixed in Vault Enterprise 1.7.10, 1.8.9, and 1.9.4. IMPROVEMENTS: secrets/pki: Restrict issuance of wildcard certificates via role parameter (`allowwildcardcertificates`) ] BUG FIXES: auth/aws: Fix ec2 auth on instances that have a cert in their PKCS7 signature ] database/mssql: Removed string interpolation on internal queries and replaced them with inline queries using named parameters. ] secrets/openldap: Fix panic from nil logger in backend ] secrets/pki: Fix issuance of wildcard certificates matching glob patterns ] ui: Fix issue removing raft storage peer via cli not reflected in UI until refresh ] ui: Trigger background token self-renewal if inactive and half of TTL has passed ] IMPROVEMENTS: core: Fixes code scanning alerts ] BUG FIXES: auth/oidc: Fixes OIDC auth from the Vault UI when using the implicit flow and `form_post` response mode. ] core (enterprise): Workaround AWS CloudHSM v5 SDK issue not allowing read-only sessions kmip (enterprise): Fix locate by name operations fail to find key after a rekey operation. secrets/gcp: Fixes role bindings for BigQuery dataset resources. ] secrets/pki: Fix regression causing performance secondaries to forward certificate generation to the primary. ] secrets/pki: Fix regression causing performance secondaries to forward certificate generation to the primary. ] storage/raft: Fix issues allowing invalid nodes to become leadership candidates. ] storage/raft: On linux, use map_populate for bolt files to improve startup time. ] storage/raft: Units for bolt metrics now given in milliseconds instead of nanoseconds ] ui: Fixes breadcrumb bug for secrets navigation ] ui: Fixes issue saving KMIP role correctly ] CHANGES: go: Update go version to 1.16.12 ] CHANGES: go: Update go version to 1.16.9 ] SECURITY: storage/raft: Integrated Storage backend could be caused to crash by an authenticated user with write permissions to the KV secrets engine. This vulnerability, CVE-2021-45042, was fixed in Vault 1.7.7, 1.8.6, and

BUG FIXES: ha (enterprise): Prevents performance standby nodes from serving and caching stale data immediately after performance standby election completes storage/raft: Fix a panic when trying to store a key > 32KB in a transaction. ] storage/raft: Fix a panic when trying to write a key > 32KB ] ui: Adds pagination to auth methods list view ] ui: Do not show verify connection value on database connection config page ] ui: Fixes issue restoring raft storage snapshot ] ui: Fixes issue with OIDC auth workflow when using MetaMask Chrome extension ] ui: Fixes issue with the number of PGP Key inputs not matching the key shares number in the initialization form on change ] SECURITY: core/identity: Templated ACL policies would always match the first-created entity alias if multiple entity aliases existed for a specified entity and mount combination, potentially resulting in incorrect policy enforcement. This vulnerability, CVE-2021-43998, was fixed in Vault and Vault Enterprise 1.7.6, 1.8.5, and 1.9.0. BUG FIXES: auth/aws: fix config/rotate-root to store new key ] core/identity: Cleanup alias in the in-memory entity after an alias deletion by ID ] core/identity: Disallow entity alias creation/update if a conflicting alias exists for the target entity and mount combination ] http (enterprise): Always forward internal/counters endpoints from perf standbys to active node identity/token: Adds missing call to unlock mutex in key deletion error handling ] kmip (enterprise): Fix handling of custom attributes when servicing GetAttributes requests kmip (enterprise): Fix handling of invalid role parameters within various vault api calls kmip (enterprise): Forward KMIP register operations to the active node secrets/keymgmt (enterprise): Fix support for Azure Managed HSM Key Vault instances. ] transform (enterprise): Fix an error where the decode response of an expired token is an empty result rather than an error. SECURITY: core/identity: A Vault user with write permission to an entity alias ID sharing a mount accessor with another user may acquire this other users policies by merging their identities. This vulnerability, CVE-2021-41802, was fixed in Vault and Vault Enterprise 1.7.5 and 1.8.4. IMPROVEMENTS: core: Update Oracle Cloud library to enable seal integration with the uk-gov-london-1 region ] BUG FIXES: core: Fix a deadlock on HA leadership transfer ] database/postgres: Update postgres library (github.com/lib/pq) to properly remove terminated TLS connections from the connection pool. ] pki: Fix regression preventing email addresses being used as a common name within certificates ] storage/postgres: Update postgres library (github.com/lib/pq) to properly remove terminated TLS connections from the connection pool. ] ui: Fix bug where edit role form on auth method is invalid by default ] IMPROVEMENTS: secrets/pki: Allow signing of self-issued certs with a different signature algorithm. ] BUG FIXES: agent: Avoid possible `unexpected fault address` panic when using persistent cache. ] core (enterprise): Allow deletion of stored licenses on DR secondary nodes core (enterprise): Fix bug where password generation through password policies do not work on namespaces if performed outside a request callback or from an external plugin. ] core (enterprise): Only delete quotas on primary cluster. ] identity: Fail alias rename if the resulting (name,accessor) exists already ] raft (enterprise): Fix panic when updating auto-snapshot config secrets/db: Fix bug where Vault can rotate static role passwords early during start up under certain conditions. ] secrets/openldap: Fix bug where Vault can rotate static role passwords early during start up under certain conditions. ] secrets/transit: Enforce minimum cache size for transit backend and init cache size on transit backend without restart. ] storage/raft: Detect incomplete raft snapshots in api.RaftSnapshot(), and thereby in `vault operator raft snapshot save`. ] ui: Fix bug where capabilities check on secret-delete-menu was encoding the forward

] ui: Show day of month instead of day of year in the expiration warning dialog ] CHANGES: Alpine: Docker images for Vault 1.6.6+, 1.7.4+, and 1.8.2+ are built with Alpine 3.14, due to CVE-2021-36159 go: Update go version to 1.16.7 ] BUG FIXES: auth/aws: Fixes ec2 login no longer supporting DSA signature verification ] cli: vault debug now puts newlines after every captured log line. ] database/couchbase: change default template to truncate username at 128 characters ] identity: Fix a panic on arm64 platform when doing identity I/O. ] physical/raft: Fix safeio.Rename error when restoring snapshots on windows ] plugin/snowflake: Fixed bug where plugin would crash on 32 bit systems ] sdk/database: Fix a DeleteUser error message on the gRPC client. ] secrets/gcp: Fixes a potential panic in the service account policy rollback for rolesets. ] ui: Fixed api explorer routing bug ] ui: Fixes metrics page when read on counter config not allowed ] ui: fix issue where on MaskedInput on auth methods if tab it would clear the value. ] CHANGES: go: Update go version to 1.16.6 ] IMPROVEMENTS: serviceregistration: add `external-source: "vault"` metadata value for Consul registration. ] BUG FIXES: auth/aws: Remove warning stating AWS Token TTL will be capped by the Default Lease TTL. ] auth/jwt: Fixes OIDC auth from the Vault UI when using `formpost` as the `oidcresponse_mode`. ] core (enterprise): Disallow autogenerated licenses to be used in diagnose even when config is specified core: fix byte printing for diagnose disk checks ] identity: do not allow a role's tokenttl to be longer than the signing key's verificationttl ] CHANGES: agent: Errors in the template engine will no longer cause agent to exit unless explicitly defined to do so. A new configuration parameter, `exitonretryfailure`, within the new top-level stanza, `templateconfig`, can be set to `true` in order to cause agent to exit. Note that for agent to exit if `template.erroronmissingkey` is set to `true`, `exitonretryfailure` must be also set to `true`. Otherwise, the template engine will log an error but then restart its internal runner. ] agent: Update to use IAM Service Account Credentials endpoint for signing JWTs when using GCP Auto-Auth method ] core (enterprise): License/EULA changes that ensure the presence of a valid HashiCorp license to start Vault. More information is available in the FEATURES: GCP Secrets Engine Static Accounts*: Adds ability to use existing service accounts for generation of service account keys and access tokens. ] Key Management Secrets Engine (Enterprise)*: Adds general availability for distributing and managing keys in AWS KMS. ] License Autoloading (Enterprise)*: Licenses may now be automatically loaded from the environment or disk. MySQL Database UI*: The UI now supports adding and editing MySQL connections in the database secret engine ] Vault Diagnose*: A new `vault operator` command to detect common issues with vault server setups. SECURITY: storage/raft: When initializing Vaults Integrated Storage backend, excessively broad filesystem permissions may be set for the underlying Bolt database used by Vaults Raft implementation. This vulnerability, CVE-2021-38553, was fixed in Vault 1.8.0. ui: The Vault UI erroneously cached and exposed user-viewed secrets between authenticated sessions in a single shared browser, if the browser window / tab was not refreshed or closed between logout and a subsequent login. This vulnerability, CVE-2021-38554, was fixed in Vault 1.8.0 and will be addressed in pending 1.7.4 / 1.6.6 releases. IMPROVEMENTS: agent/template: Added staticsecretrender_interval to specify how often to fetch non-leased secrets ] agent: Allow Agent auto auth to read symlinked JWT files ] api: Allow a leveled logger to be provided to

through `SetLogger`. ] auth/aws: Underlying error included in validation failure message. ] cli/api: Add lease lookup command ] core: Add `prefix_filter` to telemetry config ] core: Add a darwin/arm64 binary release supporting the Apple M1 CPU ] core: Add a small (<1s) exponential backoff to failed TCP listener Accept failures. ] core (enterprise): Add controlled capabilities to control group policy stanza core: Add metrics for standby node forwarding. ] core: Add metrics to report if a node is a perf standby, if a node is a dr secondary or primary, and if a node is a perf secondary or primary. ] core: Send notifications to systemd on start, stop, and configuration reload. ] core: add irrevocable lease list and count apis ] core: allow arbitrary length stack traces upon receiving SIGUSR2 (was 32MB) ] core: Improve renew/revoke performance using per-lease locks ] db/cassandra: Added tlsservername to specify server name for TLS validation ] go: Update to Go 1.16.5 ] replication: Delay evaluation of X-Vault-Index headers until merkle sync completes. secrets/rabbitmq: Add ability to customize dynamic usernames ] secrets/ad: Add `rotate-role` endpoint to allow rotations of service accounts. ] secrets/aws: add IAM tagging support for iam_user roles ] secrets/aws: add ability to provide a role session name when generating STS credentials ] secrets/database/elasticsearch: Add ability to customize dynamic usernames ] secrets/database/influxdb: Add ability to customize dynamic usernames ] secrets/database/mongodb: Add ability to customize `SocketTimeout`, `ConnectTimeout`, and `ServerSelectionTimeout` ] secrets/database/mongodb: Increased throughput by allowing for multiple request threads to simultaneously update users in MongoDB ] secrets/database/mongodbatlas: Adds the ability to customize username generation for dynamic users in MongoDB Atlas. ] secrets/database/redshift: Add ability to customize dynamic usernames ] secrets/database/snowflake: Add ability to customize dynamic usernames ] ssh: add support for templated values in SSH CA DefaultExtensions ] storage/raft: Improve raft batch size selection ] storage/raft: change freelist type to map and set nofreelistsync to true ] storage/raft: Switch to shared raft-boltdb library and add boltdb metrics ] storage/raft: Support autopilot for HA only raft storage. ] storage/raft (enterprise): Enable Autopilot on DR secondary clusters ui: Add Validation to KV secret engine ] ui: Add database secret engine support for MSSQL ] ui: Add push notification message when selecting okta auth. ] ui: Add regex validation to Transform Template pattern input ] ui: Add specific error message if unseal fails due to license ] ui: Add validation support for open api form fields ] ui: Added auth method descriptions to UI login page ] ui: JSON fields on database can be cleared on edit ] ui: Obscure secret values on input and displayOnly fields like certificates. ] ui: Redesign of KV 2 Delete toolbar. ] ui: Replace tool partials with components. ] ui: Show description on secret engine list ] ui: Update ember to latest LTS and upgrade UI dependencies ] ui: Update partials to components ] ui: Updated ivy code mirror component for consistency ] ui: Updated node to v14, latest stable build ] ui: Updated search select component styling ] ui: add transform secrets engine to features list ] ui: add validations for duplicate path kv engine ] ui: show site-wide banners for license warnings if applicable ] ui: update license page with relevant autoload info ] DEPRECATIONS: secrets/gcp: Deprecated the `/gcp/token/:roleset` and `/gcp/key/:roleset` paths for generating secrets for rolesets. Use `/gcp/roleset/:roleset/token` and `/gcp/roleset/:roleset/key`

] BUG FIXES: activity: Omit wrapping tokens and control groups from client counts ] agent/cert: Fix issue where the API client on agent was not honoring certificate information from the auto-auth config map on renewals or retries. ] agent/template: fix command shell quoting issue ] agent: Fixed agent templating to use configured tls servername values ] agent: fix timestamp format in log messages from the templating engine ] auth/approle: fixing dereference of nil pointer ] auth/jwt: Updates the library to `v0.1.0` to bring in a verification key caching fix. ] auth/kubernetes: Fix AliasLookahead to correctly extract ServiceAccount UID when using ephemeral JWTs ] auth/ldap: Fix a bug where the LDAP auth method does not return the request_timeout configuration parameter on config read. ] cli: Add support for response wrapping in `vault list` and `vault kv list` with output format other than `table`. ] cli: vault delete and vault kv delete should support the same output options (e.g. -format) as vault write. ] core (enterprise): Fix orphan return value from auth methods executed on performance standby nodes. core (enterprise): Fix plugins mounted in namespaces being unable to use password policies ] core (enterprise): serialize access to HSM entropy generation to avoid errors in concurrent key generation. core/metrics: Add generic KV mount support for vault.kv.secret.count telemetry metric ] core: Fix cleanup of storage entries from cubbyholes within namespaces. ] core: Fix edge cases in the configuration endpoint for barrier key autorotation. ] core: Fix goroutine leak when updating rate limit quota ] core (enterprise): Fix panic on DR secondary when there are lease count quotas ] core: Fix race that allowed remounting on path used by another mount ] core: Fix storage entry leak when revoking leases created with non-orphan batch tokens. ] core: Fixed double counting of http requests after operator stepdown ] core: correct logic for renewal of leases nearing their expiration time. ] identity: Use correct mount accessor when refreshing external group memberships. ] mongo-db: default username template now strips invalid '.' characters ] pki: Only remove revoked entry for certificates during tidy if they are past their NotAfter value ] replication: Fix panic trying to update walState during identity group invalidation. replication: Fix: mounts created within a namespace that was part of an Allow filtering rule would not appear on performance secondary if created after rule was defined. secret/pki: use case insensitive domain name comparison as per RFC1035 section 2.3.3 secret: fix the bug where transit encrypt batch doesn't work with key_version ] secrets/ad: Forward all creds requests to active node ] ] secrets/database/cassandra: Fixed issue where hostnames were not being validated when using TLS ] secrets/database/cassandra: Fixed issue where the PEM parsing logic of `pembundle` and `pemjson` didn't work for CA-only configurations ] secrets/database/cassandra: Updated default statement for password rotation to allow for special characters. This applies to root and static credentials. ] secrets/database: Fix marshalling to allow providing numeric arguments to external database plugins. ] secrets/database: Fixed an issue that prevented external database plugin processes from restarting after a shutdown. ] secrets/database: Fixed minor race condition when rotate-root is called ] secrets/database: Fixes issue for V4 database interface where `SetCredentials` wasn't falling back to using `RotateRootCredentials` if `SetCredentials` is `Unimplemented` ] secrets/openldap: Fix bug where schema was not compatible with rotate-root ] storage/dynamodb: Handle throttled batch write requests by retrying, without which writes could be lost. ] storage/raft: Support cluster address change for nodes in a cluster managed by autopilot ] storage/raft: Tweak creation of vault.db file ] storage/raft: leadertlsservername wasn't used unless leadercacert_file and/or mTLS were configured. ] tokenutil: Perform the num uses check before token type. ] transform (enterprise): Fix an issue with malformed transform configuration storage when upgrading from 1.5 to

See Upgrade Notes for 1.6.x. ui: Add role from database connection automatically populates the database for new role ] ui: Add root rotation statements support to appropriate database secret engine plugins ] ui: Automatically refresh the page when user logs out ] ui: Fix Version History queryParams on LinkedBlock ] ui: Fix bug where database secret engines with custom names cannot delete connections ] ui: Fix bug where the UI does not recognize version 2 KV until refresh, and fix ] ui: Fix database role CG access ] ui: Fix date display on expired token notice ] ui: Fix entity group membership and metadata not showing ] ui: Fix error message caused by control group ] ui: Fix footer URL linking to the correct version changelog. ] ui: Fix issue where logging in without namespace input causes error ] ui: Fix namespace-bug on login ] ui: Fix status menu no showing on login ] ui: Fix text link URL on database roles list ] ui: Fixed and updated lease renewal picker ] ui: fix control group access for database credential ] ui: fix issue where select-one option was not showing in secrets database role creation ] ui: fix oidc login with Safari ] SECURITY: transform (enterprise): Vault Enterprise (Vault) clusters using the tokenization transform feature can expose the tokenization key through the tokenization key configuration endpoint to authorized operators with read permissions on this endpoint. This vulnerability, CVE-2022-25244, was fixed in Vault Enterprise 1.7.10, 1.8.9, and 1.9.4. BUG FIXES: database/mssql: Removed string interpolation on internal queries and replaced them with inline queries using named parameters. ] ui: Fix issue removing raft storage peer via cli not reflected in UI until refresh ] ui: Trigger background token self-renewal if inactive and half of TTL has passed ] IMPROVEMENTS: core: Fixes code scanning alerts ] BUG FIXES: auth/oidc: Fixes OIDC auth from the Vault UI when using the implicit flow and `form_post` response mode. ] secrets/gcp: Fixes role bindings for BigQuery dataset resources. ] ui: Fixes breadcrumb bug for secrets navigation ] ui: Fixes issue saving KMIP role correctly ] CHANGES: go: Update go version to 1.16.12 ] BUG FIXES: auth/aws: Fixes ec2 login no longer supporting DSA signature verification ] identity: Fix a panic on arm64 platform when doing identity I/O. ] SECURITY: storage/raft: Integrated Storage backend could be caused to crash by an authenticated user with write permissions to the KV secrets engine. This vulnerability, CVE-2021-45042, was fixed in Vault 1.7.7, 1.8.6, and 1.9.1. BUG FIXES: ha (enterprise): Prevents performance standby nodes from serving and caching stale data immediately after performance standby election completes storage/raft: Fix a panic when trying to store a key > 32KB in a transaction. ] storage/raft: Fix a panic when trying to write a key > 32KB ] ui: Fixes issue restoring raft storage snapshot ] ui: Fixes issue with OIDC auth workflow when using MetaMask Chrome extension ] ui: Fixes issue with the number of PGP Key inputs not matching the key shares number in the initialization form on change ] SECURITY: core/identity: Templated ACL policies would always match the first-created entity alias if multiple entity aliases existed for a specified entity and mount combination, potentially resulting in incorrect policy enforcement. This vulnerability, CVE-2021-43998, was fixed in Vault and Vault Enterprise 1.7.6, 1.8.5, and

BUG FIXES: auth/aws: fix config/rotate-root to store new key ] core/identity: Cleanup alias in the in-memory entity after an alias deletion by ID ] core/identity: Disallow entity alias creation/update if a conflicting alias exists for the target entity and mount combination ] core: Fix a deadlock on HA leadership transfer ] http (enterprise): Always forward internal/counters endpoints from perf standbys to active node kmip (enterprise): Fix handling of custom attributes when servicing GetAttributes requests kmip (enterprise): Fix handling of invalid role parameters within various vault api calls kmip (enterprise): Forward KMIP register operations to the active node secrets/keymgmt (enterprise): Fix support for Azure Managed HSM Key Vault instances. ] storage/postgres: Update postgres library (github.com/lib/pq) to properly remove terminated TLS connections from the connection pool. ] database/postgres: Update postgres library (github.com/lib/pq) to properly remove terminated TLS connections from the connection pool. ] transform (enterprise): Fix an error where the decode response of an expired token is an empty result rather than an error. SECURITY: core/identity: A Vault user with write permission to an entity alias ID sharing a mount accessor with another user may acquire this other users policies by merging their identities. This vulnerability, CVE-2021-41802, was fixed in Vault and Vault Enterprise 1.7.5 and 1.8.4. IMPROVEMENTS: secrets/pki: Allow signing of self-issued certs with a different signature algorithm. ] BUG FIXES: agent: Avoid possible `unexpected fault address` panic when using persistent cache. ] core (enterprise): Fix bug where password generation through password policies do not work on namespaces if performed outside a request callback or from an external plugin. ] core (enterprise): Only delete quotas on primary cluster. ] identity: Fail alias rename if the resulting (name,accessor) exists already ] raft (enterprise): Fix panic when updating auto-snapshot config secrets/db: Fix bug where Vault can rotate static role passwords early during start up under certain conditions. ] secrets/openldap: Fix bug where Vault can rotate static role passwords early during start up under certain conditions. ] storage/raft: Detect incomplete raft snapshots in api.RaftSnapshot(), and thereby in `vault operator raft snapshot save`. ] ui: Fixed api explorer routing bug ] SECURITY: UI Secret Caching: The Vault UI erroneously cached and exposed user-viewed secrets between authenticated sessions in a single shared browser, if the browser window / tab was not refreshed or closed between logout and a subsequent login. This vulnerability, CVE-2021-38554, was fixed in Vault 1.8.0 and will be addressed in pending 1.7.4 / 1.6.6 releases. CHANGES: Alpine: Docker images for Vault 1.6.6+, 1.7.4+, and 1.8.2+ are built with Alpine 3.14, due to CVE-2021-36159 go: Update go version to 1.15.15 ] IMPROVEMENTS: ui: Updated node to v14, latest stable build ] BUG FIXES: replication (enterprise): Fix a panic that could occur when checking the last wal and the log shipper buffer is empty. cli: vault debug now puts newlines after every captured log line. ] database/couchbase: change default template to truncate username at 128 characters ] physical/raft: Fix safeio.Rename error when restoring snapshots on windows ] secrets/database/cassandra: Fixed issue where the PEM parsing logic of `pembundle` and `pemjson` didn't work for CA-only configurations ] secrets/database: Fixed an issue that prevented external database plugin processes from restarting after a shutdown. ] ui: Automatically refresh the page when user logs out ] ui: Fix database role CG access ] ui: Fixes metrics page when read on counter config not allowed ] ui: fix control group access for database credential ] ui: fix oidc login with Safari ] CHANGES: go: Update go version to 1.15.13 ] IMPROVEMENTS: db/cassandra: Added tlsservername to specify server name for TLS validation ] ui: Add specific error message if unseal fails due to license ] BUG FIXES: auth/jwt: Updates the library to `v0.1.0` to bring in a verification key caching

] core (enterprise): serialize access to HSM entropy generation to avoid errors in concurrent key generation. secret: fix the bug where transit encrypt batch doesn't work with key_version ] secrets/ad: Forward all creds requests to active node ] ] tokenutil: Perform the num uses check before token type. ] SECURITY: Non-Expiring Leases: Vault and Vault Enterprise renewed nearly-expiring token leases and dynamic secret leases with a zero-second TTL, causing them to be treated as non-expiring, and never revoked. This issue affects Vault and Vault Enterprise versions 0.10.0 through 1.7.1, and is fixed in 1.5.9, 1.6.5, and 1.7.2 (CVE-2021-32923). CHANGES: agent: Update to use IAM Service Account Credentials endpoint for signing JWTs when using GCP Auto-Auth method ] auth/gcp: Update to v0.9.1 to use IAM Service Account Credentials API for signing JWTs ] IMPROVEMENTS: api, agent: LifetimeWatcher now does more retries when renewal failures occur. This also impacts Agent auto-auth and leases managed via Agent caching. ] auth/aws: Underlying error included in validation failure message. ] http: Add optional HTTP response headers for hostname and raft node ID ] secrets/aws: add ability to provide a role session name when generating STS credentials ] secrets/database/mongodb: Add ability to customize `SocketTimeout`, `ConnectTimeout`, and `ServerSelectionTimeout` ] secrets/database/mongodb: Increased throughput by allowing for multiple request threads to simultaneously update users in MongoDB ] BUG FIXES: agent/cert: Fix issue where the API client on agent was not honoring certificate information from the auto-auth config map on renewals or retries. ] agent: Fixed agent templating to use configured tls servername values ] core (enterprise): Fix plugins mounted in namespaces being unable to use password policies ] core: correct logic for renewal of leases nearing their expiration time. ] identity: Use correct mount accessor when refreshing external group memberships. ] replication: Fix panic trying to update walState during identity group invalidation. ] secrets/database: Fix marshalling to allow providing numeric arguments to external database plugins. ] secrets/database: Fixed minor race condition when rotate-root is called ] secrets/database: Fixes issue for V4 database interface where `SetCredentials` wasn't falling back to using `RotateRootCredentials` if `SetCredentials` is `Unimplemented` ] secrets/keymgmt (enterprise): Fixes audit logging for the read key response. storage/raft: Support cluster address change for nodes in a cluster managed by autopilot ] ui: Fix entity group membership and metadata not showing ] ui: Fix text link URL on database roles list ] SECURITY: The PKI Secrets Engine tidy functionality may cause Vault to exclude revoked-but-unexpired certificates from the Vault CRL. This vulnerability affects Vault and Vault Enterprise 1.5.1 and newer and was fixed in versions 1.5.8, 1.6.4, and 1.7.1. (CVE-2021-27668) The Cassandra Database and Storage backends were not correctly verifying TLS certificates. This issue affects all versions of Vault and Vault Enterprise and was fixed in versions 1.6.4, and 1.7.1. (CVE-2021-27400) CHANGES: go: Update to Go 1.15.11 ] IMPROVEMENTS: auth/jwt: Adds ability to directly provide service account JSON in G Suite provider config. ] core: Add tlsmaxversion listener config option. ] core: Add metrics for standby node forwarding. ] core: allow arbitrary length stack traces upon receiving SIGUSR2 (was 32MB) ] storage/raft: Support autopilot for HA only raft storage. ] BUG FIXES: core: Fix cleanup of storage entries from cubbyholes within namespaces. ] core: Fix goroutine leak when updating rate limit quota ] core: Fix storage entry leak when revoking leases created with non-orphan batch tokens. ] core: requests forwarded by standby weren't always timed

] pki: Only remove revoked entry for certificates during tidy if they are past their NotAfter value ] replication: Fix: mounts created within a namespace that was part of an Allow filtering rule would not appear on performance secondary if created after rule was defined. replication: Perf standby nodes on newly enabled DR secondary sometimes couldn't connect to active node with TLS errors. ] secrets/database/cassandra: Fixed issue where hostnames were not being validated when using TLS ] secrets/database/cassandra: Updated default statement for password rotation to allow for special characters. This applies to root and static credentials. ] storage/dynamodb: Handle throttled batch write requests by retrying, without which writes could be lost. ] storage/raft: leadertlsservername wasn't used unless leadercacert_file and/or mTLS were configured. ] storage/raft: using raft for ha_storage with a different storage backend was broken in 1.7.0, now fixed. ] ui: Add root rotation statements support to appropriate database secret engine plugins ] ui: Fix bug where the UI does not recognize version 2 KV until refresh, and fix ] ui: Fix OIDC bug seen when running on HCP ] ui: Fix namespace-bug on login ] ui: Fix status menu no showing on login ] ui: fix issue where select-one option was not showing in secrets database role creation ] CHANGES: agent: Failed auto-auth attempts are now throttled by an exponential backoff instead of the ~2 second retry delay. The maximum backoff may be configured with the new `max_backoff` parameter, which defaults to 5 minutes. ] aws/auth: AWS Auth concepts and endpoints that use the "whitelist" and "blacklist" terms have been updated to more inclusive language (e.g. `/auth/aws/identity-whitelist` has been updated to`/auth/aws/identity-accesslist`). The old and new endpoints are aliases, sharing the same underlying data. The legacy endpoint names are considered deprecated and will be removed in a future release (not before Vault 1.9). The complete list of endpoint changes is available in the . go: Update Go version to 1.15.10 ] ] FEATURES: Aerospike Storage Backend*: Add support for using Aerospike as a storage backend ] Autopilot for Integrated Storage*: A set of features has been added to allow for automatic operator-friendly management of Vault servers. This is only applicable when integrated storage is in use. Dead Server Cleanup*: Dead servers will periodically be cleaned up and removed from the Raft peer set, to prevent them from interfering with the quorum size and leader elections. Server Health Checking*: An API has been added to track the state of servers, including their health. New Server Stabilization*: When a new server is added to the cluster, there will be a waiting period where it must be healthy and stable for a certain amount of time before being promoted to a full, voting member. Tokenization Secrets Engine (Enterprise)*: The Tokenization Secrets Engine is now generally available. We have added support for MySQL, key rotation, and snapshot/restore. replication (enterprise): The log shipper is now memory as well as length bound, and length and size can be separately configured. agent: Support for persisting the agent cache to disk ] auth/jwt: Adds `maxage` role parameter and `authtime` claim validation. ] core (enterprise): X-Vault-Index and related headers can be used by clients to manage eventual consistency. kmip (enterprise): Use entropy augmentation to generate kmip certificates sdk: Private key generation in the certutil package now allows custom io.Readers to be

] secrets/aws: add IAM tagging support for iam_user roles ] secrets/database/cassandra: Add ability to customize dynamic usernames ] secrets/database/couchbase: Add ability to customize dynamic usernames ] secrets/database/mongodb: Add ability to customize dynamic usernames ] secrets/database/mssql: Add ability to customize dynamic usernames ] secrets/database/mysql: Add ability to customize dynamic usernames ] secrets/database/postgresql: Add ability to customize dynamic usernames ] secrets/db/snowflake: Added support for Snowflake to the Database Secret Engine ] secrets/keymgmt (enterprise): Adds beta support for distributing and managing keys in AWS KMS. secrets/keymgmt (enterprise): Adds general availability for distributing and managing keys in Azure Key Vault. secrets/openldap: Added dynamic roles to OpenLDAP similar to the combined database engine ] secrets/terraform: New secret engine for managing Terraform Cloud API tokens ] ui: Adds check for feature flag on application, and updates namespace toolbar on login if present ] ui: Adds the wizard to the Database Secret Engine ] ui: Database secrets engine, supporting MongoDB only ] IMPROVEMENTS: agent: Add a `vault.retry` stanza that allows specifying number of retries on failure; this applies both to templating and proxied requests. ] agent: Agent can now run as a Windows service. ] agent: Better concurrent request handling on identical requests proxied through Agent. ] agent: Route templating server through cache when persistent cache is enabled. ] agent: change auto-auth to preload an existing token on start ] auth/approle: Secrets ID generation endpoint now returns `secretidttl` as part of its response. ] auth/ldap: Improve consistency in error messages ] auth/okta: Adds support for Okta Verify TOTP MFA. ] changelog: Add dependencies listed in dependencies/2-25-21 ] command/debug: Now collects logs (at level `trace`) as a periodic output. ] core (enterprise): "vault status" command works when a namespace is set. ] core (enterprise): Update Trial Enterprise license from 30 minutes to 6 hours core/metrics: Added "vault operator usage" command. ] core/metrics: New telemetry metrics reporting lease expirations by time interval and namespace ] core: Added active since timestamp to the status output of active nodes. ] core: Check audit device with a test message before adding it. ] core: Track barrier encryption count and automatically rotate after a large number of operations or on a schedule ] core: add metrics for active entity count ] core: add partial month client count api ] core: dev mode listener allows unauthenticated sys/metrics requests ] core: reduce memory used by leases ] secrets/gcp: Truncate ServiceAccount display names longer than 100 characters. ] storage/raft (enterprise): Listing of peers is now allowed on DR secondary cluster nodes, as an update operation that takes in DR operation token for authenticating the request. transform (enterprise): Improve FPE transformation performance transform (enterprise): Use transactions with batch tokenization operations for improved performance ui: Clarify language on usage metrics page empty state ] ui: Customize MongoDB input fields on Database Secrets Engine ] ui: Upgrade Ember-cli from 3.8 to 3.22. ] ui: Upgrade Storybook from 5.3.19 to 6.1.17. ] ui: Upgrade date-fns from 1.3.0 to 2.16.1. ] ui: Upgrade dependencies to resolve potential JS vulnerabilities ] ui: better errors on Database secrets engine role create ] BUG FIXES: agent: Only set the namespace if the VAULT_NAMESPACE env var isn't present ] agent: Set TokenParent correctly in the Index to be cached. ] agent: Set namespace for template server in agent. ] api/sys/config/ui: Fixes issue where multiple UI custom header values are ignored and only the first given value is used ] api: Fixes CORS API methods that were outdated and invalid ] auth/jwt: Fixes `bound_claims` validation for provider-specific group and user info fetching. ] auth/jwt: Fixes an issue where JWT verification keys weren't updated after a `jwks_url` change. ] auth/jwt: Fixes an issue where `jwtsupportedalgs` were not being validated for JWT auth using `jwksurl` and

] auth/oci: Fixes alias name to use the role name, and not the literal string `name` ] ] consul-template: Update consul-template vendor version and associated dependencies to master, pulling in <https://github.com/hashicorp/consul-template/pull/1447> ] core (enterprise): Limit entropy augmentation during token generation to root tokens. ] core (enterprise): Vault EGP policies attached to path were not correctly scoped to the namespace. core/identity: Fix deadlock in entity merge endpoint. ] core: Avoid disclosing IP addresses in the errors of unauthenticated requests ] core: Fix client.Clone() to include the address ] core: Fix duplicate quotas on performance standby nodes. ] core: Fix rate limit resource quota migration from 1.5.x to 1.6.x by ensuring `purgeInterval` and `staleAge` are set appropriately. ] core: Make all APIs that report init status consistent, and make them report initialized=true when a Raft join is in progress. ] core: Make the response to an unauthenticated request to sys/internal endpoints consistent regardless of mount existence. ] core: Turn off case sensitivity for allowed entity alias check during token create operation. ] http: change maxrequestsize to be unlimited when the config value is less than 0 ] license: Fix license caching issue that prevents new licenses to get picked up by the license manager ] metrics: Protect emitMetrics from panicking during post-seal ] quotas/rate-limit: Fix quotas enforcing old rate limit quota paths ] replication (enterprise): Fix bug with not starting merkle sync while requests are in progress secrets/database/influxdb: Fix issue where not all errors from InfluxDB were being handled ] secrets/database/mysql: Fixes issue where the DisplayName within generated usernames was the incorrect length ] secrets/database: Sanitize `private_key` field when reading database plugin config ] secrets/gcp: Fix issue with account and iam_policy roleset WALs not being removed after attempts when GCP project no longer exists ] secrets/transit: allow for null string to be used for optional parameters in encrypt and decrypt ] serviceregistration: Fix race during shutdown of Consul service registration. ] storage/raft (enterprise): Automated snapshots with Azure required specifying `azureblobenvironment`, which should have had as a default `AZUREPUBLICCLOUD`. storage/raft (enterprise): Reading a non-existent auto snapshot config now returns 404. storage/raft (enterprise): The parameter awss3serverkmskey was misnamed and didn't work. Renamed to awss3kms_key, and make it work so that when provided the given key will be used to encrypt the snapshot using AWS KMS. transform (enterprise): Fix bug tokenization handling metadata on exportable stores transform (enterprise): Fix bug where tokenization store changes are persisted but don't take effect transform (enterprise): Fix transform configuration not handling `stores` parameter on the legacy path transform (enterprise): Make expiration timestamps human readable transform (enterprise): Return false for invalid tokens on the validate endpoint rather than returning an HTTP error ui: Add role from database connection automatically populates the database for new role ] ui: Fix bug in Transform secret engine when a new role is added and then removed from a transformation ] ui: Fix bug that double encodes secret route when there are spaces in the path and makes you unable to view the version history. ] ui: Fix expected response from feature-flags endpoint ] ui: Fix footer URL linking to the correct version changelog. ] DEPRECATIONS: aws/auth: AWS Auth endpoints that use the "whitelist" and "blacklist" terms have been deprecated. Refer to the CHANGES section for additional details. BUG FIXES: core (enterprise): Fix bug where password generation through password policies do not work on namespaces if performed outside a request callback or from an external plugin. ] core (enterprise): Only delete quotas on primary cluster. ] secrets/db: Fix bug where Vault can rotate static role passwords early during start up under certain conditions. ] secrets/openldap: Fix bug where Vault can rotate static role passwords early during start up under certain

] SECURITY: UI Secret Caching: The Vault UI erroneously cached and exposed user-viewed secrets between authenticated sessions in a single shared browser, if the browser window / tab was not refreshed or closed between logout and a subsequent login. This vulnerability, CVE-2021-38554, was fixed in Vault 1.8.0 and will be addressed in pending 1.7.4 / 1.6.6 releases. CHANGES: Alpine: Docker images for Vault 1.6.6+, 1.7.4+, and 1.8.2+ are built with Alpine 3.14, due to CVE-2021-36159 go: Update go version to 1.15.15 ] IMPROVEMENTS: db/cassandra: Added tlsservername to specify server name for TLS validation ] BUG FIXES: physical/raft: Fix safeio.Rename error when restoring snapshots on windows ] secret: fix the bug where transit encrypt batch doesn't work with key_version ] secrets/database: Fixed an issue that prevented external database plugin processes from restarting after a shutdown. ] ui: Automatically refresh the page when user logs out ] ui: Fixes metrics page when read on counter config not allowed ] ui: fix oidc login with Safari ] SECURITY: Non-Expiring Leases: Vault and Vault Enterprise renewed nearly-expiring token leases and dynamic secret leases with a zero-second TTL, causing them to be treated as non-expiring, and never revoked. This issue affects Vault and Vault Enterprise versions 0.10.0 through 1.7.1, and is fixed in 1.5.9, 1.6.5, and 1.7.2 (CVE-2021-32923). CHANGES: agent: Update to use IAM Service Account Credentials endpoint for signing JWTs when using GCP Auto-Auth method ] auth/gcp: Update to v0.8.1 to use IAM Service Account Credentials API for signing JWTs ] BUG FIXES: core (enterprise): Fix plugins mounted in namespaces being unable to use password policies ] core: correct logic for renewal of leases nearing their expiration time. ] secrets/database: Fix marshalling to allow providing numeric arguments to external database plugins. ] secrets/database: Fixes issue for V4 database interface where `SetCredentials` wasn't falling back to using `RotateRootCredentials` if `SetCredentials` is `Unimplemented` ] ui: Fix namespace-bug on login ] SECURITY: The PKI Secrets Engine tidy functionality may cause Vault to exclude revoked-but-unexpired certificates from the Vault CRL. This vulnerability affects Vault and Vault Enterprise 1.5.1 and newer and was fixed in versions 1.5.8, 1.6.4, and 1.7.1. (CVE-2021-27668) The Cassandra Database and Storage backends were not correctly verifying TLS certificates. This issue affects all versions of Vault and Vault Enterprise and was fixed in versions 1.6.4, and 1.7.1. (CVE-2021-27400) CHANGES: go: Update to Go 1.15.11 ] IMPROVEMENTS: command/debug: Now collects logs (at level `trace`) as a periodic output. ] core: Add tlsmaxversion listener config option. ] core: allow arbitrary length stack traces upon receiving SIGUSR2 (was 32MB) ] BUG FIXES: core: Fix cleanup of storage entries from cubbyholes within namespaces. ] core: Fix goroutine leak when updating rate limit quota ] core: Fix storage entry leak when revoking leases created with non-orphan batch tokens. ] pki: Only remove revoked entry for certificates during tidy if they are past their NotAfter value ] pki: Preserve ordering of all DN attribute values when issuing certificates ] replication: Fix: mounts created within a namespace that was part of an Allow filtering rule would not appear on performance secondary if created after rule was defined. secrets/database/cassandra: Fixed issue where hostnames were not being validated when using TLS ] storage/raft: leadertlsservername wasn't used unless leadercacert_file and/or mTLS were configured. ] SECURITY: Limited Unauthenticated License Metadata Read: We addressed a security vulnerability that allowed for the unauthenticated reading of Vault license metadata from DR Secondaries. This vulnerability affects Vault Enterprise and is fixed in 1.6.3

CHANGES: secrets/mongodbatlas: Move from whitelist to access list API ] IMPROVEMENTS: ui: Clarify language on usage metrics page empty state ] BUG FIXES: auth/kubernetes: Cancel API calls to TokenReview endpoint when request context is closed ] core/identity: Fix deadlock in entity merge endpoint. ] quotas: Fix duplicate quotas on performance standby nodes. ] quotas/rate-limit: Fix quotas enforcing old rate limit quota paths ] replication (enterprise): Don't write request count data on DR Secondaries. Fixes DR Secondaries becoming out of sync approximately every 30s. ] secrets/azure (enterprise): Forward service principal credential creation to the primary cluster if called on a performance standby or performance secondary. ] SECURITY: IP Address Disclosure: We fixed a vulnerability where, under some error conditions, Vault would return an error message disclosing internal IP addresses. This vulnerability affects Vault and Vault Enterprise and is fixed in 1.6.2 (CVE-2021-3024). Limited Unauthenticated Remove Peer: As of Vault 1.6, the remove-peer command on DR secondaries did not require authentication. This issue impacts the stability of HA architecture, as a bad actor could remove all standby nodes from a DR secondary. This issue affects Vault Enterprise 1.6.0 and 1.6.1, and is fixed in 1.6.2 (CVE-2021-3282). Mount Path Disclosure: Vault previously returned different HTTP status codes for existent and non-existent mount paths. This behavior would allow unauthenticated brute force attacks to reveal which paths had valid mounts. This issue affects Vault and Vault Enterprise and is fixed in 1.6.2 (CVE-2020-25594). CHANGES: go: Update go version to 1.15.7 ] FEATURES: ui: Adds check for feature flag on application, and updates namespace toolbar on login if present ] IMPROVEMENTS: core (enterprise): "vault status" command works when a namespace is set. ] core: reduce memory used by leases ] storage/raft (enterprise): Listing of peers is now allowed on DR secondary cluster nodes, as an update operation that takes in DR operation token for authenticating the request. core: allow setting tls_servername for raft retry/auto-join ] BUG FIXES: agent: Set namespace for template server in agent. ] core: Make the response to an unauthenticated request to sys/internal endpoints consistent regardless of mount existence. ] metrics: Protect emitMetrics from panicking during post-seal ] secrets/gcp: Fix issue with account and iam_policy roleset WALs not being removed after attempts when GCP project no longer exists ] storage/raft (enterprise): Automated snapshots with Azure required specifying `azureblobenvironment`, which should have had as a default `AZUREPUBLICCLOUD`. storage/raft (enterprise): Autosnapshots config and storage weren't excluded from performance replication, causing conflicts and errors. ui: Fix bug that double encodes secret route when there are spaces in the path and makes you unable to view the version history. ] ui: Fix expected response from feature-flags endpoint ] SECURITY: LDAP Auth Method: We addressed an issue where error messages returned by the LDAP auth method allowed user enumeration ]. This vulnerability affects Vault OSS and Vault Enterprise and is fixed in 1.5.6 and 1.6.1 (CVE-2020-35177). Sentinel EGP: We've fixed incorrect handling of namespace paths to prevent users within namespaces from applying Sentinel EGP policies to paths above their namespace. This vulnerability affects Vault Enterprise and is fixed in 1.5.6 and 1.6.1 (CVE-2020-35453). IMPROVEMENTS: auth/ldap: Improve consistency in error messages ] core/metrics: Added "vault operator usage" command. ] secrets/gcp: Truncate ServiceAccount display names longer than 100 characters. ] BUG FIXES: agent: Only set the namespace if the VAULT_NAMESPACE env var isn't present ] auth/jwt: Fixes `bound_claims` validation for provider-specific group and user info fetching. ] core (enterprise): Vault EGP policies attached to path were not correctly scoped to the namespace. core: Avoid deadlocks by ensuring that if grabLockOrStop returns stopped=true, the lock will not be

] core: Fix client.Clone() to include the address ] core: Fix rate limit resource quota migration from 1.5.x to 1.6.x by ensuring `purgeInterval` and `staleAge` are set appropriately. ] core: Make all APIs that report init status consistent, and make them report initialized=true when a Raft join is in progress. ] secrets/database/influxdb: Fix issue where not all errors from InfluxDB were being handled ] secrets/database/mysql: Fixes issue where the DisplayName within generated usernames was the incorrect length ] secrets/database: Sanitize `private_key` field when reading database plugin config ] secrets/transit: allow for null string to be used for optional parameters in encrypt and decrypt ] storage/raft (enterprise): The parameter awss3serverkmskey was misnamed and didn't work. Renamed to awss3kms_key, and make it work so that when provided the given key will be used to encrypt the snapshot using AWS KMS. transform (enterprise): Fix bug tokenization handling metadata on exportable stores transform (enterprise): Fix transform configuration not handling `stores` parameter on the legacy path transform (enterprise): Make expiration timestamps human readable transform (enterprise): Return false for invalid tokens on the validate endpoint rather than returning an HTTP error transform (enterprise): Fix bug where tokenization store changes are persisted but don't take effect ui: Fix bug in Transform secret engine when a new role is added and then removed from a transformation ] ui: Fix footer URL linking to the correct version changelog. ] ui: Fox radio click on secrets and auth list pages. ] NOTE: Binaries for 32-bit macOS (i.e. the `darwin_386` build) will no longer be published. This target was dropped in the latest version of the Go compiler. CHANGES: agent: Agent now properly returns a non-zero exit code on error, such as one due to template rendering failure. Using `erroronmissing_key` in the template config will cause agent to immediately exit on failure. In order to make agent properly exit due to continuous failure from template rendering errors, the old behavior of indefinitely restarting the template server is now changed to exit once the default retry attempt of 12 times (with exponential backoff) gets exhausted. ] token: Periodic tokens generated by auth methods will have the period value stored in its token entry. ] core: New telemetry metrics reporting mount table size and number of entries ] go: Updated Go version to 1.15.4 ] FEATURES: Couchbase Secrets*: Vault can now manage static and dynamic credentials for Couchbase. ] Expanded Password Policy Support*: Custom password policies are now supported for all database engines. Integrated Storage Auto Snapshots (Enterprise)*: This feature enables an operator to schedule snapshots of the integrated storage backend and ensure those snapshots are persisted elsewhere. Integrated Storage Cloud Auto Join*: This feature for integrated storage enables Vault nodes running in the cloud to automatically discover and join a Vault cluster via operator-supplied metadata. Key Management Secrets Engine (Enterprise; Tech Preview)*: This new secret engine allows securely distributing and managing keys to Azure cloud KMS services. Seal Migration*: With Vault 1.6, we will support migrating from an auto unseal mechanism to a different mechanism of the same type. For example, if you were using an AWS KMS key to automatically unseal, you can now migrate to a different AWS KMS key. Tokenization (Enterprise; Tech Preview)*: Tokenization supports creating irreversible tokens from sensitive data. Tokens can be used in less secure environments, protecting the original data. Vault Client Count*: Vault now counts the number of active entities (and non-entity tokens) per month and makes this information available via the "Metrics" section of the

IMPROVEMENTS: auth/approle: Role names can now be referenced in templated policies through the `approle.metadata.role_name` property ] auth/aws: Improve logic check on wildcard `BoundIamPrincipalARNs` and include role name on error messages on check failure ] auth/jwt: Add support for fetching groups and user information from G Suite during authentication. ] auth/jwt: Adding EdDSA (ed25519) to supported algorithms ] auth/jwt: Improve cli authorization error ] auth/jwt: Add OIDC namespaceinstate option ] secrets/transit: fix missing plaintext in bulk decrypt response ] command/server: Delay informational messages in -dev mode until logs have settled. ] command/server: Add environment variable support for `disable_mlock`. ] core/metrics: Add metrics for storage cache ] core/metrics: Add metrics for leader status ] physical/azure: Add the ability to use Azure Instance Metadata Service to set the credentials for Azure Blob storage on the backend. ] sdk/framework: Add a time type for API fields. ] secrets/database: Added support for password policies to all databases , ] secrets/database/cassandra: Added support for static credential rotation ] secrets/database/elasticsearch: Added support for static credential rotation ] secrets/database/hanadb: Added support for root credential & static credential rotation ] secrets/database/hanadb: Default password generation now includes dashes. Custom statements may need to be updated to include quotes around the password field ] secrets/database/influxdb: Added support for static credential rotation ] secrets/database/mongodbatlas: Added support for root credential rotation ] secrets/database/mongodbatlas: Support scopes field in creations statements for MongoDB Atlas database plugin ] seal/awskms: Add logging during awskms auto-unseal ] storage/azure: Update SDK library to use since previous library has been deprecated. ] secrets/ad: `rotate-root` now supports POST requests like other secret engines ] ui: Add ui functionality for the Transform Secret Engine ] ui: Pricing metrics dashboard ] BUG FIXES: auth/jwt: Fix bug preventing config edit UI from rendering ] cli: Don't open or overwrite a raft snapshot file on an unsuccessful `vault operator raft snapshot` ] core: Implement constant time version of shamir GF(2^8) math ] core: Fix resource leak in plugin API (plugin-dependent, not all plugins impacted) ] core: Fix race involved in enabling certain features via a license change core: Fix error handling in HCL parsing of objects with invalid syntax ] identity: Check for timeouts in entity API ] secrets/database: Fix handling of TLS options in mongodb connection strings ] secrets/gcp: Ensure that the IAM policy version is appropriately set after a roleset's bindings have changed. ] ui: Mask LDAP bindpass while typing ] ui: Update language in promote dr modal flow ] ui: Update language on replication primary dashboard for clarity ] core: Fix bug where updating an existing path quota could introduce a conflict. ] SECURITY: Non-Expiring Leases: Vault and Vault Enterprise renewed nearly-expiring token leases and dynamic secret leases with a zero-second TTL, causing them to be treated as non-expiring, and never revoked. This issue affects Vault and Vault Enterprise versions 0.10.0 through 1.7.1, and is fixed in 1.5.9, 1.6.5, and 1.7.2 (CVE-2021-32923). CHANGES: agent: Update to use IAM Service Account Credentials endpoint for signing JWTs when using GCP Auto-Auth method ] auth/gcp: Update to v0.7.2 to use IAM Service Account Credentials API for signing JWTs ] BUG FIXES: core: correct logic for renewal of leases nearing their expiration time. ] SECURITY: The PKI Secrets Engine tidy functionality may cause Vault to exclude revoked-but-unexpired certificates from the Vault CRL. This vulnerability affects Vault and Vault Enterprise 1.5.1 and newer and was fixed in versions 1.5.8, 1.6.4, and 1.7.1. (CVE-2021-27668) CHANGES: go: Update to Go 1.14.15 ] IMPROVEMENTS: core: Add tlsmaxversion listener config option. ] BUG FIXES: core/identity: Fix deadlock in entity merge

] core: Fix cleanup of storage entries from cubbyholes within namespaces. ] pki: Only remove revoked entry for certificates during tidy if they are past their NotAfter value ] core: Avoid deadlocks by ensuring that if grabLockOrStop returns stopped=true, the lock will not be held. ] SECURITY: IP Address Disclosure: We fixed a vulnerability where, under some error conditions, Vault would return an error message disclosing internal IP addresses. This vulnerability affects Vault and Vault Enterprise and is fixed in 1.6.2 and 1.5.7 (CVE-2021-3024). Mount Path Disclosure: Vault previously returned different HTTP status codes for existent and non-existent mount paths. This behavior would allow unauthenticated brute force attacks to reveal which paths had valid mounts. This issue affects Vault and Vault Enterprise and is fixed in 1.6.2 and 1.5.7 (CVE-2020-25594). IMPROVEMENTS: storage/raft (enterprise): Listing of peers is now allowed on DR secondary cluster nodes, as an update operation that takes in DR operation token for authenticating the request. BUG FIXES: core: Avoid disclosing IP addresses in the errors of unauthenticated requests ] core: Make the response to an unauthenticated request to sys/internal endpoints consistent regardless of mount existence. ] SECURITY: LDAP Auth Method: We addressed an issue where error messages returned by the LDAP auth method allowed user enumeration ]. This vulnerability affects Vault OSS and Vault Enterprise and is fixed in 1.5.6 and 1.6.1 (CVE-2020-35177). Sentinel EGP: We've fixed incorrect handling of namespace paths to prevent users within namespaces from applying Sentinel EGP policies to paths above their namespace. This vulnerability affects Vault Enterprise and is fixed in 1.5.6 and 1.6.1. IMPROVEMENTS: auth/ldap: Improve consistency in error messages ] BUG FIXES: core (enterprise): Vault EGP policies attached to path were not correctly scoped to the namespace. core: Fix bug where updating an existing path quota could introduce a conflict ] core: Fix client.Clone() to include the address ] quotas (enterprise): Reset cache before loading quotas in the db during startup secrets/transit: allow for null string to be used for optional parameters in encrypt and decrypt ] IMPROVEMENTS: auth/aws, core/seal, secret/aws: Set default IMDS timeouts to match AWS SDK ] BUG FIXES: auth/aws: Restrict region selection when in the aws-us-gov partition to avoid IAM errors ] core (enterprise): Allow operators to add and remove (Raft) peers in a DR secondary cluster using Integrated Storage. core (enterprise): Add DR operation token to the remove peer API and CLI command (when DR secondary). core (enterprise): Fix deadlock in handling EGP policies core (enterprise): Fix extraneous error messages in DR Cluster secrets/mysql: Conditionally overwrite TLS parameters for MySQL secrets engine ] secrets/ad: Fix bug where `password_policy` setting was not using correct key when `ad/config` was read ] ui: Fix issue with listing roles and methods on the same auth methods with different names ] SECURITY: Batch Token Expiry: We addressed an issue where batch token leases could outlive their TTL because we were not scheduling the expiration time correctly. This vulnerability affects Vault OSS and Vault Enterprise 1.0 and newer and is fixed in 1.4.7 and 1.5.4 (CVE-2020-25816). IMPROVEMENTS: secrets/pki: Handle expiration of a cert not in storage as a success ] auth/kubernetes: Add an option to disable defaulting to the local CA cert and service account JWT when running in a Kubernetes pod secrets/gcp: Add check for 403 during rollback to prevent repeated deletion calls ] core: Disable usage metrics collection on performance standby nodes. ] credential/aws: Added X-Amz-Content-Sha256 as a default STS request header ] BUG FIXES: agent: Fix `disablefastnegotiation` not being set on the auth method when configured by

] core (enterprise): Fix hang when cluster-wide plugin reload cleanup is slow on unseal core (enterprise): Fix an error in cluster-wide plugin reload cleanup following such a reload core: Fix crash when metrics collection encounters zero-length keys in KV store ] mfa (enterprise): Fix incorrect handling of PingID responses that could result in auth requests failing replication (enterprise): Improve race condition when using a newly created token on a performance standby node replication (enterprise): Only write failover cluster addresses if they've changed ui: fix bug where dropdown for identity/entity management is not reflective of actual policy ] NOTE: All security content from 1.5.2, 1.5.1, 1.4.5, 1.4.4, 1.3.9, 1.3.8, 1.2.6, and 1.2.5 has been made fully open source, and the git tags for 1.5.3, 1.4.6, 1.3.10, and 1.2.7 will build correctly for open source users. BUG FIXES: auth/aws: Made header handling for IAM authentication more robust secrets/ssh: Fixed a bug with role option for SSH signing algorithm to allow more than RSA signing NOTE: Includes correct license in the HSM binary. NOTE: OSS binaries of 1.5.1, 1.4.4, 1.3.8, and 1.2.5 were built without the Vault UI. Enterprise binaries are not affected. KNOWN ISSUES: AWS IAM logins may return an error depending on the headers sent with the request. For more details and a workaround, see the In versions 1.2.6, 1.3.9, 1.4.5, and 1.5.2, enterprise licenses on the HSM build were not incorporated correctly - enterprise customers should use 1.2.6.1, 1.3.9.1, 1.4.5.1, and 1.5.2.1. SECURITY: When using the IAM AWS Auth Method, under certain circumstances, values Vault uses to validate identities and roles can be manipulated and bypassed. This vulnerability affects Vault and Vault Enterprise 0.7.1 and newer and is fixed in 1.2.5, 1.3.8, 1.4.4, and 1.5.1 (CVE-2020-16250) (Discovered by Felix Wilhelm of Google Project Zero) When using the GCP GCE Auth Method, under certain circumstances, values Vault uses to validate GCE VMs can be manipulated and bypassed. This vulnerability affects Vault and Vault Enterprise 0.8.3 and newer and is fixed in 1.2.5, 1.3.8, 1.4.4, and 1.5.1 (CVE-2020-16251) (Discovered by Felix Wilhelm of Google Project Zero) When using Vault Agent with cert auto-auth and caching enabled, under certain circumstances, clients without permission to access agent's token may retrieve the token without login credentials. This vulnerability affects Vault Agent 1.1.0 and newer and is fixed in 1.5.1 (CVE-2020-17455) KNOWN ISSUES: OSS binaries of 1.5.1, 1.4.4, 1.3.8, and 1.2.5 were built without the Vault UI. Enterprise binaries are not affected. AWS IAM logins may return an error depending on the headers sent with the request. For more details and a workaround, see the CHANGES: pki: The tidy operation will now remove revoked certificates if the parameter `tidyrevokedcerts` is set to `true`. This will result in certificate entries being immediately removed, as opposed to awaiting until its NotAfter time. Note that this only affects certificates that have been already revoked. ] go: Updated Go version to 1.14.7 IMPROVEMENTS: auth/jwt: Add support for fetching groups and user information from G Suite during authentication. ] auth/jwt: Add EdDSA to supported algorithms. ] secrets/openldap: Add "ad" schema that allows the engine to correctly rotate AD passwords. ] pki: Add a `alloweddomainstemplate` parameter that enables the use of identity templating within the `allowed_domains` parameter. ] secret/azure: Use write-ahead-logs to cleanup any orphaned Service Principals ] ui: Wrap TTL option on transit engine export action is updated to a new component. ] ui: Wrap Tool uses newest version of TTL Picker

] BUG FIXES: secrets/gcp: Ensure that the IAM policy version is appropriately set after a roleset's bindings have changed. ] replication (enterprise): Fix status API output incorrectly stating replication is in `idle` state. replication (enterprise): Use PrimaryClusterAddr if it's been set core: Fix panic when printing over-long info fields at startup ] core: Seal migration using the new minimal-downtime strategy didn't work properly with performance standbys. ] core: Vault failed to start when there were non-string values in seal configuration ] core: Handle a trailing slash in the API address used for enabling replication CHANGES: audit: Token TTL and issue time are now provided in the auth portion of audit logs. ] auth/gcp: Changes the default name of the entity alias that gets created to be the role ID for both IAM and GCE authentication. ] core: Remove the addition of newlines to parsed configuration when using integer/boolean values ] cubbyhole: Reject reads and writes to an empty ("") path. ] secrets/azure: Default password generation changed from uuid to cryptographically secure randomized string ] storage/gcs: The `credentialsfile` config option has been removed. The `GOOGLEAPPLICATION_CREDENTIALS` environment variable or default credentials may be used instead ] storage/raft: The storage configuration now accepts a new `maxentrysize` config that will limit the total size in bytes of any entry committed via raft. It defaults to `"1048576"` (1MiB). ] token: Token creation with custom token ID via `id` will no longer allow periods (`.`) as part of the input string. The final generated token value may contain periods, such as the `s.` prefix for service token indication. ] token: Token renewals will now return token policies within the `tokenpolicies` , identity policies within `identitypolicies`, and the full policy set within `policies`. ] go: Updated Go version to 1.14.4 FEATURES: Monitoring*: We have released a Splunk App [9] for Enterprise customers. The app is accompanied by an updated monitoring guide and a few new metrics to enable OSS users to effectively monitor Vault. Password Policies*: Allows operators to customize how passwords are generated for select secret engines (OpenLDAP, Active Directory, Azure, and RabbitMQ). Replication UI Improvements*: We have redesigned the replication UI to highlight the state and relationship between primaries and secondaries and improved management workflows, enabling a more holistic understanding of multiple Vault clusters. Resource Quotas*: As of 1.5, Vault supports specifying a quota to rate limit requests on OSS and Enterprise. Enterprise customers also have access to set quotas on the number of leases that can be generated on a path. OpenShift Support*: We have updated the Helm charts to allow users to install Vault onto their OpenShift clusters. Seal Migration*: We have made updates to allow migrations from auto unseal to Shamir unseal on Enterprise. AWS Auth Web Identity Support*: We've added support for AWS Web Identities, which will be used in the credentials chain if present. Vault Monitor*: Similar to the monitor command for Consul and Nomad, we have added the ability for Vault to stream logs from other Vault servers at varying log levels. AWS Secrets Groups Support*: IAM users generated by Vault may now be added to IAM Groups. Integrated Storage as HA Storage*: In Vault 1.5, it is possible to use Integrated Storage as HA Storage with a different storage backend as regular storage. OIDC Auth Provider Extensions*: We've added support to OIDC Auth to incorporate IdP-specific extensions. Currently this includes expanded Azure AD groups support. GCP Secrets*: Support BigQuery dataset ACLs in absence of IAM endpoints. KMIP*: Add support for signing client certificates requests (CSRs) rather than having them be generated entirely within

IMPROVEMENTS: audit: Replication status requests are no longer audited. ] audit: Added mount_type field to requests and responses. ] auth/aws: Add support for Web Identity credentials ] auth/jwt: Support users that are members of more than 200 groups on Azure ] auth/kerberos: Support identities without userPrincipalName ] auth/kubernetes: Allow disabling `iss` validation ] auth/kubernetes: Try reading the ca.crt and TokenReviewer JWT from the default service account ] cli: Support reading TLS parameters from file for the `vault operator raft join` command. ] cli: Add a new subcommand, `vault monitor`, for tailing server logs in the console. ] core: Add the Go version used to build a Vault binary to the server message output. ] core: Added Password Policies for user-configurable password generation ] core: New telemetry metrics covering token counts, token creation, KV secret counts, lease creation. ] ] ] ] physical/gcs: The storage backend now uses a dedicated client for HA lock updates to prevent lock table update failures when flooded by other client requests. ] physical/spanner: The storage backend now uses a dedicated client for HA lock updates to prevent lock table update failures when flooded by other client requests. ] plugin: Add SDK method, `Sys.ReloadPlugin`, and CLI command, `vault plugin reload`, for reloading plugins. ] plugin (enterprise): Add a scope field to plugin reload, which when global, reloads the plugin anywhere in a cluster. ] sdk/framework: Support accepting TypeFloat parameters over the API ] secrets/aws: Add iam_groups parameter to role create/update ] secrets/database: Add static role rotation for MongoDB Atlas database plugin ] secrets/database: Add static role rotation for MSSQL database plugin ] secrets/database: Allow InfluxDB to use insecure TLS without cert bundle ] secrets/gcp: Support BigQuery dataset ACLs in absence of IAM endpoints ] secrets/pki: Allow 3072-bit RSA keys ] secrets/ssh: Add a CA-mode role option to specify signing algorithm ] secrets/ssh: The can now be configured to reference a mount in a namespace ] secrets/transit: Transit requests that make use of keys now include a new field `key_version` in their responses ] secrets/transit: Improving transit batch encrypt and decrypt latencies ] sentinel: Add a sentinel config section, and "additionalenabledmodules", a list of Sentinel modules that may be imported in addition to the defaults. ui: Update TTL picker styling on SSH secret engine ] ui: Only render the JWT input field of the Vault login form on mounts configured for JWT auth ] ui: Add replication dashboards. Improve replication management workflows. . ui: Update alert banners to match design systems black text. . BUG FIXES: auth/oci: Fix issue where users of the Oracle Cloud Infrastructure (OCI) auth method could not authenticate when the plugin backend was mounted at a non-default path. ] core: Extend replicated cubbyhole fix in 1.4.0 to cover case where a performance primary is also a DR primary ] replication (enterprise): Use the PrimaryClusterAddr if it's been set seal/awskms: fix AWS KMS auto-unseal when AWSROLESESSION_NAME not set ] sentinel: fix panic due to concurrent map access when rules iterate over metadata maps secrets/aws: Fix issue where performance standbys weren't able to generate STS credentials after an IAM access key rotation in AWS and root IAM credential update in Vault ] secrets/database: Fix issue where rotating root database credentials while Vault's storage backend is unavailable causes Vault to lose access to the database ] secrets/database: Fix issue that prevents performance standbys from connecting to databases after a root credential rotation ] secrets/database: Fix parsing of multi-line PostgreSQL statements ] secrets/gcp: Fix issue were updates were not being applied to the `token_scopes` of a

] secrets/kv: Return the value of deleteversionafter when reading kv/config, even if it is set to the default. ] ui: Add Toggle component into core addon so it is available in KMIP and other Ember Engines. ui: Disallow max versions value of large than 9999999999999999 on kv2 secrets engine. ] ui: Add and upgrade missing dependencies to resolve a failure with `make static-dist`. ] BUG FIXES: replication (enterprise): Fix panic when old filter path evaluation fails SECURITY: Batch Token Expiry: We addressed an issue where batch token leases could outlive their TTL because we were not scheduling the expiration time correctly. This vulnerability affects Vault OSS and Vault Enterprise 1.0 and newer and is fixed in 1.4.7 and 1.5.4 (CVE-2020-25816). IMPROVEMENTS: secret/azure: Use write-ahead-logs to cleanup any orphaned Service Principals ] BUG FIXES: replication (enterprise): Don't stop replication if old filter path evaluation fails NOTE: All security content from 1.5.2, 1.5.1, 1.4.5, 1.4.4, 1.3.9, 1.3.8, 1.2.6, and 1.2.5 has been made fully open source, and the git tags for 1.5.3, 1.4.6, 1.3.10, and 1.2.7 will build correctly for open source users. BUG FIXES: auth/aws: Made header handling for IAM authentication more robust secrets/ssh: Fixed a bug with role option for SSH signing algorithm to allow more than RSA signing ] NOTE: Includes correct license in the HSM binary. NOTE: OSS binaries of 1.5.1, 1.4.4, 1.3.8, and 1.2.5 were built without the Vault UI. Enterprise binaries are not affected. KNOWN ISSUES: AWS IAM logins may return an error depending on the headers sent with the request. For more details and a workaround, see the In versions 1.2.6, 1.3.9, 1.4.5, and 1.5.2, enterprise licenses on the HSM build were not incorporated correctly - enterprise customers should use 1.2.6.1, 1.3.9.1, 1.4.5.1, and 1.5.2.1. SECURITY: When using the IAM AWS Auth Method, under certain circumstances, values Vault uses to validate identities and roles can be manipulated and bypassed. This vulnerability affects Vault and Vault Enterprise 0.7.1 and newer and is fixed in 1.2.5, 1.3.8, 1.4.4, and 1.5.1 (CVE-2020-16250) (Discovered by Felix Wilhelm of Google Project Zero) When using the GCP GCE Auth Method, under certain circumstances, values Vault uses to validate GCE VMs can be manipulated and bypassed. This vulnerability affects Vault and Vault Enterprise 0.8.3 and newer and is fixed in 1.2.5, 1.3.8, 1.4.4, and 1.5.1 (CVE-2020-16251) (Discovered by Felix Wilhelm of Google Project Zero) KNOWN ISSUES: OSS binaries of 1.5.1, 1.4.4, 1.3.8, and 1.2.5 were built without the Vault UI. Enterprise binaries are not affected. AWS IAM logins may return an error depending on the headers sent with the request. For more details and a workaround, see the BUG FIXES: auth/okta: fix bug introduced in 1.4.0: only 200 external groups were fetched even if user belonged to more ] seal/awskms: fix AWS KMS auto-unseal when AWSROLESESSION_NAME not set ] secrets/aws: Fix possible issue creating access keys when using Performance Standbys ] IMPROVEMENTS: auth/aws: Retry on transient failures during AWS IAM auth login attempts ] ui: Add transit key algorithms aes128-gcm96, ecdsa-p384, ecdsa-p521 to the UI. ] & ] IMPROVEMENTS: auth/aws: Add support for Web Identity credentials ] auth/kerberos: Support identities without userPrincipalName ] core: Add the Go version used to build a Vault binary to the server message

] secrets/database: Add static role rotation for MongoDB Atlas database plugin ] physical/mysql: Require TLS or plaintext flagging in MySQL configuration ] ui: Link to the Vault Changelog in the UI footer ] BUG FIXES: agent: Restart template server when it shuts down ] auth/oci: Fix issue where users of the Oracle Cloud Infrastructure (OCI) auth method could not authenticate when the plugin backend was mounted at a non-default path. ] replication: The issue causing cubbyholes in namespaces on performance secondaries to not work, which was fixed in 1.4.0, was still an issue when the primary was both a performance primary and DR primary. seal: (enterprise) Fix issue causing stored seal and recovery keys to be mistaken as sealwrapped values secrets/aws: Fix issue where performance standbys weren't able to generate STS credentials after an IAM access key rotation in AWS and root IAM credential update in Vault ] secrets/database: Fix issue that prevents performance standbys from connecting to databases after a root credential rotation ] secrets/gcp: Fix issue were updates were not being applied to the `token_scopes` of a roleset. ] SECURITY: core: Proxy environment variables are now redacted before being logged, in case the URLs include a username:password. This vulnerability, CVE-2020-13223, is fixed in 1.3.6 and 1.4.2, but affects 1.4.0 and 1.4.1, as well as older versions of Vault ] secrets/gcp: Fix a regression in 1.4.0 where the system TTLs were being used instead of the configured backend TTLs for dynamic service accounts. This vulnerability is CVE-2020-12757. ] IMPROVEMENTS: storage/raft: The storage stanza now accepts `leadercacertfile`, `leaderclientcertfile`, and `leaderclientkey_file` parameters to read and parse TLS certificate information from paths on disk. Existing non-path based parameters will continue to work, but their values will need to be provided as a single-line string with newlines delimited by `\n`. ] storage/raft: The `vault status` CLI command and the `sys/leader` API now contain the committed and applied raft indexes. ] BUG FIXES: auth/aws: Fix token renewal issues caused by the metadata changes in 1.4.1 ] auth/ldap: Fix 1.4.0 regression that could result in auth failures when LDAP auth config includes upndomain. ] secrets/ad: Forward rotation requests from standbys to active clusters ] secrets/database: Prevent generation of usernames that are not allowed by the MongoDB Atlas API ] secrets/database: Return an error if a manual rotation of static account credentials fails ] secrets/openldap: Forward all rotation requests from standbys to active clusters ] secrets/transform (enterprise): Fix panic that could occur when accessing cached template entries, such as a requests that accessed templates directly or indirectly from a performance standby node. serviceregistration: Fix a regression for Consul service registration that ignored using the listener address as the redirect address unless api_addr was provided. It now properly uses the same redirect address as the one used by Vault's Core object. ] storage/raft: Advertise the configured cluster address to the rest of the nodes in the raft cluster. This fixes an issue where a node advertising 0.0.0.0 is not using a unique hostname. ] storage/raft: Fix panic when multiple nodes attempt to join the cluster at once. ] sys: The path provided in `sys/internal/ui/mounts/:path` is now namespace-aware. This fixes an issue with `vault kv` subcommands that had namespaces provided in the path returning permission denied all the time. ] ui: Fix snowman that appears when namespaces have more than one period ] CHANGES: auth/aws: The default set of metadata fields added in 1.4.1 has been changed to `accountid` and `authtype` ] storage/raft: Disallow `ha_storage` to be specified if `raft` is set as the `storage`

] IMPROVEMENTS: auth/aws: The set of metadata stored during login is now configurable ] auth/aws: Improve region selection to avoid errors seen if the account hasn't enabled some newer AWS regions ] auth/azure: Enable login from Azure VMs with user-assigned identities ] auth/gcp: The set of metadata stored during login is now configurable ] auth/gcp: The type of alias name used during login is now configurable ] auth/ldap: Improve error messages during LDAP operation failures ] identity: Add a batch delete API for identity entities identity: Improve performance of logins when no group updates are needed metrics: Add `vault.identity.num_entities` metric secrets/kv: Allow `delete-version-after` to be reset to 0 via the CLI ] secrets/rabbitmq: Improve error handling and reporting ] ui: Provide One Time Password during Operation Token generation process BUG FIXES: auth/okta: Fix MFA regression (introduced in ) from 1.4.0 ] auth/userpass: Fix upgrade value for `tokenboundcidrs` being ignored due to incorrect key provided ] config/seal: Fix segfault when seal block is removed ] core: Fix an issue where users attempting to build Vault could receive Go module checksum errors ] core: Fix blocked requests if a SIGHUP is issued during a long-running request has the state lock held. Also fixes deadlock that can happen if `vault debug` with the config target is ran during this time. ] core: Always rewrite the .vault-token file as part of a `vault login` to ensure permissions and ownership are set correctly ] database/mongodb: Fix context deadline error that may result due to retry attempts on failed commands ] http: Fix superflous call messages from the http package on logs caused by missing returns after `respondError` calls ] namespace (enterprise): Fix namespace listing to return `key_info` when a scoping namespace is also provided. seal/gcpkms: Fix panic that could occur if all seal parameters were provided via environment variables ] storage/raft: Fix memory allocation and incorrect metadata tracking issues with snapshots ] storage/raft: Fix panic that could occur if `disable_clustering` was set to true on Raft storage cluster ] storage/raft: Handle errors returned from the API during snapshot operations ] sys/wrapping: Allow unwrapping of wrapping tokens which contain nil data ] CHANGES: cli: The raft configuration command has been renamed to list-peers to avoid confusion. FEATURES: Kerberos Authentication*: Vault now supports Kerberos authentication using a SPNEGO token. Login can be performed using the Vault CLI, API, or agent. Kubernetes Service Discovery*: A new Kubernetes service discovery feature where, if configured, Vault will tag Vault pods with their current health status. For more, see . MongoDB Atlas Secrets*: Vault can now generate dynamic credentials for both MongoDB Atlas databases as well as the . OpenLDAP Secrets Engine*: We now support password management of existing OpenLDAP user entries. For more, see . Redshift Database Secrets Engine*: The database secrets engine now supports static and dynamic secrets for the Amazon Web Services (AWS) Redshift service. Service Registration Config*: A newly introduced `service_registration` configuration stanza, that allows for service registration to be configured separately from the storage backend. For more, see . Transform Secrets Engine (Enterprise)*: A new secrets engine that handles secure data transformations against provided input values. Integrated Storage*: Promoted out of beta and into general availability for both open-source and enterprise workloads. IMPROVEMENTS: agent: add option to force the use of the auth-auth token, and ignore the Vault token in the request ] api: Restore and fix DNS SRV Lookup ] audit: HMAC httprawbody in audit log; this ensures that large authenticated Prometheus metrics responses get replaced with short HMAC values ] audit: Generate-root, generate-recovery-token, and generate-dr-operation-token requests and responses are now

] auth/aws: Reduce the number of simultaneous STS client credentials needed ] auth/azure: subscription ID, resource group, vm and vmss names are now stored in alias metadata ] auth/jwt: Additional OIDC callback parameters available for CLI logins & ] auth/jwt: Bound claims may be optionally configured using globs ] auth/jwt: Timeout during OIDC CLI login if process doesn't complete within 2 minutes ] auth/jwt: Add support for the `form_post` response mode ] auth/jwt: add optional client_nonce to authorization flow ] auth/okta: Upgrade okta sdk lib, which should improve handling of groups ] aws: Add support for v2 of the instance metadata service (see for all linked PRs) core: Separate out service discovery interface from storage interface to allow new types of service discovery not coupled to storage ] core: Add support for telemetry option `metrics_prefix` ] core: Entropy Augmentation can now be used with AWS KMS and Vault Transit seals core: Allow tlsminversion to be set to TLS 1.3 ] cli: Incorrect TLS configuration will now correctly fail ] identity: Allow specifying a custom `client_id` for identity tokens ] metrics/prometheus: improve performance with high volume of metrics updates ] replication (enterprise): Fix race condition causing clusters with high throughput writes to sometimes fail to enter streaming-wal mode replication (enterprise): Secondary clusters can now perform an extra gRPC call to all nodes in a primary cluster in an attempt to resolve the active node's address replication (enterprise): The replication status API now outputs `lastperformancewal`, `lastdrwal`, and `connection_state` values replication (enterprise): DR secondary clusters can now be recovered by the `replication/dr/secondary/recover` API replication (enterprise): We now allow for an alternate means to create a Disaster Recovery token, by using a batch token that is created with an ACL that allows for access to one or more of the DR

secrets/database/mongodb: Switched internal MongoDB driver to mongo-driver ] secrets/database/mongodb: Add support for x509 client authorization to MongoDB ] secrets/database/oracle: Add support for static credential rotation ] secrets/consul: Add support to specify TLS options per Consul backend ] secrets/gcp: Allow specifying the TTL for a service key ] secrets/gcp: Add support for rotating root keys ] secrets/gcp: Handle version 3 policies for Resource Manager IAM requests ] secrets/nomad: Add support to specify TLS options per Nomad backend ] secrets/ssh: Allowed users can now be templated with identity information ] secrets/transit: Adding RSA3072 key support ] storage/consul: Vault returns now a more descriptive error message when only a client cert or a client key has been provided storage/raft: Nodes in the raft cluster can all be given possible leader addresses for them to continuously try and join one of them, thus automating the process of join to a greater extent ] storage/raft: Fix a potential deadlock that could occur on leadership transition ] storage/raft: Refresh TLS keyring on snapshot restore ] storage/etcd: Bumped etcd client API SDK & & & ] ui: Make Transit Key actions more prominent ] ui: Add Core Usage Metrics ] ui: Add refresh Namespace list on the Namespace dropdown, and redesign of Namespace dropdown menu ] ui: Update transit actions to codeblocks & automatically encode plaintext unless indicated ] ui: Display the results of transit key actions in a modal window ] ui: Transit key version styling updates & ability to copy key from dropdown ] BUG FIXES: agent: Fix issue where TLS options are ignored for agent template feature ] auth/jwt: Use lower case role names for `default_role` to match the `role` case convention ] auth/ldap: Fix a bug where the UPNDOMAIN parameter was wrongly used to lookup the group membership of the given user cli: Support autocompletion for nested mounts ] cli: Fix CLI namespace autocompletion ] identity: Fix incorrect caching of identity token JWKS responses ] metrics/stackdriver: Fix issue that prevents the stackdriver metrics library to create unnecessary stackdriver descriptors ] replication (enterprise): Fix issue causing cubbyholes in namespaces on performance secondaries to not work. replication (enterprise): Unmounting a dynamic secrets backend could sometimes lead to replication errors. Change the order of operations to prevent that. seal (enterprise): Fix seal migration when transactional seal wrap backend is in use. secrets/database/influxdb: Fix potential panic if connection to the InfluxDB database cannot be established ] secrets/database/mysql: Ensures default static credential rotation statements are used ] secrets/database/mysql: Fix inconsistent query parameter names: {{name}} or {{username}} for different queries. Now it allows for either for backwards compatibility ] secrets/database/postgres: Fix inconsistent query parameter names: {{name}} or {{username}} for different queries. Now it allows for either for backwards compatibility ] secrets/pki: Support FQDNs in DNS Name ] storage/raft: Allow seal migration to be performed on Vault clusters using raft storage ] telemetry: Prometheus requests on standby nodes will now return an error instead of forwarding the request to the active node ] ui: Fix broken popup menu on the transit secrets list page ] ui: Update headless Chrome flag to fix `yarn run test:oss` ] ui: Update CLI to accept empty strings as param value to reset previously-set values ui: Fix bug where error states don't clear when moving between action tabs on Transit ] NOTE: All security content from 1.5.2, 1.5.1, 1.4.5, 1.4.4, 1.3.9, 1.3.8, 1.2.6, and 1.2.5 has been made fully open source, and the git tags for 1.5.3, 1.4.6, 1.3.10, and 1.2.7 will build correctly for open source users. BUG FIXES: auth/aws: Made header handling for IAM authentication more robust NOTE: Includes correct license in the HSM binary. NOTE: OSS binaries of 1.5.1, 1.4.4, 1.3.8, and 1.2.5 were built without the Vault UI. Enterprise binaries are not affected. KNOWN ISSUES: AWS IAM logins may return an error depending on the headers sent with the request. For more details and a workaround, see the In versions 1.2.6, 1.3.9, 1.4.5, and 1.5.2, enterprise licenses on the HSM build were not incorporated correctly - enterprise customers should use 1.2.6.1, 1.3.9.1, 1.4.5.1, and 1.5.2.1. SECURITY: When using the IAM AWS Auth Method, under certain circumstances, values Vault uses to validate identities and roles can be manipulated and bypassed. This vulnerability affects Vault and Vault Enterprise 0.7.1 and newer and is fixed in 1.2.5, 1.3.8, 1.4.4, and 1.5.1 (CVE-2020-16250) (Discovered by Felix Wilhelm of Google Project Zero) When using the GCP GCE Auth Method, under certain circumstances, values Vault uses to validate GCE VMs can be manipulated and bypassed. This vulnerability affects Vault and Vault Enterprise 0.8.3 and newer and is fixed in 1.2.5, 1.3.8, 1.4.4, and 1.5.1 (CVE-2020-16251) (Discovered by Felix Wilhelm of Google Project Zero) KNOWN ISSUES: OSS binaries of 1.5.1, 1.4.4, 1.3.8, and 1.2.5 were built without the Vault UI. Enterprise binaries are not affected. AWS IAM logins may return an error depending on the headers sent with the request. For more details and a workaround, see the BUG FIXES: seal: (enterprise) Fix issue causing stored seal and recovery keys to be mistaken as sealwrapped values secrets/aws: Fix issue where performance standbys weren't able to generate STS credentials after an IAM access key rotation in AWS and root IAM credential update in Vault ] SECURITY: core: proxy environment variables are now redacted before being logged, in case the URLs include a username:password. This vulnerability, CVE-2020-13223, is fixed in 1.3.6 and 1.4.2, but affects 1.4 and 1.4.1, as well as older versions of Vault ] BUG FIXES: auth/aws: Fix token renewal issues caused by the metadata changes in

] replication: Fix mount filter bug that allowed replication filters to hide local mounts on a performance secondary CHANGES: auth/aws: The default set of metadata fields added in 1.3.2 has been changed to `accountid` and `authtype` ] IMPROVEMENTS: auth/aws: The set of metadata stored during login is now configurable ] SECURITY: A vulnerability was identified in Vault and Vault Enterprise such that, under certain circumstances, an Entity's Group membership may inadvertently include Groups the Entity no longer has permissions to. This vulnerability, CVE-2020-10660, affects Vault and Vault Enterprise versions 0.9.0 and newer, and is fixed in 1.3.4. ] A vulnerability was identified in Vault Enterprise such that, under certain circumstances, existing nested-path policies may give access to Namespaces created after-the-fact. This vulnerability, CVE-2020-10661, affects Vault Enterprise versions 0.11 and newer, and is fixed in 1.3.4. BUG FIXES: approle: Fix excessive locking during tidy, which could potentially block new approle logins for long enough to cause an outage ] cli: Fix issue where Raft snapshots from standby nodes created an empty backup file ] identity: Fix incorrect caching of identity token JWKS responses ] kmip: role read now returns tlsclientttl kmip: fix panic when templateattr not provided in rekey request secrets/database/influxdb: Fix potential panic if connection to the InfluxDB database cannot be established ] storage/mysql: Fix potential crash when using MySQL as coordination for high availability ] storage/raft: Fix potential crash when using Raft as coordination for high availability ] ui: Fix missing License menu item ] ui: Fix bug where default auth method on login is defaulted to auth method that is listing-visibility=unauth instead of other ] ui: Fix bug where KMIP details were not shown in the UI Wizard ] ui: Show Error messages on Auth Configuration page when you hit permission errors ] ui: Remove duplicate form inputs for the GitHub config ] ui: Correct HMAC capitalization ] ui: Fix danger message in DR ] ui: Fix certificate field for LDAP config ] SECURITY: When deleting a namespace on Vault Enterprise, in certain circumstances, the deletion process will fail to revoke dynamic secrets for a mount in that namespace. This will leave any dynamic secrets in remote systems alive and will fail to clean them up. This vulnerability, CVE-2020-7220, affects Vault Enterprise 0.11.0 and

IMPROVEMENTS: auth/aws: Add aws metadata to identity alias ] auth/kubernetes: Allow both names and namespaces to be set to "" ] BUG FIXES: auth/azure: Fix Azure compute client to use correct base URL ] auth/ldap: Fix renewal of tokens without configured policies that are generated by an LDAP login ] auth/okta: Fix renewal of tokens without configured policies that are generated by an Okta login ] core: Fix seal migration error when attempting to migrate from auto unseal to shamir ] core: Fix seal migration config issue when migrating from auto unseal to auto unseal ] plugin: Fix issue where a plugin unwrap request potentially used an expired token ] replication: Fix issue where a forwarded request from a performance/standby node could run into a timeout secrets/database: Fix issue where a manual static role rotation could potentially panic ] secrets/database: Fix issue where a manual root credential rotation request is not forwarded to the primary node ] secrets/database: Fix issue where a manual static role rotation request is not forwarded to the primary node ] secrets/database/mysql: Fix issue where special characters for a MySQL password were encoded ] ui: Fix deleting namespaces ] ui: Fix Error handler on kv-secret edit and kv-secret view pages ] ui: Fix OIDC callback to check storage ]. ui: Change `.box-radio` height to min-height to prevent overflow issues ] IMPROVEMENTS: agent: Add ability to set `exit-after-auth` via the CLI ] auth/ldap: Add a `request_timeout` configuration option to prevent connection requests from hanging ] auth/kubernetes: Add audience to tokenreview API request for Kube deployments where issuer is not Kube. ] secrets/ad: Add a `request_timeout` configuration option to prevent connection requests from hanging ] storage/postgresql: Add support for setting `connection_url` from enviornment variable `VAULTPGCONNECTION_URL` ] telemetry: Add `enablehostnamelabel` option to telemetry stanza ] telemetry: Add accept header check for prometheus mime type ] BUG FIXES: agent: Fix issue where Agent exits before all templates are rendered when using and `exitafterauth` ] auth/aws: Fixes region-related issues when using a custom `sts_endpoint` by adding a `sts_region` parameter ] auth/token: Fix panic when getting batch tokens on a performance standby from a role that does not exist ] core: Improve warning message for lease TTLs ] identity: Fix identity token panic during invalidation ] plugin: Fix a panic that could occur if a mount/auth entry was unable to mount the plugin backend and a request that required the system view to be retrieved was made ] replication: Add `generate-public-key` endpoint to list of allowed endpoints for existing DR secondaries secrets/gcp: Fix panic if bindings aren't provided in roleset create/update. ] secrets/pki: Prevent generating certificate on performance standby when storing ] secrets/transit: Prevent restoring keys to new names that are sub paths ] storage/s3: Fix a bug in configurable S3 paths that was preventing use of S3 as a source during `operator migrate` operations ] ui: Ensure secrets with a period in their key can be viewed and copied ] ui: Fix status menu after demotion ] ui: Fix select dropdowns in Safari when running Mojave ] CHANGES: Secondary cluster activation: There has been a change to the way that activating performance and DR secondary clusters works when using public keys for encryption of the parameters rather than a wrapping token. This flow was experimental and never documented. It is now officially supported and documented but is not backwards compatible with older Vault releases. Cluster cipher suites: On its cluster port, Vault will no longer advertise the full TLS 1.2 cipher suite list by default. Although this port is only used for Vault-to-Vault communication and would always pick a strong cipher, it could cause false flags on port scanners and other security utilities that assumed insecure ciphers were being used. The previous behavior can be achieved by setting the value of the (undocumented) `clusterciphersuites` config flag to `tls12`. API/Agent Renewal behavior: The API now allows multiple options for how it deals with renewals. The legacy behavior in the Agent/API is for the renewer (now called the lifetime watcher) to exit on a renew error, leading to a reauthentication. The new default behavior is for the lifetime watcher to ignore 5XX errors and simply retry as scheduled, using the existing lease duration. It is also possible, within custom code, to disable renewals entirely, which allows the lifetime watcher to simply return when it believes it is time for your code to renew or reauthenticate. FEATURES: Vault Debug*: A new top-level subcommand, `debug`, is added that allows operators to retrieve debugging information related to a particular Vault node. Operators can use this simple workflow to capture triaging information, which can then be consumed programmatically or by support and engineering teams. It has the abilitity to probe for config, host, metrics, pprof, server status, and replication

Recovery Mode*: Vault server can be brought up in recovery mode to resolve outages caused due to data store being in bad state. This is a privileged mode that allows `sys/raw` API calls to perform surgical corrections to the data store. Bad storage state can be caused by bugs. However, this is usually observed when known (and fixed) bugs are hit by older versions of Vault. Entropy Augmentation (Enterprise)*: Vault now supports sourcing entropy from external source for critical security parameters. Currently an HSM that supports PKCS#11 is the only supported source. Active Directory Secret Check-In/Check-Out*: In the Active Directory secrets engine, users or applications can check out a service account for use, and its password will be rotated when it's checked back in. Vault Agent Template*: Vault Agent now supports rendering templates containing Vault secrets to disk, similar to Consul Template ] Transit Key Type Support*: Signing and verification is now supported with the P-384 (secp384r1) and P-521 (secp521r1) ECDSA curves ] and encryption and decryption is now supported via AES128-GCM96 ] SSRF Protection for Vault Agent*: Vault Agent has a configuration option to require a specific header before allowing requests ] AWS Auth Method Root Rotation*: The credential used by the AWS auth method can now be rotated, to ensure that only Vault knows the credentials it is using ] New UI Features*: The UI now supports managing users and groups for the Userpass, Cert, Okta, and Radius auth methods. Shamir with Stored Master Key*: The on disk format for Shamir seals has changed, allowing for a secondary cluster using Shamir downstream from a primary cluster using Auto Unseal. ] Stackdriver Metrics Sink*: Vault can now send metrics to . See the [configuration documentation](https://www.vaultproject.io/docs/config/index.html) for details. ] Filtered Paths Replication (Enterprise)*: Based on the predecessor Filtered Mount Replication, Filtered Paths Replication allows now filtering of namespaces in addition to mounts. With this feature, Filtered Mount Replication should be considered deprecated. Token Renewal via Accessor*: Tokens can now be renewed via the accessor value through the new `auth/token/renew-accessor` endpoint if the caller's token has permission to access that endpoint. Improved Integrated Storage (Beta)*: Improved raft write performance, added support for non-voter nodes, along with UI support for: using raft storage, joining a raft cluster, and downloading and restoring a snapshot. IMPROVEMENTS: agent: Add ability to set the TLS SNI name used by Agent ] agent & api: Change default renewer behavior to ignore 5XX errors ] auth/jwt: The redirect callback host may now be specified for CLI logins ] auth/jwt: Bound claims may now contain boolean values ] auth/jwt: CLI logins can now open the browser when running in WSL ] core: Exit ScanView if context has been cancelled ] core: re-encrypt barrier and recovery keys if the unseal key is updated ] core: Don't advertise the full set of TLS 1.2 cipher suites on the cluster port, even though only strong ciphers were used ] core (enterprise): Add background seal re-wrap core/metrics: Add config parameter to allow unauthenticated sys/metrics access. ] metrics: Upgrade DataDog library to improve performance ] replication (enterprise): Write-Ahead-Log entries will not duplicate the data belonging to the encompassing physical entries of the transaction, thereby improving the performance and storage capacity. replication (enterprise): Added more replication metrics replication (enterprise): Reindex process now compares subpages for a more accurate indexing process. replication (enterprise): Reindex API now accepts a new `skip_flush` parameter indicating all the changes should not be flushed while the tree is

secrets/aws: The root config can now be read ] secrets/aws: Role paths may now contain the '@' character ] secrets/database/cassandra: Add ability to skip verfication of connection ] secrets/gcp: Fix panic during rollback if the roleset has been deleted ] storage/azure: Add config parameter to Azure storage backend to allow specifying the ARM endpoint ] storage/cassandra: Improve storage efficiency by eliminating unnecessary copies of value data ] storage/raft: Improve raft write performance by utilizing FSM Batching ] storage/raft: Add support for non-voter nodes ] sys: Add a new `sys/host-info` endpoint for querying information about the host ] sys: Add a new set of endpoints under `sys/pprof/` that allows profiling information to be extracted ] sys: Add endpoint that counts the total number of active identity entities ] sys: `sys/seal-status` now has a `storage_type` field denoting what type of storage the cluster is configured to use sys: Add a new `sys/internal/counters/tokens` endpoint, that counts the total number of active service token accessors in the shared token storage. ] sys/config: Add a new endpoint under `sys/config/state/sanitized` that returns the configuration state of the server. It excludes config values from `storage`, `ha_storage`, and `seal` stanzas and some values from `telemetry` due to potential sensitive entries in those fields. ui: when using raft storage, you can now join a raft cluster, download a snapshot, and restore a snapshot from the UI ] ui: clarify when secret version is deleted in the secret version history dropdown ] BUG FIXES: agent: Fix a data race on the token value for inmemsink ] api: Fix Go API using lease revocation via URL instead of body ] api: Allow setting a function to control retry behavior ] auth/gcp: Fix a bug where region information in instance groups names could cause an authorization attempt to fail ] cli: Fix a bug where a token of an unknown format (e.g. in ~/.vault-token) could cause confusing error messages during `vault login` ] cli: Fix a bug where the `namespace list` command with JSON formatting always returned an empty object ] cli: Command timeouts are now always specified solely by the `VAULTCLIENTTIMEOUT` value. ] core: Don't allow registering a non-root zero TTL token lease. This is purely defense in depth as the lease would be revoked immediately anyways, but there's no real reason to allow registration. ] core: Correctly revoke the token that's present in the response auth from a auth/token/ request if there's partial failure during the process. ] identity (enterprise): Fixed identity case sensitive loading in secondary cluster ] identity: Ensure only replication primary stores the identity case sensitivity state ] raft: Fixed VAULTCLUSTERADDR env being ignored at startup ] secrets/pki: Don't allow duplicate SAN names in issued certs ] sys/health: Pay attention to the values provided for `standbyok` and `perfstandbyok` rather than simply using their presence as a key to flip on that behavior ] ui: using the `wrappedtoken` query param will work with `redirectto` and will automatically log in as intended ] ui: fix an error when initializing from the UI using PGP keys ] ui: show all active kv v2 secret versions even when `deleteversionafter` is configured ] ui: Ensure that items in the top navigation link to pages that users have access to ] NOTE: All security content from 1.5.2, 1.5.1, 1.4.5, 1.4.4, 1.3.9, 1.3.8, 1.2.6, and 1.2.5 has been made fully open source, and the git tags for 1.5.3, 1.4.6, 1.3.10, and 1.2.7 will build correctly for open source users. BUG FIXES: auth/aws: Made header handling for IAM authentication more robust NOTE: Includes correct license in the HSM binary. NOTE: OSS binaries of 1.5.1,

1.3.8, and 1.2.5 were built without the Vault UI. Enterprise binaries are not affected. KNOWN ISSUES: AWS IAM logins may return an error depending on the headers sent with the request. For more details and a workaround, see the In versions 1.2.6, 1.3.9, 1.4.5, and 1.5.2, enterprise licenses on the HSM build were not incorporated correctly - enterprise customers should use 1.2.6.1, 1.3.9.1, 1.4.5.1, and 1.5.2.1. SECURITY: When using the IAM AWS Auth Method, under certain circumstances, values Vault uses to validate identities and roles can be manipulated and bypassed. This vulnerability affects Vault and Vault Enterprise 0.7.1 and newer and is fixed in 1.2.5, 1.3.8, 1.4.4, and 1.5.1 (CVE-2020-16250) (Discovered by Felix Wilhelm of Google Project Zero) When using the GCP GCE Auth Method, under certain circumstances, values Vault uses to validate GCE VMs can be manipulated and bypassed. This vulnerability affects Vault and Vault Enterprise 0.8.3 and newer and is fixed in 1.2.5, 1.3.8, 1.4.4, and 1.5.1 (CVE-2020-16251) (Discovered by Felix Wilhelm of Google Project Zero) KNOWN ISSUES: OSS binaries of 1.5.1, 1.4.4, 1.3.8, and 1.2.5 were built without the Vault UI. Enterprise binaries are not affected. AWS IAM logins may return an error depending on the headers sent with the request. For more details and a workaround, see the BUG FIXES: seal: (enterprise) Fix issue causing stored seal and recovery keys to be mistaken as sealwrapped values SECURITY: In a non-root namespace, revocation of a token scoped to a non-root namespace did not trigger the expected revocation of dynamic secret leases associated with that token. As a result, dynamic secret leases in non-root namespaces may outlive the token that created them. This vulnerability, CVE-2019-18616, affects Vault Enterprise 0.11.0 and newer. Disaster Recovery secondary clusters did not delete already-replicated data after a mount filter has been created on an upstream Performance secondary cluster. As a result, encrypted secrets may remain replicated on a Disaster Recovery secondary cluster after application of a mount filter excluding those secrets from replication. This vulnerability, CVE-2019-18617, affects Vault Enterprise 0.8 and newer. Update version of Go to 1.12.12 to fix Go bug golang.org/issue/34960 which corresponds to CVE-2019-17596. CHANGES: auth/aws: If a custom `sts_endpoint` is configured, Vault Agent and the CLI should provide the corresponding region via the `region` parameter (which already existed as a CLI parameter, and has now been added to Agent). The automatic region detection added to the CLI and Agent in 1.2 has been removed. IMPROVEMENTS: cli: Ignore existing token during CLI login ] core: Log proxy settings from environment on startup ] core: Cache whether we've been initialized to reduce load on storage ] BUG FIXES: agent: Fix handling of gzipped responses ] cli: Fix panic when pgp keys list is empty ] cli: Command timeouts are now always specified solely by the `VAULTCLIENTTIMEOUT` value. ] core: add hook for initializing seals for migration ] core (enterprise): Migrating from one auto unseal method to another never worked on enterprise, now it does. identity: Add required field `responsetypessupported` to identity token `.well-known/openid-configuration` response ] identity: Fixed nil pointer panic when merging entities ] replication (Enterprise): Fix issue causing performance standbys nodes disconnecting when under high

secrets/azure: Fix panic that could occur if client retries timeout ] secrets/database: Fix bug in combined DB secrets engine that can result in writes to static-roles endpoints timing out ] secrets/pki: Improve tidy to continue when value is nil ] ui (Enterprise): Allow kv v2 secrets that are gated by Control Groups to be viewed in the UI ] FEATURES: Oracle Cloud (OCI) Integration*: Vault now support using Oracle Cloud for storage, auto unseal, and authentication. IMPROVEMENTS: auth/jwt: Groups claim matching now treats a string response as a single element list ] auth/kubernetes: enable better support for projected tokens API by allowing user to specify issuer ] auth/pcf: The PCF auth plugin was renamed to the CF auth plugin, maintaining full backwards compatibility ] replication: Premium packages now come with unlimited performance standby nodes BUG FIXES: agent: Allow batch tokens and other non-renewable tokens to be used for agent operations ] auth/jwt: Fix an error where newer (v1.2) token_ configuration parameters were not being applied to tokens generated using the OIDC login flow ] raft: Fix an incorrect JSON tag on `leadercacert` in the join request ] seal/transit: Allow using Vault Agent for transit seal operations ] storage/couchdb: Fix a file descriptor leak ] ui: Fix a bug where the status menu would disappear when trying to revoke a token ] ui: Fix a regression that prevented input of custom items in search-select ] ui: Fix an issue with the namespace picker being unable to render nested namespaces named with numbers and sorting of namespaces in the picker ] CHANGES: auth/pcf: The signature format has been updated to use the standard Base64 encoding instead of the URL-safe variant. Signatures created using the previous format will continue to be accepted [PCF-27] core: The http response code returned when an identity token key is not found has been changed from 400 to 404 IMPROVEMENTS: identity: Remove 512 entity limit for groups ] BUG FIXES: auth/approle: Fix an error where an empty `token_type` string was not being correctly handled as `TokenTypeDefault` ] auth/radius: Fix panic when logging in ] ui: the string-list widget will now honor multiline input ] ui: various visual bugs in the KV interface were addressed ] ui: fixed incorrect URL to access help in LDAP auth ] BUG FIXES: agent: Fix a panic on creds pulling in some error conditions in `aws` and `alicloud` auth methods ] auth/approle: Fix error reading role-id on a role created pre-1.2 ] auth/token: Fix sudo check in non-root namespaces on create ] core: Fix health checks with perfstandbyok=true returning the wrong status code ] ui: The web CLI will now parse input as a shell string, with special characters escaped ] ui: The UI will now redirect to a page after authentication ] ui (Enterprise): The list of namespaces is now cleared when logging out ] CHANGES: Token store roles use new, common token fields for the values that overlap with other auth backends. `period`, `explicitmaxttl`, and `bound_cidrs` will continue to work, with priority being given to the `token_` prefixed versions of those parameters. They will also be returned when doing a read on the role if they were used to provide values initially; however, in Vault 1.4 if `period` or `explicitmaxttl` is zero they will no longer be returned. (`explicitmaxttl` was already not returned if empty.) Due to underlying changes in Go version 1.12 and Go > 1.11.5, Vault is now stricter about what characters it will accept in path names. Whereas before it would filter out unprintable characters (and this could be turned off), control characters and other invalid characters are now rejected within Go's HTTP library before the request is passed to Vault, and this cannot be disabled. To continue using these (e.g. for already-written paths), they must be properly percent-encoded (e.g. `\r` becomes `%0D`, `\x00` becomes `%00`, and so

The user-configured regions on the AWSKMS seal stanza will now be preferred over regions set in the enclosing environment. This is a breaking change. All values in audit logs now are omitted if they are empty. This helps reduce the size of audit log entries by not reproducing keys in each entry that commonly don't contain any value, which can help in cases where audit log entries are above the maximum UDP packet size and others. Both PeriodicFunc and WALRollback functions will be called if both are provided. Previously WALRollback would only be called if PeriodicFunc was not set. See ] for details. Vault now uses Go's official dependency management system, Go Modules, to manage dependencies. As a result to both reduce transitive dependencies for API library users and plugin authors, and to work around various conflicts, we have moved various helpers around, mostly under an `sdk/` submodule. A couple of functions have also moved from plugin helper code to the `api/` submodule. If you are a plugin author, take a look at some of our official plugins and the paths they are importing for guidance. AppRole uses new, common token fields for values that overlap with other auth backends. `period` and `policies` will continue to work, with priority being given to the `token_` prefixed versions of those parameters. They will also be returned when doing a read on the role if they were used to provide values initially. In AppRole, `"default"` is no longer automatically added to the `policies` parameter. This was a no-op since it would always be added anyways by Vault's core; however, this can now be explicitly disabled with the new `tokennodefault_policy` field. In AppRole, `boundcidrlist` is no longer returned when reading a role rollback: Rollback will no longer display log messages when it runs; it will only display messages on error. Database plugins will now default to 4 `maxopenconnections` rather than 2. FEATURES: Integrated Storage*: Vault 1.2 includes a tech preview of a new way to manage storage directly within a Vault cluster. This new integrated storage solution is based on the Raft protocol which is also used to back HashiCorp Consul and HashiCorp Nomad. Combined DB credential rotation*: Alternative mode for the Combined DB Secret Engine to automatically rotate existing database account credentials and set Vault as the source of truth for credentials. Identity Tokens*: Vault's Identity system can now generate OIDC-compliant ID tokens. These customizable tokens allow encapsulating a signed, verifiable snapshot of identity information and metadata. They can be use by other applicationseven those without Vault authorizationas a way of establishing identity based on a Vault entity. Pivotal Cloud Foundry plugin*: New auth method using Pivotal Cloud Foundry certificates for Vault authentication. ElasticSearch database plugin*: New ElasticSearch database plugin issues unique, short-lived ElasticSearch credentials. New UI Features*: An HTTP Request Volume Page and new UI for editing LDAP Users and Groups have been added. HA support for Postgres*: PostgreSQL versions >= 9.5 may now but used as and HA storage backend. KMIP secrets engine (Enterprise)*: Allows Vault to operate as a KMIP Server, seamlessly brokering cryptographic operations for traditional infrastructure. Common Token Fields: Auth methods now use common fields for controlling token behavior, making it easier to understand configuration across methods. Vault API explorer*: The Vault UI now includes an embedded API explorer where you can browse the endpoints avaliable to you and make requests. To try it out, open the Web CLI and type

IMPROVEMENTS: agent: Allow EC2 nonce to be passed in ] agent: Add optional `namespace` parameter, which sets the default namespace for the auto-auth functionality ] agent: Add cert auto-auth method ] api: Add support for passing data to delete operations via `DeleteWithData` ] audit/file: Dramatically speed up file operations by changing locking/marshaling order ] auth/jwt: A JWKS endpoint may now be configured for signature verification ] auth/jwt: A new `verboseoidclogging` role parameter has been added to help troubleshoot OIDC configuration ] auth/jwt: `bound_claims` will now match received claims that are lists if any element of the list is one of the expected values ] auth/jwt: Leeways for `nbf` and `exp` are now configurable, as is clock skew leeway ] auth/kubernetes: Allow service names/namespaces to be configured as globs ] auth/token: Allow the support of the identity system for the token backend via token roles ] auth/token: Add a large set of token configuration options to token store roles ] cli: `path-help` now allows `-format=json` to be specified, which will output OpenAPI ] cli: Add support for passing parameters to `vault delete` operations ] cli: Add a log-format CLI flag that can specify either "standard" or "json" for the log format for the `vault server`command. ] cli: Add `-dev-no-store-token` to allow dev servers to not store the generated token at the tokenhelper location ] identity: Allow a group alias' canonical ID to be modified namespaces: Namespaces can now be created and deleted from performance replication secondaries plugins: Change the default for `maxopenconnections` for DB plugins to 4 ] replication: Client TLS authentication is now supported when enabling or updating a replication secondary secrets/database: Cassandra operations will now cancel on client timeout ] secrets/kv: Add optional `deleteversionafter` parameter, which takes a duration and can be set on the mount and/or the metadata for a specific key ] storage/postgres: LIST now performs better on large datasets ] storage/s3: A new `path` parameter allows selecting the path within a bucket for Vault data ] ui: KV v1 and v2 will now gracefully degrade allowing a write without read workflow in the UI ] ui: Many visual improvements with the addition of Toolbars ], the restyling of the Confirm Action component ], and using a new set of glyphs for our Icon component ] ui: Lazy loading parts of the application so that the total initial payload is smaller ] ui: Tabbing to auto-complete in filters will first complete a common prefix if there is one ] ui: Removing jQuery from the application makes the initial JS payload smaller ] BUG FIXES: audit: Log requests and responses due to invalid wrapping token provided ] audit: Fix bug preventing request counter queries from working with auditing enabled auth/aws: AWS Roles are now upgraded and saved to the latest version just after the AWS credential plugin is mounted. ] auth/aws: Fix a case where a panic could stem from a malformed assumed-role ARN when parsing this value ] auth/aws: Fix an error complaining about a read-only view that could occur during updating of a role when on a performance replication secondary ] auth/jwt: Fix a regression introduced in

that disabled checking of client_id for OIDC logins ] auth/jwt: Fix a panic during OIDC CLI logins that could occur if the Vault server response is empty ] auth/jwt: Fix issue where OIDC logins might intermittently fail when using performance standbys ] identity: Fix a case where modifying aliases of an entity could end up moving the entity into the wrong namespace namespaces: Fix a behavior (currently only known to be benign) where we wouldn't delete policies through the official functions before wiping the namespaces on deletion secrets/database: Escape username/password before using in connection URL ] secrets/pki: Forward revocation requests to active node when on a performance standby ] ui: Fix timestamp on some transit keys ] ui: Show Entities and Groups in Side Navigation ] ui: Ensure dropdown updates selected item on HTTP Request Metrics page NOTE: Although 1.1.4 was tagged, we realized very soon after the tag was publicly pushed that an intended fix was accidentally left out. As a result, 1.1.4 was not officially announced and 1.1.5 should be used as the release after 1.1.3. IMPROVEMENTS: identity: Allow a group alias' canonical ID to be modified namespaces: Improve namespace deletion performance ] namespaces: Namespaces can now be created and deleted from performance replication secondaries BUG FIXES: api: Add backwards compat support for API env vars ] auth/aws: Fix a case where a panic could stem from a malformed assumed-role ARN when parsing this value ] auth/ldap: Add `usepre111groupcnbehavior` flag to allow recovering from a regression caused by a bug fix starting in

] auth/aws: Use a role cache to avoid separate locking paths ] core: Fix a deadlock if a panic happens during request handling ] core: Fix an issue that may cause key upgrades to not be cleaned up properly ] core: Don't shutdown if key upgrades fail due to canceled context ] core: Fix panic caused by handling requests while vault is inactive identity: Fix reading entity and groups that have spaces in their names ] identity: Ensure entity alias operations properly verify namespace ] mfa: Fix a nil pointer panic that could occur if invalid Duo credentials were supplied replication: Forward step-down on perf standbys to match HA behavior replication: Fix various read only storage errors on performance standbys replication: Stop forwarding before stopping replication to eliminate some possible bad states secrets/database: Allow cassandra queries to be cancled ] storage/consul: Fix a regression causing vault to not connect to consul over unix sockets ] ui: Fix saving of TTL and string array fields generated by Open API ] IMPROVEMENTS: agent: Now supports proxying request query parameters ] core: Mount table output now includes a UUID indicating the storage path ] core: HTTP server timeout values are now configurable ] replication: Improve performance of the reindex operation on secondary clusters when mount filters are in use replication: Replication status API now returns the state and progress of a reindex BUG FIXES: api: Return the Entity ID in the secret output ] auth/jwt: Consider bound claims when considering if there is at least one bound constraint ] auth/okta: Fix handling of group names containing slashes ] cli: Add deprecated stored-shares flag back to the init command ] cli: Fix a panic when the KV command would return no data ] cli: Fix issue causing CLI list operations to not return proper format when there is an empty response ] core: Correctly honor non-HMAC request keys when auditing requests ] core: Fix the `x-vault-unauthenticated` value in OpenAPI for a number of endpoints ] core: Fix issue where some OpenAPI parameters were incorrectly listed as being sent as a header ] core: Fix issue that would allow duplicate mount names to be used ] namespaces: Fix behavior when using `root` instead of `root/` as the namespace header value pki: fix a panic when a client submits a null value ] replication: Properly update mount entry cache on a secondary to apply all new values after a tune replication: Properly close connection on bootstrap error replication: Fix an issue causing startup problems if a namespace policy wasn't replicated properly replication: Fix longer than necessary WAL replay during an initial reindex replication: Fix error during mount filter invalidation on DR secondary clusters secrets/ad: Make time buffer configurable [AD-35] secrets/gcp: Check for nil config when getting credentials ] secrets/gcp: Fix error checking in some cases where the returned value could be 403 instead of 404 ] secrets/gcpkms: Disable key rotation when deleting a key ] storage/consul: recognize `https://` address even if schema not specified ] storage/dynamodb: Fix an issue where a deleted lock key in DynamoDB (HA) could cause constant switching of the active node ] storage/dynamodb: Eliminate a high-CPU condition that could occur if an error was received from the DynamoDB API ] storage/gcs: Correctly use configured chunk size values ] storage/mssql: Use the correct database when pre-created schemas exist ] ui: Fix issue with select arrows on drop down menus ] ui: Fix an issue where sensitive input values weren't being saved to the server ] ui: Fix web cli parsing when using quoted values ] ui: Fix a namespace workflow mapping identities from external namespaces by allowing arbitrary input in search-select component ] This is a bug fix release containing the two items below. It is otherwise unchanged from 1.1.1. BUG FIXES: auth/okta: Fix a potential dropped error ] secrets/kv: Fix a regression on upgrade where a KVv2 mount could fail to be mounted on unseal if it had previously been mounted but not written to ] SECURITY: Given: (a) performance replication is enabled; (b) performance standbys are in use on the performance replication secondary cluster; and (c) mount filters are in use, if a mount that was previously available to a secondary is updated to be filtered out, although the data would be removed from the secondary cluster, the in-memory cache of the data would not be purged on the performance standby nodes. As a result, the previously-available data could still be read from memory if it was ever read from disk, and if this included mount configuration data this could result in token or lease issuance. The issue is fixed in this release; in prior releases either an active node changeover (such as a step-down) or a restart of the standby nodes is sufficient to cause the performance standby nodes to clear their cache. A CVE is in the process of being issued; the number is CVE-2019-11075. Roles in the JWT Auth backend using the OIDC login flow (i.e. role_type of oidc) were not enforcing bound_cidrs restrictions, if any were configured for the role. This issue did not affect roles of type jwt. CHANGES: auth/jwt: Disallow logins of role_type "oidc" via the `/login` path ] core/acl: New ordering defines which policy wins when there are multiple inexact matches and at least one path contains `+`. `+*` is now illegal in policy paths. The previous behavior simply selected any matching segment-wildcard path that matched. ] replication: Due to technical limitations, mounting and unmounting was not previously possible from a performance secondary. These have been resolved, and these operations may now be run from a performance

IMPROVEMENTS: agent: Allow AppRole auto-auth without a secret-id ] auth/gcp: Cache clients to improve performance and reduce open file usage auth/jwt: Bounds claims validiation will now allow matching the received claims against a list of expected values ] secret/gcp: Cache clients to improve performance and reduce open file usage replication: Mounting/unmounting/remounting/mount-tuning is now supported from a performance secondary cluster ui: Suport for authentication via the RADIUS auth method ] ui: Navigating away from secret list view will clear any page-specific filter that was applied ] ui: Improved the display when OIDC auth errors ] BUG FIXES: agent: Allow auto-auth to be used with caching without having to define any sinks ] agent: Disallow some nonsensical config file combinations ] auth/ldap: Fix CN check not working if CN was not all in uppercase ] auth/jwt: The CLI helper for OIDC logins will now open the browser to the correct URL when running on Windows ] auth/jwt: Fix OIDC login issue where configured TLS certs weren't being used ] auth/jwt: Fix an issue where the `oidc_scopes` parameter was not being included in the response to a role read request ] core: Fix seal migration case when migrating to Shamir and a seal block wasn't explicitly specified ] core: Fix unwrapping when using namespaced wrapping tokens ] core: Fix incorrect representation of required properties in OpenAPI output ] core: Fix deadlock that could happen when using the UI ] identity: Fix updating groups removing existing members ] identity: Properly invalidate group alias in performance secondary ] identity: Use namespace context when loading entities and groups to ensure merging of duplicate entries works properly ] replication: Fix performance standby election failure ] replication: Fix mount filter invalidation on performance standby nodes replication: Fix license reloading on performance standby nodes replication: Fix handling of control groups on performance standby nodes replication: Fix some forwarding scenarios with request bodies using performance standby nodes ] secret/gcp: Fix roleset binding when using JSON ] secret/pki: Use `uri_sans` param in when not using CSR parameters ] storage/dynamodb: Fix a race condition possible in HA configurations that could leave the cluster without a leader ] ui: Fix an issue where in production builds OpenAPI model generation was failing, causing any form using it to render labels with missing fields ] ui: Fix issue nav-hiding when moving between namespaces ] ui: Secrets will always show in the nav regardless of access to cubbyhole ] ui: fix SSH OTP generation ] ui: add polyfill to load UI in IE11 ] ui: Fix issue where some elements would fail to work properly if using ACLs with segment-wildcard paths (`/+/` segments) ] CHANGES: auth/jwt: The `groupsclaimdelimiter_pattern` field has been removed. If the groups claim is not at the top level, it can now be specified as a . auth/jwt: Roles now have a "role type" parameter with a default type of "oidc". To configure new JWT roles, a role type of "jwt" must be explicitly specified. cli: CLI commands deprecated in 0.9.2 are now removed. Please see the CLI help/warning output in previous versions of Vault for updated commands. core: Vault no longer automatically mounts a K/V backend at the "secret/" path when initializing Vault core: Vault's cluster port will now be open at all times on HA standby nodes plugins: Vault no longer supports running netRPC plugins. These were deprecated in favor of gRPC based plugins and any plugin built since 0.9.4 defaults to gRPC. Older plugins may need to be recompiled against the latest Vault dependencies. FEATURES: Vault Agent Caching*: Vault Agent can now be configured to act as a caching proxy to Vault. Clients can send requests to Vault Agent and the request will be proxied to the Vault server and cached locally in Agent. Currently Agent will cache generated leases and tokens and keep them

The proxy can also use the Auto Auth feature so clients do not need to authenticate to Vault, but rather can make requests to Agent and have Agent fully manage token lifecycle. OIDC Redirect Flow Support*: The JWT auth backend now supports OIDC roles. These allow authentication via an OIDC-compliant provider via the user's browser. The login may be initiated from the Vault UI or through the `vault login` command. ACL Path Wildcard*: ACL paths can now use the `+` character to enable wild card matching for a single directory in the path definition. Transit Auto Unseal*: Vault can now be configured to use the Transit Secret Engine in another Vault cluster as an auto unseal provider. IMPROVEMENTS: auth/jwt: A default role can be set. It will be used during JWT/OIDC logins if a role is not specified. auth/jwt: Arbitrary claims data can now be copied into token & alias metadata. auth/jwt: An arbitrary set of bound claims can now be configured for a role. auth/jwt: The name "oidc" has been added as an alias for the jwt backend. Either name may be specified in the `auth enable` command. command/server: A warning will be printed when 'tlsciphersuites' includes a blacklisted cipher suite or all cipher suites are blacklisted by the HTTP/2 specification ] core/metrics: Prometheus pull support using a new sys/metrics endpoint. ] core: On non-windows platforms a SIGUSR2 will make the server log a dump of all running goroutines' stack traces for debugging purposes ] replication: The initial replication indexing process on newly initialized or upgraded clusters now runs asynchronously sentinel: Add token namespace id and path, available in rules as token.namespace.id and token.namespace.path ui: The UI is now leveraging OpenAPI definitions to pull in fields for various forms. This means, it will not be necessary to add fields on the go and JS sides in the future. ] BUG FIXES: auth/jwt: Apply `bound_claims` validation across all login paths auth/jwt: Update `bound_audiences` validation during non-OIDC logins to accept any matched audience, as documented and handled in OIDC logins ] auth/token: Fix issue where empty values for token role update call were ignored ] core: The `operator migrate` command will no longer hang on empty key names ] identity: Fix a panic at login when external group has a nil alias ] namespaces: Clear out identity store items upon namespace deletion replication/perfstandby: Fixed a bug causing performance standbys to wait longer than necessary after forwarding a write to the active node replication/mountfilter: Fix a deadlock that could occur when mount filters were updated ] secret/kv: Fix issue where a v1v2 upgrade could run on a performance standby when using a local mount secret/ssh: Fix for a bug where attempting to delete the last ssh role in the zeroaddress configuration could fail ] secret/totp: Uppercase provided keys so they don't fail base32 validation ] secret/transit: Multiple HMAC, Sign or Verify operations can now be performed with one API call using the new `batch_input` parameter ] sys: `sys/internal/ui/mounts` will no longer return secret or auth mounts that have been filtered. Similarly, `sys/internal/ui/mount/:path` will return a error response if a filtered mount path is requested. ] ui: Fix for a bug where you couldn't access the data tab after clicking on wrap details on the unwrap page ] ui: Fix an issue where the policies tab was erroneously hidden ] ui: Fix encoding issues with kv interfaces ] SECURITY: A regression was fixed in replication mount filter code introduced in Vault 1.0 that caused the underlying filtered data to be replicated to

This data was not accessible to users via Vault's API but via a combination of privileged configuration file changes/Vault commands it could be read. Upgrading to this version or 1.1 will fix this issue and cause the replicated data to be deleted from filtered secondaries. More information was sent to customer contacts on file. CHANGES: New AWS authentication plugin mounts will default to using the generated role ID as the Identity alias name. This applies to both EC2 and IAM auth. Existing mounts that explicitly set this value will not be affected but mounts that specified no preference will switch over on upgrade. The default policy now allows a token to look up its associated identity entity either by name or by id ] The Vault UI's navigation and onboarding wizard now only displays items that are permitted in a users' policy , ] An issue was fixed that caused recovery keys to not work on secondary clusters when using a different unseal mechanism/key than the primary. This would be hit if the cluster was rekeyed or initialized after 1.0. We recommend rekeying the recovery keys on the primary cluster if you meet the above requirements. FEATURES: cURL Command Output*: CLI commands can now use the `-output-curl-string` flag to print out an equivalent cURL command. Response Headers From Plugins*: Plugins can now send back headers that will be included in the response to a client. The set of allowed headers can be managed by the operator. IMPROVEMENTS: auth/aws: AWS EC2 authentication can optionally create entity aliases by role ID ] auth/jwt: The supported set of signing algorithms is now configurable [JWT plugin ] core: When starting from an uninitialized state, HA nodes will now attempt to auto-unseal using a configured auto-unseal mechanism after the active node initializes Vault ] secret/database: Add socket keepalive option for Cassandra ] secret/ssh: Add signed key constraints, allowing enforcement of key types and minimum key sizes ] secret/transit: ECDSA signatures can now be marshaled in JWS-compatible fashion ] storage/etcd: Support SRV service names ] storage/aws: Support specifying a KMS key ID for server-side encryption ] BUG FIXES: core: Fix a rare case where a standby whose connection is entirely torn down to the active node, then reconnects to the same active node, may not successfully resume operation ] cors: Don't duplicate headers when they're written ] identity: Persist merged entities only on the primary ] replication: Fix a potential race when a token is created and then used with a performance standby very quickly, before an associated entity has been replicated. If the entity is not found in this scenario, the request will forward to the active node. replication: Fix issue where recovery keys would not work on secondary clusters if using a different unseal mechanism than the primary. replication: Fix a "failed to register lease" error when using performance standbys storage/postgresql: The `Get` method will now return an Entry object with the `Key` member correctly populated with the full path that was requested instead of just the last path element ] SECURITY: When creating a child token from a parent with `bound_cidrs`, the list of CIDRs would not be propagated to the child token, allowing the child token to be used from any address. CHANGES: secret/aws: Role now returns `credentialtype` instead of `credentialtypes` to match role input. If a legacy role that can supply more than one credential type, they will be concatenated with a `,`. physical/dynamodb, autoseal/aws: Instead of Vault performing environment variable handling, and overriding static (config file) values if found, we use the default AWS SDK env handling behavior, which also looks for deprecated

If you were previously providing both config values and environment values, please ensure the config values are unset if you want to use environment values. Namespaces (Enterprise): Providing "root" as the header value for `X-Vault-Namespace` will perform the request on the root namespace. This is equivalent to providing an empty value. Creating a namespace called "root" in the root namespace is disallowed. FEATURES: InfluxDB Database Plugin*: Use Vault to dynamically create and manage InfluxDB users IMPROVEMENTS: auth/aws: AWS EC2 authentication can optionally create entity aliases by image ID ] autoseal/gcpckms: Reduce the required permissions for the GCPCKMS autounseal ] physical/foundationdb: TLS support added. ] BUG FIXES: api: Fix a couple of places where we were using the `LIST` HTTP verb (necessary to get the right method into the wrapping lookup function) and not then modifying it to a `GET`; although this is officially the verb Vault uses for listing and it's fully legal to use custom verbs, since many WAFs and API gateways choke on anything outside of RFC-standardized verbs we fall back to `GET` ] autoseal/aws: Fix reading session tokens when AWS access key/secret key are also provided ] command/operator/rekey: Fix help output showing `-delete-backup` when it should show `-backup-delete` ] core: Fix bound_cidrs not being propagated to child tokens replication: Correctly forward identity entity creation that originates from performance standby nodes (Enterprise) secret/aws: Make input `credential_type` match the output type (string, not array) ] secret/cubbyhole: Properly cleanup cubbyhole after token revocation ] secret/pki: Fix reading certificates on windows with the file storage backend ] ui (enterprise): properly display perf-standby count on the license page ] ui: fix disappearing nested secrets and go to the nearest parent when deleting a secret - ] ui: fix error where deleting an item via the context menu would fail if the item name contained dots ] ui: allow saving of kv secret after an errored save attempt ] ui: fix display of kv-v1 secret containing a key named "keys" ] SECURITY: Update version of Go to 1.11.3 to fix Go bug <https://github.com/golang/go/issues/29233> which corresponds to CVE-2018-16875 Database user revocation: If a client has configured custom revocation statements for a role with a value of `""`, that statement would be executed verbatim, resulting in a lack of actual revocation but success for the operation. Vault will now strip empty statements from any provided; as a result if an empty statement is provided, it will behave as if no statement is provided, falling back to the default revocation statement. CHANGES: secret/database: On role read, empty statements will be returned as empty slices instead of potentially being returned as JSON null values. This makes it more in line with other parts of Vault and makes it easier for statically typed languages to interpret the

IMPROVEMENTS: cli: Strip iTerm extra characters from password manager input ] command/server: Setting default kv engine to v1 in -dev mode can now be specified via -dev-kv-v1 ] core: Add operationId field to OpenAPI output ] ui: Added ability to search for Group and Policy IDs when creating Groups and Entities instead of typing them in manually BUG FIXES: auth/azure: Cache azure authorizer [15] auth/gcp: Remove explicit project for service account in GCE authorizer ] cli: Show correct stored keys/threshold for autoseals ] cli: Fix backwards compatibility fallback when listing plugins ] core: Fix upgrades when the seal config had been created on early versions of vault ] namespaces: Correctly reload the proper mount when tuning or reloading the mount ] secret/azure: Cache azure authorizer [19] secret/database: Strip empty statements on user input ] secret/gcpkms: Add path for retrieving the public key ] secret/pki: Fix panic that could occur during tidy operation when malformed data was found ] secret/pki: Strip empty line in ca_chain output ] ui: Fixed a bug where the web CLI was not usable via the `fullscreen` command - ] ui: Fix a bug where you couldn't write a jwt auth method config ] SECURITY: When debugging a customer incident we discovered that in the case of malformed data from an autoseal mechanism, Vault's master key could be logged in Vault's server log. For this to happen, the data would need to be modified by the autoseal mechanism after being submitted to it by Vault but prior to encryption, or after decryption, prior to it being returned to Vault. To put it another way, it requires the data that Vault submits for encryption to not match the data returned after decryption. It is not sufficient for the autoseal mechanism to return an error, and it cannot be triggered by an outside attacker changing the on-disk ciphertext as all autoseal mechanisms use authenticated encryption. We do not believe that this is generally a cause for concern; since it involves the autoseal mechanism returning bad data to Vault but with no error, in a working Vault configuration this code path should never be hit, and if hitting this issue Vault will not be unsealing properly anyways so it will be obvious what is happening and an immediate rekey of the master key can be performed after service is restored. We have filed for a CVE (CVE-2018-19786) and a CVSS V3 score of 5.2 has been assigned. CHANGES: Tokens are now prefixed by a designation to indicate what type of token they are. Service tokens start with `s.` and batch tokens start with `b.`. Existing tokens will still work (they are all of service type and will be considered as such). Prefixing allows us to be more efficient when consuming a token, which keeps the critical path of requests faster. Paths within `auth/token` that allow specifying a token or accessor in the URL have been removed. These have been deprecated since March 2016 and undocumented, but were retained for backwards compatibility. They shouldn't be used due to the possibility of those paths being logged, so at this point they are simply being removed. Vault will no longer accept updates when the storage key has invalid UTF-8 character encoding ] Mount/Auth tuning the `options` map on backends will now upsert any provided values, and keep any of the existing values in place if not provided. The options map itself cannot be unset once it's set, but the keypairs within the map can be unset if an empty value is provided, with the exception of the `version` keypair which is handled differently for KVv2 purposes. Agent no longer automatically reauthenticates when new credentials are detected. It's not strictly necessary and in some cases was causing reauthentication much more often than intended. HSM Regenerate Key Support Removed: Vault no longer supports destroying and regenerating encryption keys on an HSM; it only supports creating them. Although this has never been a source of a customer incident, it is simply a code path that is too trivial to activate, especially by mistyping `regeneratekey` instead of `generatekey`. Barrier Config Upgrade (Enterprise): When upgrading from Vault

the seal type in the barrier config storage entry will be upgraded from "hsm-auto" to "awskms" or "pkcs11" upon unseal if using AWSKMS or HSM seals. If performing seal migration, the barrier config should first be upgraded prior to starting migration. Go API client uses pooled HTTP client: The Go API client now uses a connection-pooling HTTP client by default. For CLI operations this makes no difference but it should provide significant performance benefits for those writing custom clients using the Go API library. As before, this can be changed to any custom HTTP client by the caller. Builtin Secret Engines and Auth Methods are integrated deeper into the plugin system. The plugin catalog can now override builtin plugins with custom versions of the same name. Additionally the plugin system now requires a plugin `type` field when configuring plugins, this can be "auth", "database", or "secret". FEATURES: Auto-Unseal in Open Source*: Cloud-based auto-unseal has been migrated from Enterprise to Open Source. We've created a migrator to allow migrating between Shamir seals and auto unseal methods. Batch Tokens*: Batch tokens trade off some features of service tokens for no storage overhead, and in most cases can be used across performance replication clusters. Replication Speed Improvements*: We've worked hard to speed up a lot of operations when using Vault Enterprise Replication. GCP KMS Secrets Engine*: This new secrets engine provides a Transit-like pattern to keys stored within GCP Cloud KMS. AppRole support in Vault Agent Auto-Auth*: You can now use AppRole credentials when having Agent automatically authenticate to Vault OpenAPI Support*: Descriptions of mounted backends can be served directly from Vault Kubernetes Projected Service Account Tokens*: Projected Service Account Tokens are now supported in Kubernetes auth Response Wrapping in UI*: Added ability to wrap secrets and easily copy the wrap token or secret JSON in the UI IMPROVEMENTS: agent: Support for configuring the location of the kubernetes service account ] auth/token: New tokens are indexed in storage HMAC-SHA256 instead of SHA1 secret/totp: Allow @ character to be part of key name ] secret/consul: Add support for new policy based tokens added in Consul 1.4 ] ui: Improve the token auto-renew warning, and automatically begin renewal when a user becomes active again ] ui: The unbundled UI page now has some styling ] ui: Improved banner and popup design ] ui: Added token type to auth method mount config ] ui: Display additonal wrap info when unwrapping. ] ui: Empty states have updated styling and link to relevant actions and documentation ] ui: Allow editing of KV V2 data when a token doesn't have capabilities to read secret metadata ] BUG FIXES: agent: Fix auth when multiple redirects ] cli: Restore the `-policy-override` flag ] core: Fix rekey progress reset which did not happen under certain circumstances. ] core: Migration from autounseal to shamir will clean up old keys ] identity: Update group memberships when entity is deleted ] replication/perfstandby: Fix audit table upgrade on standbys ] replication/perfstandby: Fix redirect on approle update ] secrets/azure: Fix valid roles being rejected for duplicate ids despite having distinct scopes ] storage/gcs: Send md5 of values to GCS to avoid potential corruption ] secrets/kv: Fix issue where storage version would get incorrectly downgraded ] secrets/kv: Disallow empty paths on a `kv put` while accepting empty paths for all other operations for backwards compatibility ] ui: Allow for secret creation in kv v2 when cas_required=true ] ui: Fix dr secondary operation token generation via the ui ] ui: Fix the PKI context menu so that items load ] ui: Update DR Secondary Token generation command ] ui: