- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
`dlopen_derive` hasn't been updated since June 9, 2019.
`dlopen_derive` depends on [`quote = "0.6.12"`] and [`syn = "0.15.34"`]. Versions `1.0.0` of these dependencies were published on August 13, 2019. The `0.*` versions haven't received updates since.
Note that `dlopen` is an unmaintained crate from the same repository as `dlopen_derive`. However, migrating away from `dlopen_derive` implies migrating away from `dlopen`, as well.
## Recommended alternatives
- [`dlopen2_derive`] (and `dlopen2`)
[`dlopen2_derive`]: https://github.com/OpenByteDev/dlopen2 [`quote = "0.6.12"`]: https://github.com/dtolnay/quote/releases/tag/0.6.12 [`syn = "0.15.34"`]: https://github.com/dtolnay/syn/releases/tag/0.15.34
Is RUSTSEC-2023-0051 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | dlopen_derive | >=0.0.0-0 |
no fix listed |
References
Sources
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.