CVE-2020-8929
Vulnerability Scoring
Status: Modified - Last modified: 21 Nov 2024, 05:39 UTC Published: 19 Oct 2020, 13:15 UTC
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.
Above is the Access Complexity Graph for CVE-2020-8929. It helps visualize the difficulty level and privilege requirements needed to exploit this vulnerability, providing a quick assessment of its exploitation feasibility.
Above is the CVSS Sub-score Breakdown for CVE-2020-8929, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.
Below is the Impact Analysis for CVE-2020-8929, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.
The EPSS score estimates the probability that this vulnerability will be exploited in the near future.
EPSS Score: 0.056% (probability of exploit)
EPSS Percentile: 26.44%
(lower percentile = lower relative risk)
This vulnerability is less risky than approximately 73.56% of others.
NVD-CWE-Other
cve-coordination@google.com
Secondary
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.