Security readout for executives and security teams
Plain-English summary
This flaw affects Rust software that uses vulnerable ed25519-dalek versions for Ed25519 signatures. Under the described oracle condition, an attacker could derive a private key from the Keypair implementation. That threatens confidentiality of signing keys, but the CVSS vector indicates local attack requirements and high attack complexity.
Executive priority
Prioritize as moderate. Business urgency rises sharply if affected keys sign customer identities, software releases, transactions, or authentication tokens. There is no cited active exploitation, but private key exposure can create durable downstream trust failures.
Technical view
CVE-2022-50237 is described as a double public key signing function oracle issue in ed25519-dalek before version 2. The vulnerable Keypair implementation can allow private key extraction by simple computation once the oracle condition is available. The record is sparse and should be validated against RustSec and dependency metadata.
Likely exposure
Exposure is most likely in Rust applications, services, wallets, or libraries that depend on ed25519-dalek versions before 2 and perform signing with Keypair. The source bundle’s affected metadata is limited, so teams should verify exact dependency versions rather than assuming all deployments are affected.
Exploitation context
The source bundle does not report active exploitation, and KEV is false. CVSS lists local attack vector, high complexity, no privileges, and no user interaction. Treat this as a serious key-confidentiality risk where vulnerable signing functionality is reachable.
Researcher notes
Evidence is concise and partly incomplete. The description says ed25519-dalek before 2, while affected metadata in the bundle lists version 0. Validate exact vulnerable ranges through RustSec, the crate history, and dependency manifests before scoping remediation.
Mitigation direction
- Inventory Rust dependencies for ed25519-dalek usage and versions.
- Plan migration to ed25519-dalek version 2 or later where compatible.
- Review RustSec advisory and upstream guidance before deployment.
- Rotate exposed or suspect signing keys after confirming vulnerable use.
- Prioritize systems where signing keys protect funds, identity, or trust anchors.
Validation and detection
- Check Cargo.lock and SBOMs for ed25519-dalek versions before 2.
- Identify services or libraries that call Keypair-based signing paths.
- Confirm whether vulnerable signing functionality is locally reachable.
- Review test coverage around dependency upgrades and signature compatibility.
- Document affected repositories, owners, key material, and remediation status.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-497: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-50237 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N1.44Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.9MediumVector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://rustsec.org/advisories/RUSTSEC-2022-0093.htmlCVE reference
- https://github.com/MystenLabs/ed25519-unsafe-libsCVE reference
- https://crates.io/crates/ed25519-dalekCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Exposure of Sensitive System Information to an Unauthorized Control Sphere
Exposure of Sensitive System Information to an Unauthorized Control Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.