Directory Traversal in shttp safe_path
shttp versions before 0.0.5 contain a directory traversal vulnerability in the safe_path function. A remote attacker can supply a path combining ".." with subdirectory specifiers so that it resolves to a location at or below the web document root’s level but in a different directory-tree branch, bypassing the intended path restriction and allowing file reads.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
An unauthenticated remote attacker may read files from directory-tree locations outside the intended web document-root branch, potentially disclosing sensitive information accessible to the shttp process.
If you can’t patch tonight, do this now.
Until an upgrade is applied, restrict network access to the shttp service and prevent exposure to untrusted remote clients. Limit the service account's filesystem permissions so it cannot read sensitive files outside the intended web content tree.
Patch, then assume compromise.
Upgrade shttp to version 0.0.5 or later.
No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.