LowGO-2022-0963CVE-2022-36078GHSA-4p6f-m4f9-ch88

Resource exhaustion in github.com/gagliardetto/binary

Published 2 Sept 2022 · Updated 20 May 2024

Is your project on an affected github.com/gagliardetto/binary?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<0.7.1
Fixed in
0.7.1
Update to the fixed version for your release line, for example:go get github.com/gagliardetto/binary@v0.7.1

Details

A memory allocation vulnerability can be exploited to allocate arbitrarily large slices, which can exhaust available memory or crash the program.

When parsing data from untrusted sources of input (e.g. the blockchain), the length of the slice to allocate is read directly from the data itself without any checks, which could lead to an allocation of excessive memory.

Is GO-2022-0963 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/gagliardetto/binary, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.