Approved changes feed: RSS · Atom
cpe:2.3:a:parsec.cloud:parsec:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Parsec.Cloud (bc6b9d51-8501-54a0-9cf9-8c260b7a5fe2) |
|---|---|
| Product | Parsec (d8ca7d76-bd67-56df-a327-af005aac9aa5) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-62514 |
vulnerable | 2026-06-08 07:37:29.879992 |
`libparsec_crypto` does not check for weak order point of curve 25519
HIGH (8.3)
Parsec is a cloud-based application for cryptographically secure file sharing. In versions on the 3.x branch prior to 3.6.0, `libparsec_crypto`, a component of the Parsec application, does not check for weak order point of Curve25519 when compiled with its RustCrypto backend. In practice this means an attacker in a man-in-the-middle position would be able to provide weak order points to both parties in the Diffie-Hellman exchange, resulting in a high probability to for both parties to obtain the same shared key (hence leading to a successful SAS code exchange, misleading both parties into thinking no MITM has occurred) which is also known by the attacker. Note only Parsec web is impacted (as Parsec desktop uses `libparsec_crypto` with the libsodium backend). Version 3.6.0 of Parsec patches the issue.
Published: 2026-01-29T15:46:50.922Z
Updated: 2026-01-29T21:29:03.456Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.