fix(deps): update rust crate pgp to 0.14.0 [security]#4
Open
stackable-bot wants to merge 1 commit into
Open
Conversation
| datasource | package | from | to | | ---------- | ------- | ------ | ------ | | crate | pgp | 0.13.0 | 0.14.2 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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:
0.13.0->0.14.0GitHub Vulnerability Alerts
CVE-2024-53856
During a security audit, Radically Open Security discovered several reachable edge cases which allow an attacker to trigger
rpgpcrashes by providing crafted data.Impact
When processing malformed input,
rpgpcan run into Rust panics which halt the program.This can happen in the following scenarios:
decrypt_with_password()Given the affected components, we consider most attack vectors to be reachable by remote attackers during typical use cases of the
rpgplibrary. The attack complexity is low since the malformed messages are generic, short, and require no victim-specific knowledge.The result is a denial-of-service impact via program termination. There is no impact to confidentiality or integrity security properties.
Versions and Patches
All recent versions are affected by at least some of the above mentioned issues.
The vulnerabilities have been fixed with version
0.14.1. We recommend all users to upgrade to this version.References
The security audit was made possible by the NLnet Foundation NGI Zero Core grant program for rpgp.
CVE-2024-53857
During a security audit, Radically Open Security discovered two vulnerabilities which allow attackers to trigger resource exhaustion vulnerabilities in
rpgpby providing crafted messages. This affects general message parsing and decryption with symmetric keys.Impact
Affected
rpgpversions do not correctly set upper limits on the total reserved amount of memory when parsing long sequences of partial OpenPGP packets, which can grow to to several GiB in size. Additionally, up to 4GiB of memory is reserved for OpenPGP packets of fixed size with large length fields, even if less data is received.Depending on existing message size restrictions and available system resources, this can cause out-of-memory conditions and crash the
rpgpprocess or cause other system instability through memory resource exhaustion when parsing crafted messages.Affected
rpgpversions are susceptible to excessive memory allocation with values of up to 2TiB or long processing times for some decryption operations which involve the Argon2 function. An attacker can provide a validSymmetric Key Encrypted Session Keypacket (SKESK) which usesArgon2for String-to-Key hashing with parameters that are excessive, but within specification limits of the RFC9580 OpenPGP standard. Sincerpgpdid not further restrict the Argon2 parameters, this can cause out-of-memory conditions and crash therpgpprocess. Under some conditions, the memory resource exhaustion may trigger other system instability. Alternatively, this can make the program unresponsive via long computations. The attacker needs to trick a victim into attempting decryption, but does not require knowledge of the symmetric secret used by the victim.There is no impact to confidentiality or integrity security properties.
Versions and Patches
The impact details on the message parsing component varies with different versions. We've confirmed some of the problematic behavior on older versions such as
v0.10.0and see all recent versions as affected in some form.The affected
Argon2functionality was introduced withv0.12.0-alpha.1, earlier versions are not vulnerable.The vulnerabilities have been fixed with version
0.14.2. We recommend all users to upgrade to this version.References
The security audit was made possible by the NLnet Foundation NGI Zero Core grant program for rpgp.
Release Notes
rpgp/rpgp (pgp)
v0.14.2Compare Source
🐛 Bug Fixes
📚 Documentation
v0.14.1Compare Source
⛰️ Features
🐛 Bug Fixes
🚜 Refactor
Displayimplementation forBlockType- (00b5027)🧪 Testing
⚙️ Miscellaneous Tasks
v0.14.0Compare Source
⛰️ Features
SignatureConfig::hash_signature_datamore flexible - (c6d6b2c)🐛 Bug Fixes
🚜 Refactor
📚 Documentation
🧪 Testing
⚙️ Miscellaneous Tasks
v0.13.2Compare Source
🐛 Bug Fixes
🧪 Testing
⚙️ Miscellaneous Tasks
v0.13.1Compare Source
🐛 Bug Fixes
📚 Documentation
⚙️ Miscellaneous Tasks
Configuration
📅 Schedule: Branch creation - "" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.