Quick answers
- Is CVE-2018-25025 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2018-25025 being exploited in the wild.
- How severe is CVE-2018-25025?
- Critical severity, with a CVSS score of 9.8, published 6 January 2022.
- Which products and versions are affected?
- actix-web (crates.io) < 0.7.19.
- Is there a fix for CVE-2018-25025?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2018-25025 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2018-25025?
- Check whether you run actix-web (crates.io) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The actix-web crate (versions prior to 0.7.19) contains multiple memory safety issues stemming from the unsound use of 'unsafe' Rust code. Specifically, the framework could unsoundly extend the lifetime of a string, leading to an out-of-bounds write and subsequent memory corruption. Other related issues in these versions include the unsound coercion of immutable references to mutable ones and improper implementation of the 'Send' trait. These flaws can be exploited by a remote attacker over the network without authentication to achieve arbitrary code execution or a denial-of-service (use-after-free). The issues were addressed through a significant refactoring in version 0.7.19.
Affected products
- actix actix-web < 0.7.19
Identifiers
- CVE-2018-25025
- GHSA-fgfm-hqjw-3265
Timeline
- 2018-06-08: disclosed: Initial issue reported on GitHub
- 2021-12-27: advisory: NVD published CVE-2018-25025
- 2022-01-06: advisory: GitHub Advisory published