Versity panic induced by AWS chunked data sent to port

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

7.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Sending AWS chunk data with no Content-Length HTTP header causes the panic, every time. Reproduction Setup versity server running on port 7071, no SSL (for ease of packet tracing with tshark). Problem can be reproduced with or without SSL on the versity end. Use nginx to reverse proxy on port 7070. This does have to be SSL enabled for the repro to occur. nginx config: Use aws s3 cp to copy a large file (one that will trigger multipart upload) into versity via the nginx proxy on port 7070. AWS CLI must be version 2 for the repro to occur. Connecting directly to versity on port 7070 does not trigger the repro. Initial crash analysis The versity server enters a panic exception in function HashReader (csum-reader.go). The panic is due to a null value in the field r which should be a pointer to an io.Reader. The reason this field is blank goes back to code in the fasthttp library, ContinueReadBodyStream. This function exits prematurely if the incoming request ContentLength field is set to…

Published by the source

29 Aug 2025, 16:24 UTC

Last modified by the source

29 Aug 2025, 16:24 UTC

Source last checked

26 Oct 2026, 15:10 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-v2ch-c8v8-fgr7

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-v2ch-c8v8-fgr7

Advisory: Versity panic induced by AWS chunked data sent to port
IDs: GHSA-v2ch-c8v8-fgr7
Record: https://patchnext.com/advisories/ghsa-v2ch-c8v8-fgr7 (revision 1, source checked 26 Oct 2026, 15:10 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/versity/versitygw 1.0.17. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/versity/versitygw: affected < 1.0.17; fixed in 1.0.17

## Suggested inspection (read-only)
- Go github.com/versity/versitygw: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/versity/versitygw.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-v2ch-c8v8-fgr7 (GitHub-reviewed advisory GHSA-v2ch-c8v8-fgr7 lists affected ranges: Go github.com/versity/versitygw >=0 <1.0.17)

Commands are suggestions: review each one before running it.