Skip to content

← Public intelligence

crates.io package

actix-web

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

4 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Critical, CVSS 9.8crates.ioPublished

    Out-of-bounds Write in actix-web

    CVE-2018-25024 · GHSA-9qj6-4rfq-vm84

    Affected
    • crates.io actix-web < 0.7.19
    Fixed in
    0.7.19· Vendor fix available
    Issue
    An issue was discovered in the actix-web crate before 0.7.19 for Rust. It can unsoundly coerce an immutable reference into a mutable reference, leading to memory corruption.

    Recommended action: Upgrade to 0.7.19 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Critical, CVSS 9.8crates.ioPublished

    Out-of-bounds Write in actix-web

    CVE-2018-25026 · GHSA-7x36-h62w-vw65

    Affected
    • crates.io actix-web < 0.7.19
    Fixed in
    0.7.19· Vendor fix available
    Issue
    An issue was discovered in the actix-web crate before 0.7.15 for Rust. It can add the Send marker trait to an object that cannot be sent between threads safely, leading to memory corruption.

    Recommended action: Upgrade to 0.7.19 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  3. Critical, CVSS 9.8crates.ioPublished

    Out-of-bounds Write in actix-web

    CVE-2018-25025 · GHSA-fgfm-hqjw-3265

    Affected
    • crates.io actix-web < 0.7.19
    Fixed in
    0.7.19· Vendor fix available
    Issue
    An 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.

    Recommended action: Upgrade to 0.7.19 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  4. Unratedcrates.ioPublished

    Multiple memory safety issues in actix-web

    GHSA-w65j-g6c7-g3m4

    Affected
    • crates.io actix-web < 0.7.19
    Fixed in
    0.7.19· Vendor fix available
    Issue
    Affected versions contain multiple memory safety issues, such as: - Unsoundly coercing immutable references to mutable references - Unsoundly extending lifetimes of strings - Adding the Send marker trait to objects that cannot be safely sent between threads This may result in a variety of memory corruption scenarios, most likely use-after-free. A signficant refactoring effort has been conducted to resolve these issues.

    Recommended action: Upgrade to 0.7.19 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →