Loading vulnerability…
Xerver 4.17 improperly handles alternate path representations in HTTP requests. A remote requester can append a trailing dot to a script resource to cause the server to disclose the script's source code rather than process it. A request containing a trailing null character can cause directory contents to be listed. The flaw is an improper resolution of path equivalence (CWE-41), where special path characters bypass expected resource handling and access restrictions.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 2 candidates as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An information-disclosure vulnerability in Xerver 4.17 that permits remote attackers to disclose script source code using a trailing dot or list directory contents through a trailing null character.
A path-equivalence vulnerability involving a trailing dot that permits source-code disclosure.
Source-code disclosure through trailing-dot path equivalence.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.