Shared-secret exposure via unchecked elliptic-curve points
Published Feb 24, 2023 · Updated Mar 12, 2025
Invalid-curve handling in Development IL ecdh before 0.2.0 allows remote attackers to obtain a predictable derived shared secret. PrivateKey.prototype.deriveSharedSecret checks only that a public-key object and Q value exist, then multiplies the supplied point without verifying that its coordinates lie on the configured elliptic curve. An unauthenticated peer that supplies the public key can force an all-zero secret with the point (0,0), exposing confidentiality without reported integrity or availability impact.
Summary
What happened
Invalid-curve handling in Development IL ecdh before 0.2.0 allows remote attackers to obtain a predictable derived shared secret. PrivateKey.prototype.deriveSharedSecret checks only that a public-key object and Q value exist, then multiplies the supplied point without verifying that its coordinates lie on the configured elliptic curve. An unauthenticated peer that supplies the public key can force an all-zero secret with the point (0,0), exposing confidentiality without reported integrity or availability impact.
The record
- CVE
- CVE-2022-44310
- Published
- Feb 24, 2023
- Updated
- Mar 12, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-668
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 24, 2023CVE publishedPublication date reported by the CVE source.
- Mar 12, 2025Record 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
- Invalid-point all-zero shared-secret proof of conceptproof of concept · demonstrated
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