Actix WebApplication · Actix
CVE-2018-25025
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 extend the lifetime of a string, 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 · moderate confidenceA memory safety vulnerability in the actix-web Rust web framework allows unsound extension of string lifetimes, potentially causing use-after-free conditions and memory corruption. This is a Rust-specific safety violation where references outlive their referent.
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 the actix-web crate in your project dependenciesCheck your Cargo.lock file for the actix-web entry, or run `cargo tree -p actix-web` to see the installed versionAffected if The version listed is less than 0.7.15
-
Identify all projects using actix-webSearch for Cargo.toml files containing `actix-web` under [dependencies] or [dev-dependencies] across your codebaseAffected if Any project declares actix-web version < 0.7.15
-
Check runtime-installed crate versionIf actix-web is a runtime dependency, run `cargo pkgid actix-web` in the project directory to retrieve the exact versionAffected if The returned version is < 0.7.15
-
Inspect string handling usage in actix-web codeReview your application code for usage of actix-web's string types, particularly in request/response handling paths where external strings are stored or extendedAffected if Your code stores or extends string lifetimes from external input through actix-web APIs
You are affected if any actix-web dependency in your environment resolves to a version earlier than 0.7.15 and your application processes external strings through actix-web handlers.
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 actix-web crate to version 0.7.15 or later to resolve the lifetime soundness issue.
actix-web >= 0.7.15
- Locate your Cargo.toml file and identify the actix-web dependency
- Update the actix-web version requirement to 0.7.15 or later (e.g., actix-web = "0.7.15")
- Run `cargo update actix-web` or `cargo build` to fetch the fixed version
- Test your application thoroughly to ensure compatibility with the updated version
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-25025 — 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-25025 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