Actix WebApplication · Actix
CVE-2018-25024
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was discovered in the actix-web crate before 0.7.15 for Rust. It can unsoundly coerce an immutable reference into a mutable reference, leading to memory corruption.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe actix-web crate before version 0.7.15 contains a soundness bug that allows immutable references to be unsafely coerced into mutable references, violating Rust's memory safety guarantees. This undefined behavior can lead to memory corruption and potential remote code execution. The vulnerability is a critical design flaw in the crate's internal reference handling.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Actix WebApplication
< 0.7.15CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate actix-web dependency in your projectSearch your project's Cargo.toml file for 'actix-web' or 'actix' in the dependencies section, or check Cargo.lock for the actix-web entryAffected if The actix-web crate is listed as a dependency
-
Determine the installed actix-web versionCheck the version number next to actix-web in Cargo.toml or the version entry in Cargo.lock (look for name = "actix-web" and the corresponding version field)Affected if The version number is less than 0.7.15 (e.g., 0.7.14, 0.7.13, 0.6.x, etc.)
-
Verify the application uses actix-web handlersInspect your source code for actix-web web::block, web::Data, or handler functions that process HTTP requests using actix-web actix::Handler implementationsAffected if The application uses actix-web web handlers that could trigger the unsound reference coercion
Your environment is affected if actix-web crate version less than 0.7.15 is present in your project dependencies and is used at runtime.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.7.15
Upgrade the actix-web crate to version 0.7.15 or later to obtain the patched version that properly enforces Rust's reference soundness rules.
actix-web 0.7.15
- Open your project's Cargo.toml file
- Locate the actix-web dependency declaration (e.g., actix-web = "0.7")
- Update the version to 0.7.15 or later (e.g., actix-web = "0.7.15")
- Run `cargo update actix-web` to update Cargo.lock
- Run `cargo build` to rebuild with the fixed version
- Verify the installed version using `cargo tree | grep actix-web`
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Actix Web
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-25024 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-25024 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data