GitHub Advisoryadvisory · crates.io

GHSA-3227-r97m-8j95 Relative Path Traversal in afire serve_static

HIGH Published 2022-04-22 Modified 2022-04-22 Official page ↗
Ecosystem
crates.io
Packages
afire
Severity
High
Weaknesses
CWE-22, CWE-34
Reviewed
2022-04-22

Affected packages

• crates.io afire: >= 0.2.1, < 1.1.0 → fixed in 1.1.0

Description

Impact This vulnerability effects the built-in afire serve_static extension allowing paths containing `//....` to bypass the previous path sanitation and request files in higher directories that should not be accessible. Patches The issue has been fixed in afire 1.1.0. If you can, just update to the newest version of afire. Workarounds If you can't update afire you can simply disallow paths containing `/..` with the following middleware. Make sure this is the last middleware added to the server so it runs first, stopping the bad requests. ```rust use afire::prelude::*; struct PathTraversalFix; impl Middleware for PathTraversalFix { fn pre(&self, req: Request) -> MiddleRequest { if req.path.replace("\\", "/").contains("/..") { return MiddleRequest::Send( Response::new() .status(400) .text("Paths containing `..` are not allowed"), ); } MiddleRequest::Continue } } ``` ```rust let mut server = Server::new(host, port); PathTraversalFix.attach(&mut server); ``` References You can read about the new changes to afire in 1.1.0 here For more information If you have any questions or comments about this advisory you can email me or message me on discord. [https://connorcode.com/contact]

Related

Weakness · CWE (2)

  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory weakness
  • CWE-34 Path Traversal: '....//' weakness

References