Cryptographic integrity failure via ignored SHA-1 input
Published May 12, 2022 · Updated Aug 3, 2024
Cryptographic failure in JetBrains Ktor Native 2.0.0 allows attackers to obtain identical SHA-1 digests for different inputs. The sha1(ByteArray) wrapper in ktor-utils/posix called Sha1().digest() without passing its bytes argument, so it always hashed empty input. Reachability requires application code compiled for Kotlin/Native to call the affected helper; the resulting digest does not represent the supplied data.
Summary
What happened
Cryptographic failure in JetBrains Ktor Native 2.0.0 allows attackers to obtain identical SHA-1 digests for different inputs. The sha1(ByteArray) wrapper in ktor-utils/posix called Sha1().digest() without passing its bytes argument, so it always hashed empty input. Reachability requires application code compiled for Kotlin/Native to call the affected helper; the resulting digest does not represent the supplied data.
The record
- CVE
- CVE-2022-29930
- Published
- May 12, 2022
- Updated
- Aug 3, 2024
- Vendor
- JetBrains
- Product
- Ktor
- Classifications
- CWE-342, CWE-330
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- May 12, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0.0
- Affected versionversion=2.0.1 <2.0.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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