Window can read out of bounds if Read instance returns more bytes than buffer size

Exploitation

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

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

rdiff performs a diff of two provided strings or files. As part of its reading code it uses the return value of a Read instance to set the length of its internal character vector. If the Read implementation claims that it has read more bytes than the length of the provided buffer, the length of the vector will be set to longer than its capacity. This causes rdiff APIs to return uninitialized memory in its API methods.

Published by the source

17 Jun 2022, 00:14 UTC

Last modified by the source

13 Jun 2023, 20:10 UTC

Source last checked

26 Oct 2026, 15:34 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-q579-9wp9-gfp2

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

# Patch Next advisory brief: GHSA-q579-9wp9-gfp2

Advisory: Window can read out of bounds if Read instance returns more bytes than buffer size
IDs: GHSA-q579-9wp9-gfp2
Record: https://patchnext.com/advisories/ghsa-q579-9wp9-gfp2 (revision 1, source checked 26 Oct 2026, 15:34 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io rdiff: affected <= 0.1.2

## Suggested inspection (read-only)
- crates.io rdiff: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on rdiff.
- 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-q579-9wp9-gfp2 (GitHub-reviewed advisory GHSA-q579-9wp9-gfp2 lists affected ranges: crates.io rdiff >=0 <=0.1.2)

Commands are suggestions: review each one before running it.