chore(deps): update dependency jose to 2.0.6 [security] - abandoned #209
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
Images automagically compressed by Calibre's image-actions ✨ Compression reduced images by 52.5%, saving 1.84 MB.
68 images did not require optimisation. |
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. ⚠ Warning: custom changes will be lost. |
renovate
bot
changed the title
Autoclosing SkippedThis PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error. |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.0.5->2.0.6GitHub Vulnerability Alerts
CVE-2022-36083
The PBKDF2-based JWE key management algorithms expect a JOSE Header Parameter named
p2c(PBES2 Count), which determines how many PBKDF2 iterations must be executed in order to derive a CEK wrapping key. The purpose of this parameter is to intentionally slow down the key derivation function in order to make password brute-force and dictionary attacks more expensive.This makes the PBES2 algorithms unsuitable for situations where the JWE is coming from an untrusted source: an adversary can intentionally pick an extremely high PBES2 Count value, that will initiate a CPU-bound computation that may take an unreasonable amount of time to finish.
Impact
Under certain conditions (see below) it is possible to have the user's environment consume unreasonable amount of CPU time.
Affected users
The impact is limited only to users utilizing the JWE decryption APIs with symmetric secrets to decrypt JWEs from untrusted parties who do not limit the accepted JWE Key Management Algorithms (
algHeader Parameter) using thekeyManagementAlgorithms(oralgorithmsin v1.x) decryption option or through other means.The PBKDF2-based JWE Key Management Algorithm Identifiers are
PBES2-HS256+A128KWPBES2-HS384+A192KWPBES2-HS512+A256KWe.g.
You are NOT affected if any of the following applies to you
keyManagementAlgorithmsdecryption option not including any of the PBKDF2-based JWE key management algorithmsPatches
v1.28.2,v2.0.6,v3.20.4, andv4.9.2releases limit the maximum PBKDF2 iteration count to10000by default. It is possible to adjust this limit with a newly introducedmaxPBES2Countdecryption option.Workarounds
All users should be able to upgrade given all stable semver major release lines have had new a patch release introduced which limits the PBKDF2 iteration count to
10000by default. This removes the ability to craft JWEs that would consume unreasonable amount of CPU time.If users are unable to upgrade their required library version they have two options depending on whether they expect to receive JWEs using any of the three PBKDF2-based JWE key management algorithms.
keyManagementAlgorithmsdecryption option to disable accepting PBKDF2 altogetherp2cHeader Parameter)For more information
If you have any questions or comments about this advisory:
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate. View repository job log here.