N/A

CVSS Score

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

GHSA-c7ph-f7jm-xv4w

GHSA-c7ph-f7jm-xv4w: rPGP's integrity protection of encrypted data was not always checked

Summary

For some messages, rPGP returned incorrectly decrypted data without signaling that integrity protection was invalid.

Details

When decrypting SEIPD (Symmetrically Encrypted and Integrity Protected Data Packet), rPGP previously did not under all circumstances report the absence of valid integrity protection to callers of the library.

Impact

While the resulting invalid decryption output is not attacker controlled, its contents may be a security concern if an attacker can gain access to it.

Attribution

Discovered internally in the course of rPGP development work.

(GitHub Advisory)

Miggo Vulnerability Database

→

GHSA-c7ph-f7jm-xv4w

GHSA-c7ph-f7jm-xv4w:

N/A

CVSS Score

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
pgp	rust	>= 0.16.0-alpha.0, < 0.19.0	0.19.0

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability lies in the incomplete consumption of OpenPGP message streams during decryption, specifically for Symmetrically Encrypted and Integrity Protected Data (SEIPD) packets. The integrity of SEIPD packets is verified by a Modification Detection Code (MDC) which is checked only when the entire encrypted data stream is read.

The analysis of the patch 16c2457867476bcb9942c0a13d70d46ef9e350b8 revealed the root cause. The rpgp library uses a MessageReader struct to handle decrypted data. When this struct is dropped, its drop implementation calls the check_next_packet function to handle any data remaining in the stream.

The vulnerable version of check_next_packet in src/composed/message/types.rs would identify certain types of trailing packets (e.g., Padding, Marker) but failed to read their content from the stream. This left the underlying decryption reader in a state where it had not reached the end of the stream. Consequently, the crucial MDC check was never triggered. An attacker could provide a malformed message that, when decrypted with an incorrect key, would produce garbage output but would not fail the integrity check, potentially leading to further issues if this garbage data is processed.

The patch corrects this by introducing a loop and explicitly calling packet.read_to_end() on these trailing packets, ensuring the stream is fully consumed and the MDC is always validated.

The identified vulnerable function, pgp::composed::message::types::MessageReader::check_next_packet, is the precise location of this flawed logic. Any decryption operation that results in a MessageReader for an SEIPD packet was susceptible to this vulnerability.

Vulnerable functions

pgp::composed::message::types::MessageReader::check_next_packet

src/composed/message/types.rs

The function `check_next_packet` is called when a `MessageReader` is dropped to ensure the entire message stream has been processed. The vulnerable version of this function identified certain types of trailing packets (e.g., Padding, Marker) but did not read their content from the underlying stream. For Symmetrically Encrypted and Integrity Protected Data (SEIPD) packets, the integrity check (MDC) is performed only when the encrypted data stream is read to the very end. By not consuming the trailing packets, the stream was not fully read, and the integrity check was skipped. This could allow incorrectly decrypted data to be returned without an error if an incorrect decryption key was used. The patch fixes this by reading the trailing packets to their end, forcing the full consumption of the stream and triggering the integrity check.

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.

N/A

-

Basic Information

Basic Information

Concerned about an active attack path?

GHSA-c7ph-f7jm-xv4w: rPGP's integrity protection of encrypted data was not always checked

Summary

Details

Impact

Attribution

GHSA-c7ph-f7jm-xv4w:

N/A

-

Basic Information

Basic Information

Is this CVE running in your environment?

Technical Details

Technical Details

Vulnerability IntelligenceMiggo AI

Root Cause Analysis

Vulnerable functions

Vulnerability IntelligenceMiggo AI

Unlock WAF rules for this CVE

WAF Protection Rules

WAF Rule

Reasoning

Basic Information

Basic Information

GHSA-c7ph-f7jm-xv4w: rPGP's integrity protection of encrypted data was not always checked

Summary

Details

Impact

Attribution

Technical Details

N/A

N/A

Vulnerability IntelligenceMiggo AI

Root Cause Analysis

Vulnerable functions

Vulnerability Intelligence
Miggo AI

Vulnerability Intelligence
Miggo AI

Vulnerability Intelligence
Miggo AI