Buffer overflow in deprecated USB HALs and stack overflow in USB enumeration

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.

Impact 1) If an application is making use of the deprecated kit protocol HALs as the communication channel to the target device an attacker can masquerade as a device and return malformed packets of arbitrary length which the protocol stack will write to the stack. HALs intended for production use are unaffected (I2C, SWI, & SPI) as well as the hidapi HAL (halallplatformskithidapi.c). 2) The hidapi HAL can be made to overrun the application stack by attaching more than 10 (real or virtual) devices likely resulting in an application crash as this does not allow arbitrary data to be written to the stack. Patches USB kit enumeration has been patched in v3.2.3 for the hidapi HAL (halallplatformskithidapi.c). Removal of deprecated HALs Deprecated usb kit HALs have been removed in v3.2.3. Workarounds This vulnerability is limited to users of the kit protocol which is used with Microchip kits and kit firmware to bridge communication from USB-HID to I2C or SWI. It is not expected that kits…

Published by the source

2 Oct 2020, 16:33 UTC

Last modified by the source

2 Dec 2024, 05:37 UTC

Source last checked

26 Oct 2026, 13:08 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-f366-4rvv-95x2

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-f366-4rvv-95x2

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

# Patch Next advisory brief: GHSA-f366-4rvv-95x2

Advisory: Buffer overflow in deprecated USB HALs and stack overflow in USB enumeration
IDs: GHSA-f366-4rvv-95x2
Record: https://patchnext.com/advisories/ghsa-f366-4rvv-95x2 (revision 2, source checked 26 Oct 2026, 13:08 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 fix available; fixed versions by package: cryptoauthlib 20200912. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI cryptoauthlib: affected < 20200912; fixed in 20200912

## Suggested inspection (read-only)
- `python -m pip show cryptoauthlib`: prints the installed version. Run with the environment that serves production active.

## 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 cryptoauthlib.
- 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://osv.dev/vulnerability/GHSA-f366-4rvv-95x2 (OSV record GHSA-f366-4rvv-95x2 lists affected ranges: PyPI cryptoauthlib >=0 <20200912 (fixed))
- Verified: https://github.com/advisories/GHSA-f366-4rvv-95x2 (GitHub-reviewed advisory GHSA-f366-4rvv-95x2 lists affected ranges: PyPI cryptoauthlib >=0 <20200912)

Commands are suggestions: review each one before running it.