Skip to content
Fencer Intel
medium —

GHSA-c7ph-f7jm-xv4w json

rPGP's integrity protection of encrypted data was not always checked

published 9mo ago modified 8mo ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### 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.

Patch / fix

  • crates.io pgp 0.19.0

Is GHSA-c7ph-f7jm-xv4w in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
crates.io pgp
>=0.16.0-alpha.0, <0.19.0
0.19.0

Classification

Weakness
  • CWE-354 Improper Validation of Integrity Check Value

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.