Adversarial Input in Actix

Fixing adversarial input vulnerabilities in Actix relies on rigorous validation at the framework's extraction points and leveraging its type-safe ecosystem. The primary defense is to never trust raw extractor outputs; instead, validate and sanitize data immediately after extraction. For JSON bodies, avoid relying solely on #[serde(deserialize_with = "...")] for security — use dedicated validation libraries like validator or schemars with actix-web::web::Data to apply constraints post-deserialization. Example:

use actix_web::{web, HttpResponse, Responder};
use serde::Deserialize;
use validator::Validate;

#[derive(Deserialize, Validate)]
struct UserUpdate {
    #[validate(length(min = 1, max = 50))]
    username: String,
    #[validate(range(min = 18, max = 120))]
    age: u32,
}

async fn update_user(item: web::Json) -> impl Responder {
    if let Err(e) = item.validate() {
        return HttpResponse::BadRequest().json(e);
    }
    // Proceed with validated data
    HttpResponse::Ok().finish()
}

For path and query parameters, apply similar validation:

use actix_web::{web, HttpResponse, Responder};
use serde::Deserialize;
use validator::Validate;

#[derive(Deserialize, Validate)]
struct PathParams {
    #[validate(length(min = 1))]
    #[validate(regex = "^[a-zA-Z0-9_-]+$")]
    user_id: String,
}

async fn get_user(path: web::Path) -> impl Responder {
    if let Err(e) = path.validate() {
        return HttpResponse::BadRequest().json(e);
    }
    // Safe to use path.user_id
    HttpResponse::Ok().body(format!("User: {}", path.user_id))
}

To prevent header injection, never embed unsanitized input into headers. Use Actix's HttpResponse::build() with explicit, validated values:

async fn set_header(user_input: web::Query>) -> impl Responder {
    let value = user_input.get("key").unwrap_or(&"default".to_string());
    if !value.is_ascii() || value.contains(&['\n', '\r'][..]) {
        return HttpResponse::BadRequest().finish();
    }
    HttpResponse::Ok()
        .header("X-Custom", value.as_str())
        .body("Header set")
}

Finally, protect shared state by ensuring mutations go through validated, authorized channels — use Actix's web::Data with Mutex or RwLock only after validating input, and consider using the actix-web-actors model for stateful services with strict message validation.