# GHSA-j57r-4qw6-58r3: rusty_paseto vulnerable to private key extraction due to ed25519-dalek dependency > A dependency flaw in rusty_paseto allows private key extraction via unsafe serialization APIs, requiring an upgrade to secure key handling. - **Severity:** Not scored - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Not stated - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 7 Nov 2023 ## What is GHSA-j57r-4qw6-58r3? GHSA-j57r-4qw6-58r3 is a vulnerability in rusty-paseto, published on 7 Nov 2023. ### Official description ## Impact The vulnerability, known as RUSTSEC-2022-0093, impacts the `ed25519-dalek` crate, which is a dependency of the `rusty-paseto` crate. This issue arises from a "Double Public Key Signing Function Oracle Attack" affecting versions of `ed25519-dalek` prior to v2.0. These versions expose an unsafe API for serializing and deserializing 64-byte keypairs that include both private and public keys, creating potential for certain attacks. `d25519-dalek` users utilizing these serialization and deserialization functions directly could potentially be impacted. ## Patches The vulnerability within the `ed25519-dalek` crate has been addressed in version 2.0. `rusty-paseto` has addressed it in release v0.6.0. ## Workarounds Users are recommended to upgrade to v0.6.0 of `rusty-paseto`. However, users should still ensure that their key serialization and deserialization practices are secure and avoid any practices that could lead to key exposure. ## References More information about RUSTSEC-2022-0093 can be found in the [RustSec Advisory Database](https://rustsec.org/advisories/RUSTSEC-2022-0093.html). Updates and details regarding the upcoming release of `rusty-paseto` will be documented in the project's [releases](https://github.com/your-repo/rusty-paseto/releases) and [changelog](https://github.com/your-repo/rusty-paseto/blob/main/CHANGELOG.md). This issue was first reported by Dependabot on 2023-08-15. The source was reviewed by @rrrodzilla at that time and a determination was made that the vulnerability low harm to existing users due to the strongly typed nature of keys provided by the rusty-paseto API. @techport-om reported the vulnerability to the repository by discovering during a `cargo-audit` run on 2023-11-05 and opened [issue 28](https://github.com/rrrodzilla/rusty_paseto/issues/28). This advisory was created at that time to notify existing users. ## Which versions are affected by GHSA-j57r-4qw6-58r3? 2 open source packages ship an affected version, including rusty-paseto. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `rusty-paseto` | crates.io | All versions | 0.6.0 | | `rusty-paseto` | crates.io | All versions | 0.6.0 | ## How do I fix GHSA-j57r-4qw6-58r3? Upgrade rusty-paseto to 0.6.0 or later. ## Is GHSA-j57r-4qw6-58r3 being exploited? There is no known exploitation of GHSA-j57r-4qw6-58r3 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for GHSA-j57r-4qw6-58r3 and fix it if it is affected. What it is: GHSA-j57r-4qw6-58r3 is a vulnerability in rusty-paseto, published on 7 Nov 2023. Exploitation: There is no known exploitation of GHSA-j57r-4qw6-58r3 in the wild and no public exploit code. Affected packages and fixed versions: - rusty-paseto (crates.io): affected all versions; fixed in 0.6.0 - rusty-paseto (crates.io): affected all versions; fixed in 0.6.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/GHSA-j57r-4qw6-58r3/ (Markdown: https://insights.sbomify.com/GHSA-j57r-4qw6-58r3/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/GHSA-j57r-4qw6-58r3 --- From sbomify Insights: https://insights.sbomify.com/GHSA-j57r-4qw6-58r3/ Summaries are generated and may contain mistakes; the official description above is the record.