TempID and upload-token fabrication via AES-GCM key reuse
Published Apr 17, 2020 · Updated Aug 4, 2024
Cryptographic weakness in OpenTrace 1.0 Cloud Functions allows remote attackers to fabricate TempIDs or Upload Tokens via repeated requests. The subsystem reuses an AES-256-GCM key beyond the 2^32-invocation limit and can generate duplicate IVs, violating required IV-construction constraints. Exploitation requires collecting duplicate IVs or driving more than 2^32 encryptions under one key, after which forged identifiers or upload tokens compromise tracing-data integrity.
Summary
What happened
Cryptographic weakness in OpenTrace 1.0 Cloud Functions allows remote attackers to fabricate TempIDs or Upload Tokens via repeated requests. The subsystem reuses an AES-256-GCM key beyond the 2^32-invocation limit and can generate duplicate IVs, violating required IV-construction constraints. Exploitation requires collecting duplicate IVs or driving more than 2^32 encryptions under one key, after which forged identifiers or upload tokens compromise tracing-data integrity.
The record
- CVE
- CVE-2020-11872
- Published
- Apr 17, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-327
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 17, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo