This is a summary of the AI-generated 10-question deep analysis. The full version (longer answers, follow-up Q&A, related CVEs) requires login. Read the full analysis โ
Q1What is this vulnerability? (Essence + Consequences)
๐จ **Essence**: Path Traversal in Eclipse BaSyx Java Server SDK. ๐ **Consequences**: Attackers write arbitrary files to the host filesystem via crafted `fileName` parameters during uploads.โฆ
๐ก๏ธ **CWE-22**: Improper Limitation of a Pathname to a Restricted Directory. ๐ **Flaw**: Insufficient path normalization in the Submodel HTTP API.โฆ
๐ **Privileges**: Runs as the Java process user. ๐พ **Data**: Full Read/Write access to host filesystem. ๐ **Action**: Execute arbitrary code (RCE). ๐ **Impact**: Complete system takeover.
๐ **Public Exp**: No PoC listed in data. ๐ **Wild Exp**: Unknown status. โ ๏ธ **Risk**: CVSS 10.0 suggests high likelihood of rapid exploitation if details leak.
Q7How to self-check? (Features/Scanning)
๐ **Check**: Scan for Eclipse BaSyx instances. ๐ **Verify**: Check Submodel HTTP API endpoints. ๐ **Test**: Attempt file upload with `../` in `fileName` parameter. ๐ก๏ธ **Monitor**: Look for unexpected file writes on host.
Q8Is it fixed officially? (Patch/Mitigation)
๐ง **Fix**: Upgrade to **Eclipse BaSyx Java Server SDK 2.0.0-milestone-10** or newer. ๐ฅ **Source**: Eclipse Foundation GitLab issues. ๐ **Action**: Immediate patching recommended.
Q9What if no patch? (Workaround)
๐ซ **Workaround**: Disable Submodel HTTP API if not needed. ๐ **Restrict**: Block external access to upload endpoints. ๐ **Isolate**: Run in container with limited filesystem permissions.โฆ