CVE-2020-8929
Last modified
CVE-2020-8929 is a medium-severity vulnerability rated 5.3/10 on the CVSS scale. A mis-handling of invalid unicode characters in the Java implementation of Tink versions prior to 1.5 allows an attacker to change the ID part of a ciphertext, which result in the creation of a second ciphertext that can decrypt to the same plaintext. This can be a problem with encrypting deterministic AEAD with a single key, and rely on a unique ciphertext-per-plaintext.. EPSS estimates a 0.47% chance of exploitation in the next 30 days.
Description
A mis-handling of invalid unicode characters in the Java implementation of Tink versions prior to 1.5 allows an attacker to change the ID part of a ciphertext, which result in the creation of a second ciphertext that can decrypt to the same plaintext. This can be a problem with encrypting deterministic AEAD with a single key, and rely on a unique ciphertext-per-plaintext.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Tink Java | < 1.5.0 |
References
- https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899Patch, Third Party Advisory
- https://github.com/google/tink/security/advisories/GHSA-g5vf-v6wf-7w2rPatch, Third Party Advisory
- https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899Patch, Third Party Advisory
- https://github.com/google/tink/security/advisories/GHSA-g5vf-v6wf-7w2rPatch, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2020-8929?
How severe is CVE-2020-8929?
How do I fix CVE-2020-8929?
Are you affected by CVE-2020-8929?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
