Fix Improper Error Handling in Rocket
Improper error handling in Rocket frameworks often leads to Information Disclosure. By leaking raw database errors, stack traces, or filesystem paths, you provide attackers with a roadmap of your backend. Hardening involves sanitizing client-facing messages while maintaining detailed internal logs.
The Vulnerable Pattern
#[get("/data/")]
fn get_data(id: usize) -> String {
// VULNERABLE: .unwrap() triggers a panic on failure, potentially leaking internals
// or returning raw error strings directly to the requester.
let secret_data = load_from_db(id).expect("Failed to connect to DB at 192.168.1.50");
secret_data
} The Secure Implementation
The fix eliminates internal state leakage by decoupling backend error details from HTTP responses. First, replace panicking methods like .unwrap() or .expect() with Result types. Second, use .map_err() to intercept internal errors, log them to a secure location (stderr/file), and transform them into generic status::Custom responses. Finally, implement Rocket 'Catchers' to provide a global safety net for unhandled status codes, ensuring the client never receives a raw stack trace or environment-specific metadata.
use rocket::http::Status; use rocket::response::status;#[get(“/data/
”)] fn get_data(id: usize) -> Result<String, status::Custom<&‘static str>> { load_from_db(id) .map_err(|e| { // Log the actual error internally for debugging eprintln!(“Internal Error: {:?}”, e); // Return a generic error to the client status::Custom(Status::InternalServerError, “An internal error occurred”) }) } #[catch(500)] fn handle_500() -> &‘static str { “Service unavailable. Please try again later.” }
#[launch] fn rocket() -> _ { rocket::build() .mount(”/”, routes![get_data]) .register(”/”, catchers![handle_500]) }
Your Rocket API
might be exposed to Improper Error Handling
74% of Rocket apps fail this check. Hackers use automated scanners to find this specific flaw. Check your codebase before they do.
Free Tier • No Credit Card • Instant Report
Verified by Ghost Labs Security Team
This content is continuously validated by our automated security engine and reviewed by our research team. Ghost Labs analyzes over 500+ vulnerability patterns across 40+ frameworks to provide up-to-date remediation strategies.